[OpenSIPS-Users] Not forwarding 200 ok sporatically

[Vlad Paiu]

Hello,

Looking at your OpenSIPS logs, it seems that the 200 OK was succesfully 
relayed ( 2302 bytes written ) :

Nov 13 20:05:44 mediaproxy2 /sbin/opensips[311]: DBG:core:tcp_send: 
after write: c= 0x7f80dc6230d0 n=2302 fd=41
Nov 13 20:05:44 mediaproxy2 /sbin/opensips[311]: DBG:core:tcp_send: 
buf=#012SIP/2.0 200 Ok#015#012Via: SIP/2.0/TCP 
192.168.2.93:45442;received=24.186.16.85;branch=z9hG4bK.gLQAkbdo-;rport=45442#015#012From: 

Nov 13 20:05:44 mediaproxy2 /sbin/opensips[311]: DBG:tm:relay_reply: 
sent buf=0x7f80e70df3a8: SIP/2.0 2..., shmem=0x7f80dc616370: SIP/2.0 2

You do a ngrep trace on the OpenSIPS box, you do not see that 200 OK 
going out ?
Best Regards,

Vlad Paiu
OpenSIPS Developer
http://www.opensips-solutions.com

On 02.12.2014 13:41, Tito Cumpen wrote:
> Any idea what would cause this issue?? Not sure Michele and I are 
> facing the same issue.
>
> On Wed, Nov 26, 2014 at 3:53 AM, Michele Pinassi 
> <michele.pinassi at unisi.it <mailto:michele.pinassi at unisi.it>> wrote:
>
>     A similar issue happens to me, when from some voip phones i try to
>     call other voip phones.
>
>     For example, when from 5002 i try to call 5023.
>
>     Here's my config: http://pastebin.com/9gP9xncd
>
>     This is what happens on server 172.20.1.2 <http://172.20.1.2>:
>     http://pastebin.com/gZNSwyHB
>
>     This is the log on 5002: http://pastebin.com/RXtqwMtz
>
>     But on 5023 no INVITE arrive... :-( this happens only from some
>     phones while on others calling 5023 works as expected.
>
>     Michele
>
>
>     Il 25/11/2014 17:24, Vlad Paiu ha scritto:
>>     Hello,
>>
>>     Please provide the SIP trace and the OpenSIPS full debug log.
>>
>>     Best Regards,
>>     Vlad Paiu
>>     OpenSIPS Developer
>>     http://www.opensips-solutions.com  
>>     On 25.11.2014 11:50, Tito Cumpen wrote:
>>>     group
>>>
>>>
>>>     I am having an issue in which opensips will ignore the the 200
>>>     ok response to an invite . I am using Opensips 1.11. This will
>>>     cause the the b leg to assume a call and the A leg to be treated
>>>     by the failure route. I cant find the initial invite in the
>>>     debug logs but see the 200 ok response. I have captures of a
>>>     working call vs a non working and cannot find a difference that
>>>     would be the reason behind the failure. Is there anything I can
>>>     provide to help identify the cause of this issue?
>>>
>>>
>>>     Thanks,
>>>     Tito
>>>
>>>
>>>     _______________________________________________
>>>     Users mailing list
>>>     Users at lists.opensips.org  <mailto:Users at lists.opensips.org>
>>>     http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>>
>>
>>     _______________________________________________
>>     Users mailing list
>>     Users at lists.opensips.org  <mailto:Users at lists.opensips.org>
>>     http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>     -- 
>     Michele Pinassi
>     Responsabile Telefonia di Ateneo
>     Servizio Reti, Sistemi e Sicurezza Informatica - Università degli Studi di Siena
>     tel: 0577.(23)2169 - fax: 0577.(23)2053
>
>     Per trovare una soluzione rapida ai tuoi problemi tecnici
>     consulta le FAQ di Ateneo,http://www.faq.unisi.it  
>
>
>     _______________________________________________
>     Users mailing list
>     Users at lists.opensips.org <mailto:Users at lists.opensips.org>
>     http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
>
>
> _______________________________________________
> 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/20141202/4338c60e/attachment.htm>