yes.

Regards,
Qasim


On Thu, May 16, 2013 at 2:50 PM, Bogdan-Andrei Iancu <[email protected]>wrote:

> **
> And do you have UDP 202.152.203.195 port 6000 as listener defined in
> OpenSIPS ??
>
> Regards,
>
> Bogdan-Andrei Iancu
> OpenSIPS Founder and Developerhttp://www.opensips-solutions.com
>
>
> On 05/16/2013 12:32 PM, [email protected] wrote:
>
>  Hi Bodgan,
>
>  Yes i see the following route header in my packet.
>
> Route:
> <sip:[email protected]:6000;lr;ftag=3b710c25;did=e55.a77ff685>
>
>
>  And yes i am routing it through loose_route.
>
>  Regards,
> Qasim
>
>
> On Wed, May 15, 2013 at 10:40 PM, Bogdan-Andrei Iancu <[email protected]
> > wrote:
>
>>  Hello Qasim,
>>
>> The ACK should be routed via loose_route() based on the "Route" headers
>> from it. Could you check if the Route hdrs (from the ACK) are correctly
>> reflecting your opensips interfaces ?
>>
>> Best regards,
>>
>> Bogdan-Andrei Iancu
>> OpenSIPS Founder and Developerhttp://www.opensips-solutions.com
>>
>>
>> On 05/14/2013 07:55 AM, [email protected] wrote:
>>
>>   Hi,
>>
>>  I am using OpenSIPs in Public<->Private bridging mode and have enabled
>> mhomed=1. But the problem is that when we have a call in which both parties
>> are on Public interface the INVITE gets relayed properly but and ACK of
>> that invite gives the following error.
>>
>> ERROR:core:get_out_socket: no socket found
>> ERROR:core:forward_request: cannot forward to af 2, proto 1 no
>> correspondinglistening socket
>>
>>  Regards,
>> Qasim
>>
>>
>> _______________________________________________
>> Users mailing 
>> [email protected]http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>>
>
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Reply via email to