[OpenSIPS-Users] Opensips ACK routing problem

[Nauman Sulaiman]

Maybe one way round this problem would be for us to replace the incoming RURI on the ACK with a sips address maybe to force Opensips to forward it on the tls connection

Not sure how to do this however or is there better way?

--- On Mon, 23/8/10, Nauman Sulaiman <nauman762-home at yahoo.co.uk> wrote:

> From: Nauman Sulaiman <nauman762-home at yahoo.co.uk>
> Subject: [OpenSIPS-Users] Opensips ACK routing problem
> To: users at lists.opensips.org
> Date: Monday, 23 August, 2010, 14:42
> Hi, using Opensips 1.6.2. We are
> using Opensips as outbound proxy using TLS just for final
> hop between UAC and Opensips. Other legs of the call will be
> udp. We have a test set up with Sipgate (but same occurs
> with other providers) where an incoming INVITE to the UAC
> via opensips results in 200ok  generated by UAC and
> then the ACK coming back from sipgate server is routed over
> udp connection as opposed to tls, opensips seems to be
> ignoring the Route header in the ACK
> 
> If the contact header has a sips uri opensips will route it
> correctly but some voip providers do not like sips uri in
> contact header and we are only using tls for the final hop
> so are not using a sips uri for contact header.
> 
> Do we have our understanding of the spec wrong or should
> opensips be routing according to the route header or should
> it use the contact header. 
> 
> Opensips ip 172.230.135.190   UAC ip
> 81.13.94.206
> 
> U 217.10.79.23:5060 -> 172.230.135.190:5060
> ACK sip:9082575 at 81.13.94.206:59053 SIP/2.0.
> Via: SIP/2.0/UDP
> 217.10.79.23:5060;branch=z9hG4bK59c7.0bbb2877.2.
> Via: SIP/2.0/UDP
> 172.20.40.4;branch=z9hG4bK59c7.0bbb2877.2.
> Via: SIP/2.0/UDP
> 217.10.79.23:5060;received=217.10.68.226;branch=z9hG4bK6a423428.
> Via: SIP/2.0/UDP
> 217.10.66.71:5060;branch=z9hG4bK6a423428;rport=5060.
> Route:
> <sip:172.230.135.190;r2=on;lr=on;ftag=as126bf37e>,<sip:172.230.135.190:5061;transport=tls;r2=on;lr=on;ftag=as126bf37e>.
> From: "anonymous" <sip:anonymous at sipgate.co.uk>;tag=as126bf37e.
> To: <sip:00441519082575 at sipgate.co.uk>;tag=94gc3N42r9X5D.
> Contact: <sip:anonymous at 217.10.66.71>.
> Call-ID: 181c48541a5ad00d04322ccc0752c846 at sipgate.co.uk.
> CSeq: 102 ACK.
> Max-Forwards: 67.
> Content-Length: 0.
> X-hint: rr-enforced.
> .
> 
> 
> U 172.230.135.190:5060 -> 81.13.94.206:59053
> ACK sip:9082575 at 81.13.94.206:59053 SIP/2.0.
> Via: SIP/2.0/UDP
> 172.230.135.190;branch=z9hG4bK59c7.6f77cf2.3.
> Via: SIP/2.0/UDP
> 217.10.79.23:5060;rport=5060;received=217.10.79.23;branch=z9hG4bK59c7.0bbb2877.2.
> Via: SIP/2.0/UDP
> 172.20.40.4;branch=z9hG4bK59c7.0bbb2877.2.
> Via: SIP/2.0/UDP
> 217.10.79.23:5060;received=217.10.68.226;branch=z9hG4bK6a423428.
> Via: SIP/2.0/UDP
> 217.10.66.71:5060;branch=z9hG4bK6a423428;rport=5060.
> From: "anonymous" <sip:anonymous at sipgate.co.uk>;tag=as126bf37e.
> To: <sip:00441519082575 at sipgate.co.uk>;tag=94gc3N42r9X5D.
> Contact: <sip:anonymous at 217.10.66.71>.
> Call-ID: 181c48541a5ad00d04322ccc0752c846 at sipgate.co.uk.
> CSeq: 102 ACK.
> Max-Forwards: 66.
> Content-Length: 0.
> X-hint: rr-enforced.
>  
> 
> 
> 
>       
> 
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>