Hi Juha,
On 10/18/07, Juha Heinanen jh@tutpro.com wrote:
[...] replies always obey via headers. in-dialog requests should obey rr header.
Thank you for your answer. I am a bit confused as when I tested with other sip phones (sipura or some common soft phones), the reply come right back to the server:
U 2007/10/18 09:33:10.412644 192.168.5.119:5060 -> xx.xx.28.203:5060 INVITE sip:2031@192.168.0.6:5060 SIP/2.0. Record-Route: sip:xx.xx.33.119:5060;nat=yes;lr=on. Via: SIP/2.0/UDP 192.168.5.119;branch=z9hG4bKbb68.aef53616.1. Via: SIP/2.0/UDP 192.168.5.120:5060;branch=z9hG4bK06ffa32f;rport=5060. From: "2030" sip:2030@192.168.5.120;tag=as5d0ed162. To: sip:2031@192.168.5.119. Contact: sip:2030@192.168.5.120. Call-ID: 75284ea22077807748c712db79678f15@192.168.5.120. CSeq: 102 INVITE.
U 2007/10/18 09:33:10.478888 xx.xx.28.203:5060 -> 192.168.5.119:5060 SIP/2.0 100 Trying. To: sip:2031@192.168.5.119. From: "2030" sip:2030@192.168.5.120;tag=as5d0ed162. Call-ID: 75284ea22077807748c712db79678f15@192.168.5.120. CSeq: 102 INVITE. Via: SIP/2.0/UDP 192.168.5.119;branch=z9hG4bKbb68.aef53616.1. Via: SIP/2.0/UDP 192.168.5.120:5060;branch=z9hG4bK06ffa32f;rport=5060. Record-Route: sip:xx.xx.33.119:5060;nat=yes;lr=on. Server: Sipura/SPA941-4.1.8.
My openser have a private IP (192.168.5.119) statically natted to xx.xx.33.119; so the first via contains the private IP. Is it up to the client to figure out how to manage this or is there a way to handle this in openser ?
Thanks,