[Asterisk-Users] Sipura 3000 inbound FXO problem
Michael Graves
mgraves at mstvp.com
Thu Dec 30 15:18:16 MST 2004
On Thu, 30 Dec 2004 11:49:59 -0600, Kristian Kielhofner wrote:
>Steven P. Donegan wrote:
>> Kristian Kielhofner wrote:
>>
>>> Steven P. Donegan wrote:
>>>
>>>> I have a Sipura 3000, apparently configured correctly, when incoming
>>>> calls arrive on the telco port they arrive properly on the Asterisk
>>>> system - however they don't get routed properly. The Asterisk message:
>>>>
>>>> Dec 30 07:47:16 NOTICE[2745]: chan_sip.c:7486 handle_request: Failed
>>>> to authenticate user WIRELESS CALLER
>>>> <sip:714XXXXXXX at 1.0.24.5>;tag=7f8072c0c46250f7o1
>>>>
>>>> X's are there to not advertise my phone number :-)
>>>>
>>>> Any idea as to why any kind of authenticate would be done or would
>>>> fail would be appreciated.
>>>
>>>
>>>
>>> Steven,
>>>
>>> It really seems like you need to setup an entry in sip.conf that
>>> "PSTN Line" on the sipura can register with. Do you have an entry in
>>> sip.conf for it? How is "PSTN Line" programmed?
>>>
>>> --
>>> Kristian Kielhofner
>>> _______________________________________________
>>> 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
>>>
>>>
>>>
>> Here is sip show peers:
>>
>> www*CLI> sip show peers
>> Name/username Host Dyn Nat ACL Mask Port
>> Status 1004/1004 1.0.24.223 D 255.255.255.255
>> 5060 Unmonitored
>> 1003/1003 1.0.24.223 D 255.255.255.255 5060
>> Unmonitored
>> 1002/1002 1.0.24.222 D 255.255.255.255 5061
>> Unmonitored
>> 1001/1001 1.0.24.222 D 255.255.255.255 5060
>> Unmonitored
>> 1000/1000 (Unspecified) D 255.255.255.255 0
>> Unmonitored
>> 5 sip peers loaded [4 online , 1 offline]
>>
>> Which seems to say the Sipura is registered...
>
>..snip..
>
>Steven,
>
> You need to create another "friend" for the Sipura FXO. You then need
>to configure "PSTN Line" to register as that user. You need to make
>sure that context= for your new friend allows the Sipura to forward
>those PSTN calls to where they need to go.
>
> Think of it like this - on a Sipura 2000, you have lines 1 + 2. On a
>Sipura 3000 your have lines 1 + 2 - it just so happens that they call
>line 2 "PSTN Line". It still needs valid login information to get to *.
>
>Example (1003 is the Sipura 3000 Line 1 user):
>
>[1003]
>type=friend
>username=1003
>secret=1003
>canreinvite=no
>host=dynamic
>dtmfmode=rfc2833
>mailbox=1003
>nat=no
>disallow=all
>allow=ulaw
>
>[1003-in] <--- can be anything, so long as you know what it is
>type=friend
>username=1003-in
>secret=1003-in
>canreinvite=no
>host=dynamic
>context=friends <---- set to whatever you need it to be
>dtmfmode=rfc2833
>nat=no
>disallow=all
>allow=ulaw
>
> Then, configure "PSTN Line" on the 3000 to register with your * machine
>as 1003-in. Hopefully this helps.
>
>--
>Kristian Kielhofner
Here's snippet from my SIP.CONF that related to a now out of service
SPA-3000.
[3016]
; Sipura SPA-3000, fxo port
type=friend
host=dynamic
username=3016
auth=md5
secret=3016
qualify=2000
dtmfmode=rfc2833
canreinvite=yes
context=from-inhouse
Michael
--
Michael Graves mgraves at pixelpower.com
Sr. Product Specialist www.pixelpower.com
Pixel Power Inc. mgraves at mstvp.com
o713-861-4005
o800-905-6412
c713-201-1262
More information about the asterisk-users
mailing list