Yeah, if you able to get it to work. I have been working on this for
about 3 hours now. I can't get the thing to connect. I was once
getting 503 now I am getting 403 Forbidden from StanaPhone.
Ergh, this is very annoying.
Travis Conway
EFS, Inc.
Information Technology
Desk: (334) 215-6551
Mobile: (334) 391-4450
mailto:travis@homeoffice.quikpawn.com
-----Original Message-----
From: Chris Shaw [mailto:chriss@watertech.com]
Sent: Wednesday, August 11, 2004 6:13 PM
To: asterisk-users@lists.digium.com
Subject: Re: [Asterisk-Users] StanaPhone and Asterisks
----- Original Message -----
From: "Pulu 'Anau" <pulu@afe.to>
To: <asterisk-users@lists.digium.com>; "Travis Conway"
<tconway@tritonmanagementgroup.com>
Sent: Wednesday, August 11, 2004 3:52 PM
Subject: Re: [Asterisk-Users] StanaPhone and Asterisks
> >From my sip.conf:
>
> register=9146186144:notyoursecret@sip.stanaphone.com/9146186144
>
> [stanaphone]
> fromdomain=sip.stanaphone.com
> fromuser=9146186144
> type=peer
> secret=notyoursecret
> auth=MD5
> username=9146186144
> host=sip.stanaphone.com
> dtmfmode=info
> context=default
> canreinvite=no
> disallow=all
> allow=ulaw
> allow=ilbc
>
> It looks like the only big difference is with the fromuser thing. I
had a> really hard time with it, and ended up searching alot until I found
this
setup> in some cablemodem fansite. Outgoing always seems to work fine,
incoming
I have> problems with, sometimes it fails on the registration with
unauthorized
errors.>
> Pulu
Neat, another *-capable provider...
The insecure=very should fix the incoming calls issue if it's on *'s
end, I
noticed that you didn't have that anywhere. Also adding an [incoming]
context as type peer without username and password info should work as
well...
-Chris
_______________________________________________
Asterisk-Users mailing list
Asterisk-Users@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