[Home]

Summary:ASTERISK-02072: Registering with an intertex ix66 no longer works
Reporter:scaredycat (scaredycat)Labels:
Date Opened:2004-07-20 21:13:51Date Closed:2011-06-07 14:10:43
Priority:MinorRegression?No
Status:Closed/CompleteComponents:Core/General
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:
Description:The Intertex IX66 allows you to define domains that will be forced to register with it. eg sip.nixhelp.org resolves to my external ip, so I can register * using:

register => scaredycat@sip.nixhelp.org/100

and people could call that and the * box would ring the appropriate exten. Up until CVS from the 17th July this worked fine. Just updated from CVS (earlier in the day of the 20th) and it's stopped working and the asterisk box appears to be trying to register with itself (see additional information)



in the info192.168.1.2 is the ip of the asterisk box

****** ADDITIONAL INFORMATION ******

11 headers, 0 lines
Reliably Transmitting:
REGISTER sip:sip.nixhelp.org SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:5060;branch=z9hG4bK4a2529b8
From: <sip:andy@192.168.1.2>;tag=as72c0d7da
To: <sip:andy@192.168.1.2>
Call-ID: 3d1b58ba507ed7ab2eb141f241b71efb@127.0.0.1
CSeq: 105 REGISTER
User-Agent: Asterisk PBX
Expires: 3600
Contact: <sip:1000@192.168.1.2>
Event: registration
Content-Length: 0

(no NAT) to 192.168.1.2:5060


Sip read:
REGISTER sip:sip.nixhelp.org SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:5060;branch=z9hG4bK4a2529b8
From: <sip:andy@192.168.1.2>;tag=as72c0d7da
To: <sip:andy@192.168.1.2>
Call-ID: 3d1b58ba507ed7ab2eb141f241b71efb@127.0.0.1
CSeq: 105 REGISTER
User-Agent: Asterisk PBX
Expires: 3600
Contact: <sip:1000@192.168.1.2>
Event: registration
Content-Length: 0


11 headers, 0 lines
Using latest request as basis request
Sending to 192.168.1.2 : 5060 (non-NAT)
Transmitting (no NAT):
SIP/2.0 403 Forbidden
Via: SIP/2.0/UDP 192.168.1.2:5060;branch=z9hG4bK4a2529b8
From: <sip:andy@192.168.1.2>;tag=as72c0d7da
To: <sip:andy@192.168.1.2>;tag=as72c0d7da
Call-ID: 3d1b58ba507ed7ab2eb141f241b71efb@127.0.0.1
CSeq: 105 REGISTER
User-Agent: Asterisk PBX
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER
Contact: <sip:andy@192.168.1.2>
ontent-Length: 0


to 192.168.1.2:5060
Jul 20 23:46:40 NOTICE[81930]: chan_sip.c:7320 handle_request: Registration from '<sip:andy@192.168.1.2>' failed for '192.168.1.2'
Scheduling destruction of call '3d1b58ba507ed7ab2eb141f241b71efb@127.0.0.1' in 15000 ms


Sip read:
SIP/2.0 403 Forbidden
Via: SIP/2.0/UDP 192.168.1.2:5060;branch=z9hG4bK4a2529b8
From: <sip:andy@192.168.1.2>;tag=as72c0d7da
To: <sip:andy@192.168.1.2>;tag=as72c0d7da
Call-ID: 3d1b58ba507ed7ab2eb141f241b71efb@127.0.0.1
CSeq: 105 REGISTER
User-Agent: Asterisk PBX
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER
Contact: <sip:andy@192.168.1.2>
Content-Length: 0


10 headers, 0 lines
   -- Got SIP response 403 "Forbidden" back from 192.168.1.2
Destroying call '3d1b58ba507ed7ab2eb141f241b71efb@127.0.0.1'
Comments:By: Mark Spencer (markster) 2004-07-20 22:08:25

Ooh ooh!  I smell a configuration issue!

How about posting your sip.conf.  I'm going to take a wild stab in the dark here and say you have a sip.nixhelp.org peer which has host setting of 192.168.1.2 (or equivalent somehow).
By: scaredycat (scaredycat) 2004-07-21 17:25:59

ok, my config hasn;t changed at all, but you are correct... I had an entry in there for sip.nixhelp.org

Is this a change in how reg's work? This was definately working perfectly with no config changes from the 17th and stopped on the 20th..

I'd like to know if I'm insane or not.. I did a diff on the two chan_sip.c's - there's a lot of changes, not sure if any have any bearing on this..

You can close this one off....

edited on: 07-21-04 18:08
By: Mark Spencer (markster) 2004-07-21 23:42:51

Yes, behavior was changed recently so that we actually look up the host in the register as a peer rather than just a gethostbyname.  That allows you to use all the paramters of a sip peer in what you're registering with.