just setup a gateway in fs that has reg=false and the proper credentials to pass the challenge.<br><br><br><div class="gmail_quote">On Thu, Oct 30, 2008 at 2:49 PM, Wellie Chao <span dir="ltr"><<a href="mailto:wchao@yahoo.com">wchao@yahoo.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hangups do not work for me under certain circumstances. Here is the<br>
background information:<br>
<br>
* Our carrier uses a Metaswitch server with Acme Packet in front as a<br>
proxy/SBC. Only the Acme Packet machine is publicly visible<br>
(<a href="http://64.115.128.6" target="_blank">64.115.128.6</a>).<br>
<br>
* Our Freeswitch server is at <a href="http://216.57.23.143" target="_blank">216.57.23.143</a>.<br>
<br>
* For calls originating from Freeswitch and terminating on Metaswitch<br>
(<a href="http://216.57.23.143" target="_blank">216.57.23.143</a> -> <a href="http://64.115.128.6" target="_blank">64.115.128.6</a>), Freeswitch authenticates with<br>
Metaswitch and everything works hunky-dorey. Either side can hang up and<br>
the other side will automatically hang up without requiring a manual<br>
hang-up.<br>
<br>
Now the problem:<br>
<br>
For calls originating from Metaswitch to Freeswitch (<a href="http://64.115.128.6" target="_blank">64.115.128.6</a> -><br>
<a href="http://216.57.23.143" target="_blank">216.57.23.143</a>), Metaswitch does not authenticate with Freeswitch.<br>
Metaswitch also does not use the existing authenticated registration that<br>
our Freeswitch server initiates with Metaswitch upon startup of<br>
Freeswitch. Metaswitch just begins a new (unauthenticated) session and we<br>
have configured Freeswitch to allow any inbound calls from <a href="http://64.115.128.6" target="_blank">64.115.128.6</a><br>
without requiring authentication.<br>
<br>
We receive inbound calls (Metaswitch to Freeswitch, <a href="http://64.115.128.6" target="_blank">64.115.128.6</a> -><br>
<a href="http://216.57.23.143" target="_blank">216.57.23.143</a>) just fine. The phone rings and we can have a normal<br>
conversation. If the caller (the endpoint attached to Metaswitch) hangs<br>
up, both sides hang up. If I hang up (remember, I'm at the endpoint<br>
attached to Freeswitch), the caller's line remains attached forever.<br>
<br>
I have recorded a packet trace. Look at freeswitch_2.cap in the ZIP file,<br>
and you want to graph the first call starting at 21.202 and ending 53.798.<br>
If you go to time 53.087, you can see that my Freeswitch server sends a<br>
BYE to Metaswitch. This is a result of me hanging up my phone. At time<br>
53.089, you see Metaswitch responding with 401 Unauthorized. Later at time<br>
53.777, you see a BYE from Metaswitch to Freeswitch, but you should ignore<br>
this because that was a result of the caller (the guy hooked up to<br>
Metaswitch) manually hanging up. If he had not hung up his phone, the BYE<br>
from Metaswitch to Freeswitch would not have been issued and his phone<br>
would just stay on the line forever. Also, when I hang up my phone, I see<br>
the following at the Freeswitch console:<br>
<br>
2008-10-29 23:03:28 [ERR] sofia_reg.c:1089<br>
sofia_reg_handle_sip_r_challenge() No Matching gateway found<br>
<br>
I presume that Freeswitch emits this error because it got the 401<br>
Unauthorized from Metaswitch.<br>
<br>
I also asked our carrier for a packet trace of a successful hangup on the<br>
Aastra platform (the engineer at the carrier says it is an Asterisk<br>
derivative -- I'm not sure about that). Look at<br>
Aastra_authentication_test.cap in the ZIP file. Graph the first call<br>
starting at 43.633 and ending 93.156. If you go to 93.118, you'll see that<br>
the Aastra server sends a BYE. Just like our Freeswitch scenario,<br>
Metaswitch sends back a 401 Unauthorized, but in response to the 401<br>
Unauthorized, Aastra then sends back another BYE with the difference that<br>
the second BYE is authenticated. Metaswitch gets the second BYE and<br>
responds with 200 OK.<br>
<br>
I am pretty sure that if Freeswitch were to send back a second BYE (but<br>
with authentication), it would work fine. Now my question is how can I do<br>
this? I am not sure if this divergence of behavior is caused by: (a) my<br>
own error in configuring Freeswitch, (b) Metaswitch lacking standard SIP<br>
support (maybe it's not supposed to send the 401 Unauthorized), or (c)<br>
Freeswitch lacking standard SIP support (maybe it's supposed to send back<br>
a second BYE with authentication automatically). I don't know the SIP<br>
standards (or Freeswitch) well enough to know whether this problem is<br>
caused by me or by a deficiency in one of the two products (Metaswitch or<br>
Freeswitch).<br>
<br>
Can you provide some pointers?<br>
<br>
The ZIP file with the packet traces can be downloaded here:<br>
<a href="http://216.57.23.143/hangup_problem.zip" target="_blank">http://216.57.23.143/hangup_problem.zip</a><br>
<br>
_______________________________________________<br>
Freeswitch-users mailing list<br>
<a href="mailto:Freeswitch-users@lists.freeswitch.org">Freeswitch-users@lists.freeswitch.org</a><br>
<a href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/listinfo/freeswitch-users</a><br>
UNSUBSCRIBE:<a href="http://lists.freeswitch.org/mailman/options/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/options/freeswitch-users</a><br>
<a href="http://www.freeswitch.org" target="_blank">http://www.freeswitch.org</a><br>
</blockquote></div><br><br clear="all"><br>-- <br>Anthony Minessale II<br><br>FreeSWITCH <a href="http://www.freeswitch.org/">http://www.freeswitch.org/</a><br>ClueCon <a href="http://www.cluecon.com/">http://www.cluecon.com/</a><br>
<br>AIM: anthm<br><a href="mailto:MSN%3Aanthony_minessale@hotmail.com">MSN:anthony_minessale@hotmail.com</a><br>GTALK/JABBER/<a href="mailto:PAYPAL%3Aanthony.minessale@gmail.com">PAYPAL:anthony.minessale@gmail.com</a><br>
IRC: <a href="http://irc.freenode.net">irc.freenode.net</a> #freeswitch<br><br>FreeSWITCH Developer Conference<br><a href="mailto:sip%3A888@conference.freeswitch.org">sip:888@conference.freeswitch.org</a><br><a href="http://iax:guest@conference.freeswitch.org/888">iax:guest@conference.freeswitch.org/888</a><br>
<a href="mailto:googletalk%3Aconf%2B888@conference.freeswitch.org">googletalk:conf+888@conference.freeswitch.org</a><br>pstn:213-799-1400<br>