[SR-Users] ASYNC Module

[Alex Balashov]

On 06/12/2015 07:07 PM, Aaron Hamstra wrote:

> Jun 12 22:55:41 /usr/local/sbin/kamailio[23297]: DEBUG: <core> [tcp_main.c:2552]: tcpconn_do_send(): tcp_send: aft£Y;ùô0#}¤V|#031Y#037$kÍlJ8CÂ}F’å«Õ=661 fd=12
> Jun 12 22:55:41 /usr/local/sbin/kamailio[23297]: DEBUG: tm [t_hooks.c:288]: run_trans_callbacks_internal(): DBG: trans=0x7f36f40f0228, callback type 8388608, id 0 entered                 x#003Ø|ïYå?*â'£qbÔk*#020Ø#03
> Jun 12 22:55:41 /usr/local/sbin/kamailio[23297]: DEBUG: siptrace [siptrace.c:1847]: pipport2su(): the port string is 5061      VâG–.9AÏ#001#030#033#024yt8H¶#001F˜ÃßáF%eæåom~Í’‰ªr(väÓÊ#010

I find the garbage data in these log entries highly suspect, although 
I'm not necessarily qualified to debug this to the bottom.

If you can spare the time, I'd try to test the following things:

1. Does this also occur if you call async_route() while processing 
another type of request, i.e. an OPTIONS or an INVITE request, as 
opposed to REGISTER?

2. Does this happen only with the TCP transport, or also UDP?

If #2 doesn't prove to be the case, it might indicate that the cause of 
the suspected regression is a change in code unrelated to async or TM 
per se.

-- Alex

-- 
Alex Balashov | Principal | Evariste Systems LLC
303 Perimeter Center North, Suite 300
Atlanta, GA 30346
United States

Tel: +1-800-250-5920 (toll-free) / +1-678-954-0671 (direct)
Web: http://www.evaristesys.com/, http://www.csrpswitch.com/