This issue is now fixed in svn. Thanks Seven for access to your box to troubleshoot. Mike On Jun 16, 2009, at 9:17 AM, Seven Du wrote:
What's wrong of the contact string? 639(snom) works but 637(zoiper) doesn't.
"user" <sip:637@192.168.1.27:5070;rinstance=e1e47e9a22f3e450;transport=UDP;fs_nat=yes;fs_path=sip%3A637%40192.168.1.27%3A5070%3Brinstance%3De1e47e9a22f3e450%3Btransport%3DUDP
"seven" <sip:639@192.168.1.21:2051;line=298293g2;fs_nat=yes;fs_path=sip%3A639%40192.168.1.21%3A2051%3Bline%3D298293g2
On Jun 16, 2009, at 8:43 PM, Brian West wrote:
Ok i'll have to se what I can do about reproducing this issue now that I have more info on how its happening.
/b
On Jun 16, 2009, at 7:40 AM, dujinfang wrote:
Almost caught you on IRC Mike.
Our server is in a NAT'd network and all agents registered in the same LAN. I can remotely register by using the public IP and the contact string is right.
Call-ID: ZTZhMGJkZTE0NzNjZTlmZTkxYmU5NWRlZTU1MzJlYTE. User: 637@192.168.1.16 Contact: "user" <sip:637@210.73.8.180:5090;rinstance=9fc589bbc407518f
Agent: Zoiper rev.1809
So it's like only happens on our LAN and where there's a fs_path present.
Just curious, why agents registered on a local LAN has param fs_nat=yes; (default internal profile, port 5060) ?
Seems our time doesn't match, I'm generally available in office 9:00AM-6:00PM GMT+0800, so will try to catch you tomorrow.
Thank you.