[OpenSIPS-Users] Opensips + RtpProxy: media stream timed out while starting

Eric Tamme eric at uphreak.com
Sat Feb 14 02:47:15 CET 2015


The message about late back means it is probably not routing.

Install ngrep and run

ngrep -qtd any -W byline port 5060

On OpenSIPS during the call.  Paste the output to a gist on gist.github.com and include the link in your next reply.

-Eric



On Feb 13, 2015, 6:19 PM, at 6:19 PM, Semen Golubcov <thegolub4 at gmail.com> wrote:
>Hello. Should i answer you here or send my replies to the user list?
>
>I looked up the sip trace and syslog, apparently there are no
>retransmissions i think and there is no messages about "no matching
>transaction exists".
>
>Feb 14 01:19:43 martin /usr/local/sbin/opensips[14061]:
>DBG:core:parse_msg:  method:  <ACK>
>Feb 14 01:19:43 martin /usr/local/sbin/opensips[14061]:
>DBG:core:parse_msg:  uri:     <sip:53049768 at 92.xx.xx.xx(my_Public_ip
>(client) ):49190;transport=tls>
>Feb 14 01:19:43 martin /usr/local/sbin/opensips[14061]:
>DBG:core:parse_msg:  version: <SIP/2.0>
>Feb 14 01:19:43 martin /usr/local/sbin/opensips[14061]:
>DBG:core:parse_headers: flags=2
>Feb 14 01:19:43 martin /usr/local/sbin/opensips[14061]:
>DBG:core:parse_via_param: found param type 235, <rport> = <n/a>;
>state=6
>Feb 14 01:19:43 martin /usr/local/sbin/opensips[14061]:
>DBG:core:parse_via_param: found param type 232, <branch> =
><z9hG4bKPjb29aaf78cf594541aeb97e0b801a4075>; state=6
>Feb 14 01:19:43 martin /usr/local/sbin/opensips[14061]:
>DBG:core:parse_via_param: found param type 237, <alias> = <n/a>;
>state=16
>Feb 14 01:19:43 martin /usr/local/sbin/opensips[14061]:
>DBG:core:parse_via:
>end of header reached, state=5
>Feb 14 01:19:43 martin /usr/local/sbin/opensips[14061]:
>DBG:core:parse_headers: via found, flags=2
>Feb 14 01:19:43 martin /usr/local/sbin/opensips[14061]:
>DBG:core:parse_headers: this is the first via
>Feb 14 01:19:43 martin /usr/local/sbin/opensips[14061]:
>DBG:core:receive_msg: After parse_msg...
>Feb 14 01:19:43 martin /usr/local/sbin/opensips[14061]:
>DBG:core:receive_msg: preparing to run routing scripts...
>Feb 14 01:19:43 martin /usr/local/sbin/opensips[14061]:
>DBG:sl:sl_filter_ACK: to late to be a local ACK!
>
>In this example i was calling calling from one user to another on my
>machine (so the ip will always be the same for both clients). I guess
>here:
>Feb 14 01:19:43 martin /usr/local/sbin/opensips[14061]:
>DBG:core:parse_msg:  method:  <ACK>
>Feb 14 01:19:43 martin /usr/local/sbin/opensips[14061]:
>DBG:core:parse_msg:  uri:     <sip:53049768 at 92.xx.xx.xx(my_Public_ip
>(client) ):49190;transport=tls>
>Feb 14 01:19:43 martin /usr/local/sbin/opensips[14061]:
>DBG:core:parse_msg:  version: <SIP/2.0>
>Feb 14 01:19:43 martin /usr/local/sbin/opensips[14061]:
>DBG:core:parse_headers: flags=2
>
>The server get's the ack from my client, and than opensips says:
>
>"Apr  5 23:06:22 ser /usr/local/sbin/ser[6282]: DEBUG : sl_filter_ACK:
>to
>late to be a local ACK!"
>
>Does this mean that ACK is getting lost? I'll attach the syslog just in
>case.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20150213/85d0fb70/attachment-0001.htm>


More information about the Users mailing list