[OpenSIPS-Users] Broken Loose Routing?

[Brett Nemeroff]

On Thu, Oct 30, 2008 at 9:34 AM, Bogdan-Andrei Iancu <bogdan at voice-system.ro
> wrote:

> Hi Brett,
>
> Yes, the BYE is sent again to your opensips, because, as Inaki said, the
> incoming BYE has a bogus RURI - it has to be the contact from the INVITE,
> but you can see it actually points to our own server. This confuses opensips
> which thinks the previous hop was a strict router.
>
> Check with the with the next public hope as they screw up the INVITE
> contact (which propagates into BYE RURI)
>
> Regards,
> Bogdan
>
>
Bogdan,
The next public hop is the provider. Are you saying that I'm sending them an
INVITE with a bad Contact header? I'm not sure where you are saying the bad
header is.. The contact header I send to them in the INVITE looks like this:

   1. U 62.175.182.141:5060 -> 195.62.163.131:5060
   2. INVITE sip:17475551212 at 195.62.163.131:5060;transport=udp SIP/2.0.
   3. Record-Route: <sip:62.175.182.141
   ;r2=on;lr;ftag=1c2145666146;did=fe6.729dae35>.
   4. Record-Route: <sip:10.10.65.141
   ;r2=on;lr;ftag=1c2145666146;did=fe6.729dae35>.
   5. Via: SIP/2.0/UDP 62.175.182.141;branch=z9hG4bKac82.22c28106.0.
   6. Via: SIP/2.0/UDP 10.10.67.190;branch=z9hG4bKac2145676337.
   7. Max-Forwards: 69.
   8. From: <sip:15125551234 at dvm2-vxgw-1.sfba.mydomain.net
   >;tag=1c2145666146.
   9. To: <sip:17475551212 at 10.10.65.141>.
   10. Call-ID: 214566535627102008205744 at 10.10.67.190.
   11. CSeq: 1 INVITE.
   12. Contact: <sip:15125551234 at 10.10.67.190:5060>.
   13. Supported:
   em,100rel,timer,replaces,path,early-session,resource-priority.
   14. Allow:
   REGISTER,OPTIONS,INVITE,ACK,CANCEL,BYE,NOTIFY,PRACK,REFER,INFO,SUBSCRIBE,UPDATE.
   15. Remote-Party-ID: <sip:15125551234 at 10.10.65.141
   >;party=calling;privacy=off;screen=no;npi=0;ton=0.
   16. Remote-Party-ID: <sip:17475551212 at 10.10.65.141>;party=called;npi=0
   ;ton=0.
   17. x-channel: ds/ds1-5/6;IP=10.10.67.190.
   18. User-Agent: dvm2-vxgw-1/v.5.20A.048.006.
   19. Content-Type: application/sdp.
   20. Content-Disposition: session.
   21. Content-Length: 271.

Contact: <sip:15125551234 at 10.10.67.190:5060> Looks right to me? Is it not?

Then the BYE from the Provider has a RURI that looks like this:

   1. U 195.62.163.131:5060 -> 62.175.182.141:5060
   2. BYE sip:15125551234 at 62.175.182.141:5060 SIP/2.0.
   3. Record-Route: <sip:195.62.163.131;lr;ftag=BDA2FF96-481D6819>.
   4. Via: SIP/2.0/UDP 195.62.163.131;branch=z9hG4bKac82.9acd04c3.0.
   5. Via: SIP/2.0/UDP 76.235.229.126;branch=z9hG4bKf2ef284024BE6DBB.
   6. From: <sip:17475551212 at 10.10.65.141>;tag=BDA2FF96-481D6819.
   7. To: <sip:15125551234 at dvm2-vxgw-1.sfba.mydomain.net>;tag=1c2145666146.
   8. Route: <sip:62.175.182.141;r2=on;lr;ftag=1c2145666146;did=fe6.729dae35>,
   <sip:10.10.65.141;r2=on;lr;ftag=1c2145666146;did=fe6.729dae35>.
   9. CSeq: 1 BYE.
   10. Call-ID: 214566535627102008205744 at 10.10.67.190.
   11. Contact: <sip:17475551212 at 76.235.229.126>.
   12. User-Agent: PolycomSoundPointIP-SPIP_320-UA/2.1.1.0037.
   13. Max-Forwards: 69.
   14. Content-Length: 0.
   15. RemoteIP: 76.235.229.126.
   16. P-hint: rr-enforced.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.opensips.org/pipermail/users/attachments/20081030/cfe23f06/attachment.htm