[OpenSIPS-Users] One way audio - media port changed (opensips / mediaproxy)

Magnus Burman magnus.burman at adamo.es
Thu Feb 4 12:54:07 CET 2010


Hmm, you are right, that wasn't the full syslog for that call. Investigating
further I see that I get the following:

Jan 11 22:28:07 sbc1 /usr/sbin/opensips[27792]:
CRITICAL:dialog:log_next_state_dlg: bogus event 6 in state 2 for dlg
0x7f5e880692a0 [1305:480665684] with clid
'a27f94c890000e3e13c410b392b13d753bdb84e00e2147f91b8-0266-6714' and tags
'e-13c4-10b392b-75e19db4-10b392b' ''

This is right after the call has been established; the next event in the sip
trace is at 22:53:40, the re-invite.

According to a year old post by Bogdan (
http://www.mail-archive.com/users@lists.opensips.org/msg00700.html) this
means that ACK is received before 200 OK.

Here's the sip trace up to the point of the dialog error:
22:27:56.376925 Trunk -> Proxy : INVITE
22:27:56.381153 Proxy -> Trunk : 100 TRYING
22:27:56.381215 Proxy -> UA___ : INVITE
22:27:56.437339 UA___ -> Proxy : 100 TRYING
22:27:56.552454 UA___ -> Proxy : 180 RINGING
22:27:56.552530 Proxy -> Trunk : 180 RINGING
22:28:07.179499 UA___ -> Proxy : 200 OK
22:28:07.182204 Proxy -> Trunk : 200 OK
22:28:07.197002 Trunk -> Proxy : ACK
22:28:07.197158 Proxy -> UA___ : ACK

Could this be the source of the problem?

Best Regards,
Magnus

2010/2/3 Saúl Ibarra Corretgé <saul at ag-projects.com>

> Hi,
>
> El 03/02/10 14:43, Magnus Burman escribió:
> > Now I see what you're saying. I thought mediaproxy used the wrong port
> > in the re-invite, while it is in fact not engaged at all and thus the
> > original IP and port is sent on. That makes a lot of sense, thank you.
> >
> > According to the docs the engage_media_proxy should only be called once
> > on the initial invite thou and after that use the dialog module to trace
> > the dialog. Any suggestions as how to debug where it fails? I'm not
> > getting any output in the syslog.
> >
>
> You are correct, the by calling engage_mediaproxy the dialog module
> should take care. However, it's surprising that this only happens
> sometimes, so it's harder to debug :( Is the syslog you pasted in your
> earlier mail the only output you get for that call? Any warning from the
> dialog module?
>
>
>
> Regards,
>
> --
> Saúl Ibarra Corretgé
> AG Projects
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.opensips.org/pipermail/users/attachments/20100204/02d98214/attachment.htm 


More information about the Users mailing list