I have to diagnostic this system further, as before facing a memory shortage, there is a huge bunch of ERROR:tm:t_check: reply cannot be parsed Apr 29 19:16:58 osip /usr/local/sbin/opensips[20101]: ***BRANCH ROUTE** Apr 29 19:16:58 osip /usr/local/sbin/opensips[20104]: ***REPLY ROUTE - td[10.1.16.50]** Apr 29 19:16:58 osip /usr/local/sbin/opensips[20103]: ERROR:tm:t_check: reply cannot be parsed Apr 29 19:16:58 osip /usr/local/sbin/opensips[20101]: ***HOST ROUTED ***
________________________________ From: [email protected] on behalf of Julien Chavanton Sent: Thu 29/04/2010 8:27 PM To: [email protected] Subject: [OpenSIPS-Users] tm - module out of memory tm module went out of memory, we did face other problems with a non compliant SIP device, so this could well be a side effect of it. Any recommendation on tm memory usage ? opensips log ------------------------------------------------------------------------------------------- Apr 29 19:17:33 osip /usr/local/sbin/opensips[20101]: ERROR:tm:new_t: out of mem Apr 29 19:17:33 osip /usr/local/sbin/opensips[20101]: ERROR:tm:t_newtran: new_t failed
_______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
