Hmm, you are right, that wasn't the full syslog for that call. Investigating further I see that I get the following:<br><br>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' ''<br>
<br>This is right after the call has been established; the next event in the sip trace is at 22:53:40, the re-invite.<br><br>According to a year old post by Bogdan (<a href="http://www.mail-archive.com/users@lists.opensips.org/msg00700.html">http://www.mail-archive.com/users@lists.opensips.org/msg00700.html</a>) this means that ACK is received before 200 OK.<br>
<br>Here's the sip trace up to the point of the dialog error:<br>22:27:56.376925 Trunk -> Proxy : INVITE <br>22:27:56.381153 Proxy -> Trunk : 100 TRYING<br>22:27:56.381215 Proxy -> UA___ : INVITE<br>22:27:56.437339 UA___ -> Proxy : 100 TRYING<br>
22:27:56.552454 UA___ -> Proxy : 180 RINGING<br>22:27:56.552530 Proxy -> Trunk : 180 RINGING<br>22:28:07.179499 UA___ -> Proxy : 200 OK<br>22:28:07.182204 Proxy -> Trunk : 200 OK<br>22:28:07.197002 Trunk -> Proxy : ACK<br>
22:28:07.197158 Proxy -> UA___ : ACK<br><br>Could this be the source of the problem?<br><br>Best Regards,<br>Magnus<br><br><div class="gmail_quote">2010/2/3 Saúl Ibarra Corretgé <span dir="ltr"><<a href="mailto:saul@ag-projects.com">saul@ag-projects.com</a>></span><br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hi,<br>
<br>
El 03/02/10 14:43, Magnus Burman escribió:<br>
<div class="im">> Now I see what you're saying. I thought mediaproxy used the wrong port<br>
> in the re-invite, while it is in fact not engaged at all and thus the<br>
> original IP and port is sent on. That makes a lot of sense, thank you.<br>
><br>
> According to the docs the engage_media_proxy should only be called once<br>
> on the initial invite thou and after that use the dialog module to trace<br>
> the dialog. Any suggestions as how to debug where it fails? I'm not<br>
> getting any output in the syslog.<br>
><br>
<br>
</div>You are correct, the by calling engage_mediaproxy the dialog module<br>
should take care. However, it's surprising that this only happens<br>
sometimes, so it's harder to debug :( Is the syslog you pasted in your<br>
earlier mail the only output you get for that call? Any warning from the<br>
dialog module?<br>
<div class="im"><br>
<br>
<br>
Regards,<br>
<br>
--<br>
Saúl Ibarra Corretgé<br>
AG Projects<br>
<br>
_______________________________________________<br>
</div><div><div></div><div class="h5">Users mailing list<br>
<a href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
</div></div></blockquote></div><br>