[Asterisk-Users] strange behaviour of asterisk sip.conf type=user vs type=peer

[Gary Reuter]

My guess is the problem is related to the reverse lookup of
147.135.20.128<http://147.135.20.128>
.
sip.broadvoice.com <http://sip.broadvoice.com> =
147.135.20.128<http://147.135.20.128>
147.135.20.128 <http://147.135.20.128> = non-existant

If you change your "host=sip.broadvoice.com <http://sip.broadvoice.com>" to
"host=147.135.20.128 <http://147.135.20.128>" it'll probably work until they
change the IP of their server....
Someone else who actually uses broadvoice may have a better solution.

On 10/25/05, Vikas <topgun9 at gmail.com> wrote:
>
> Hi,
>
> In sip.conf if
> type=peer
> then incoming calls from broadvoice are sent to context=incoming in
> the extension.conf file.
>
> But in sip.conf if
> type=user
> then we get the following messages in the packets being exchanged with
> broadvoice:
> 1. "Found no matching peer or user for '147.135.20.128:5060<http://147.135.20.128:5060>
> '"
> 2. Looking for 4155131083 in default
> 3. Reliably Transmitting (no NAT):
> 4. SIP/2.0 404 Not Found
>
> The sip.conf host section for broadvoice looks like:
> [sip.broadvoice.com <http://sip.broadvoice.com>]
> callerid=xxxxxxxxxx
> context=incoming
> fromdomain=sip.broadvoice.com <http://sip.broadvoice.com>
> host=sip.broadvoice.com <http://sip.broadvoice.com>
> insecure=very
> secret=xxxxxxxx
> type=peer
> user=xxxxxxxxx
> username=xxxxxxxxx
>
> Why is this happening,
>
> vikas
> _______________________________________________
> --Bandwidth and Colocation sponsored by Easynews.com <http://Easynews.com>--
>
> Asterisk-Users mailing list
> Asterisk-Users at lists.digium.com
> http://lists.digium.com/mailman/listinfo/asterisk-users
> To UNSUBSCRIBE or update options visit:
> http://lists.digium.com/mailman/listinfo/asterisk-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20051025/056e3ab4/attachment.htm