<p>Poster is having problem when he disallows anonymous sip peers. Do you know at all how FreePBX deals with anonymous sip peers? Obviously you haven't yet seen the dialplan for FreePBX.</p>
<p>When there is enough detail in the post and I am aware of the problem, I always try to help. I don't believe in making guesses. Troubleshooting requires some good detail of the problem. And yes, answering non-asterisk related issues is not the goal of this mailing list.<br>
</p>
<p>Zeeshan A Zakaria</p>
<p>--<br>
<a href="http://www.ilovetovoip.com">www.ilovetovoip.com</a></p>
<p><blockquote type="cite">On 2010-09-11 9:24 PM, "Jeff LaCoursiere" <<a href="mailto:jeff@sunfone.com">jeff@sunfone.com</a>> wrote:<br><br><p><font color="#500050"><br>> --<br>> <a href="http://www.ilovetovoip.com">www.ilovetovoip.com</a><br>
> <br>> > On 2010-09-11 7:22 PM, "Paul Belanger"<br>> > <paul.belanger@polybea...</font></p>[un top posting]<br>
<p><font color="#500050"><br>On Sat, 2010-09-11 at 19:30 -0400, Zeeshan Zakaria wrote:<br>> Actually it is a very easy to understan...</font></p>Its not that he isn't receiving a response - its that his peer debug<br>
statement isn't getting tripped because the peer hasn't authenticated.<br>
That's why I suggested he debug by IP rather than peer. Then what he<br>
will see is the SIP auth attempts and asterisk rejecting them, but in my<br>
experience not much is of value in seeing those packets - it doesn't<br>
point to *why* the connection is being rejected. The routing must be ok<br>
since allowing guest sip connections (the result of setting "accept<br>
anonymous" in FreePBX) allows the calls to come in fine.<br>
<br>
His problem is the peer authenticating. This of course has nothing to<br>
do with extensions.conf, as the dialplan is not involved. It is a SIP<br>
authentication problem, purely. There is no "relevant code" to post,<br>
and if you had ever looked into FreePBX's "relevant code" you would<br>
realize that it is actually fairly complex, and you would indeed have a<br>
difficult time debugging the flow.<br>
<br>
It *might* help if he posted his peer entry, but without seeing the<br>
other side that may not help much either. As Paul suggested first off,<br>
he should be in touch with his provider, whose tech support should be<br>
able to help him sort it out.<br>
<br>
I ran into a strange one EXACTLY like this just last week. We have a<br>
residential dial-tone customer with a Linksys SPA2102 (our standard<br>
device for this service). He had someone come out and replace his home<br>
router, and when he did he stopped authenticating. He has a fixed IP,<br>
so I enabled the debugging as I have mentioned twice now (by IP) and saw<br>
the attempts and rejections. After much hair pulling I *disabled* nat<br>
in his peer entry and it suddenly connected fine. This is bizarre, as<br>
our standard peer configuration works for 100% of the rest of our<br>
customers, who all connect from behind their home nat gateways of all<br>
kinds. I still don't know why that fixed it.<br>
<br>
Sorry you took it so harshly Zeeshan, but the only posts that stick out<br>
to me from you are the ones where you are bashing people for posting<br>
questions. I don't recall any off the top of my head where you are<br>
actually helping. Yup, I consider that policing, and it isn't needed.<br>
Like someone else suggested, if you don't want to read it, delete it.<br>
And no, I am not going to bother to read back through archives to see if<br>
that is the truth. Its my impression of your posts, thats all.<br>
<br>
j<br>
<font color="#888888"><br>
<br>
<br>
<br>
<br>
<br>
--<br>
_____________________________________________________________________<br>
</font><p><font color="#500050">-- Bandwidth and Colocation Provided by <a href="http://www.api-digital.com">http://www.api-digital.com</a> --</font></p><p><font color="#500050">New to Asterisk? Join us for a live introductory webinar every Thurs:<br>
<a href="http://www.aste.">http://www.aste.</a>..</font></p></blockquote></p>