<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">This issue is now fixed in svn. Thanks Seven for access to your box to troubleshoot.<div><br></div><div>Mike</div><div><br><div><div>On Jun 16, 2009, at 9:17 AM, Seven Du wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>What's wrong of the contact string? 639(snom) works but 637(zoiper) doesn't.</div><div><br></div><div>"user" <<a href="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">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</a>></div><div><br></div><div>"seven" <<a href="sip:639@192.168.1.21:2051;line=298293g2;fs_nat=yes;fs_path=sip%3A639%40192.168.1.21%3A2051%3Bline%3D298293g2">sip:639@192.168.1.21:2051;line=298293g2;fs_nat=yes;fs_path=sip%3A639%40192.168.1.21%3A2051%3Bline%3D298293g2</a>></div><div><br></div><br><div>On Jun 16, 2009, at 8:43 PM, Brian West wrote:<br class="Apple-interchange-newline"><blockquote type="cite"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Ok i'll have to se what I can do about reproducing this issue now that I have more info on how its happening.<div><br></div><div>/b</div><div><br><div><div>On Jun 16, 2009, at 7:40 AM, dujinfang wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0; ">Almost caught you on IRC Mike.<div><br></div><div>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.</div><div><br></div><div><div>Call-ID: ZTZhMGJkZTE0NzNjZTlmZTkxYmU5NWRlZTU1MzJlYTE.</div><div>User: <span class="Apple-converted-space"> </span><a href="mailto:637@192.168.1.16">637@192.168.1.16</a></div><div>Contact: "user" <<a href="sip:637@210.73.8.180:5090;rinstance=9fc589bbc407518f">sip:637@210.73.8.180:5090;rinstance=9fc589bbc407518f</a>></div><div>Agent: Zoiper rev.1809</div></div><div><div><br></div><div>So it's like only happens on our LAN and where there's a fs_path present.</div><div><br></div><div>Just curious, why agents registered on a local LAN has param fs_nat=yes; (default internal profile, port 5060) ?</div><div><br></div><div>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.</div><div><br></div><div>Thank you.</div></div></span></blockquote></div></div></div></blockquote></div></div></blockquote></div><br></div></body></html>