On 05/07/10 12:40, Gareth Blades wrote:
> Mike A. Leonetti wrote:
>
>> On 05/07/10 12:14, Gareth Blades wrote:
>>
>>> Mike A. Leonetti wrote:
>>>
>>>
>>>> On 05/07/10 11:52, Gareth Blades wrote:
>>>>
>>>>
>>>>> Mike A. Leonetti wrote:
>>>>>
>>>>>
>>>>>
>>>>>> In an attempt to connect our Asterisk 1.6 phone system with another
>>>>>> phone system called "Broadsmart", they gave me credentials to register
>>>>>> to.
>>>>>>
>>>>>> Connected to Asterisk 1.6.2.5 currently running on watermelon (pid =
>>>>>> 10365)
>>>>>> watermelon*CLI> sip show registry
>>>>>> Host dnsmgr Username Refresh
>>>>>> State Reg.Time
>>>>>> {broadsmart_ip}:5060 N {broadsmart_user} 3317
>>>>>> Registered Fri, 07 May 2010 11:21:41
>>>>>> 1 SIP registrations.
>>>>>>
>>>>>> It shows that I am registered. But when I go to make a call using:
>>>>>> exten => 706,1,Macro(broadsmart,706)
>>>>>>
>>>>>> and the Macro
>>>>>> [macro-broadsmart]
>>>>>> exten => s,1,Dial(SIP/${ar...@broadsmart,60)
>>>>>>
>>>>>> Asterisk reports:
>>>>>> [May 7 11:34:45] WARNING[10402]: chan_sip.c:17775
>>>>>> handle_response_invite: Received response: "Forbidden" from '"Mike A.
>>>>>> Leonetti" <sip:{broadsmart_us...@broadsmart.net>;tag=as6376d669'
>>>>>>
>>>>>> The people on the other end sent me this e-mail:
>>>>>>
>>>>>>
>>>>>>
>>>>> The register command has one set of credentials but if you are dialing
>>>>> using Dial(SIP/${ar...@broadsmart,60) then the credentials will be
>>>>> looked up in the [broadsmart] section within sip.conf
>>>>>
>>>>>
>>>>>
>>>>>
>>>> So is there a way to dial out using what is already registered?
>>>>
>>>>
>>>>
>>> No. The server you register with can often be different to the one you
>>> pass calls to so keeping them completely separate makes a lot of sense.
>>> You can put the authentication information in the dial command itself
>>> but that is generally not a good idea because it can expose the username
>>> and password to other applications which integrate into asterisk or when
>>> viewing the asterisk console.
>>>
>>>
>>>
>>>
>> So then where is my mistake? The credentials in broadsmart look like
>> the same from whats being registered.
>>
>>
> I cant say but just made you aware that both are separate so the
> password may be wrong in one place. It would be best to do a sip debug
> and that may help diagnose the problem.
>
> I am off now so wont be back until after the weekend so hopefully
> someone else will help furthur.
>
>
It turns out that it's actually on the registration end. I see that too:
[May 7 13:02:14] NOTICE[10402]: chan_sip.c:11461 sip_reregister: --
Re-registration for {broadsmart_passwo...@{broadsmart_ip}
REGISTER 12 headers, 0
lines
Reliably Transmitting (no NAT) to
{broadsmart_ip}:5060:
REGISTER sip:{broadsmart_ip}
SIP/2.0
Via: SIP/2.0/UDP
{asterisk_ip}:5060;branch=z9hG4bK6df043c0;rport
Max-Forwards:
70
From:
<sip:{broadsmart_passwo...@{broadsmart_ip}>;tag=as59ede08c
To:
<sip:{broadsmart_passwo...@{broadsmart_ip}>
Call-ID:
4fd754b9115b2e1c2c17ce6d1f24b...@127.0.0.1
CSeq: 104
REGISTER
User-Agent: Asterisk PBX
1.6.2.5
Authorization: Digest username="{broadsmart_password}",
realm="Registered_Subscribers", algorithm=MD5, uri="sip:broadsmart.net",
nonce="c022714eff5d7016afe930e9390392a3",
response="2e14289556acb0bf2657504c9147b6c1",
opaque="e5677a6b"
Expires:
3600
Contact:
<sip:s...@{asterisk_ip}>
Content-Length: 0
--
_____________________________________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
http://www.asterisk.org/hello
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
