[Home]

Summary:ASTERISK-16883: Registration failed when remote device sends port number afer domain in From field.
Reporter:performer (performer)Labels:
Date Opened:2010-10-27 12:19:37Date Closed:2012-02-01 09:10:40.000-0600
Priority:MinorRegression?No
Status:Closed/CompleteComponents:Channels/chan_sip/Registration
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:
Description:Registration failed when remote device sends port number afer domain in From field.
See dump below.

The work-around is to define new domian record at sip.conf that includes port number.
For example: domain=cyanidehouse.ru:5060


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

<--- SIP read from UDP:217.147.44.48:5060 --->
REGISTER sip:cyanidehouse.ru:5060 SIP/2.0
From: <sip:3006@cyanidehouse.ru:5060>;tag=a8c658-0-13c4-4cc6c42f-2b896461-4cc6c42f
To: <sip:3006@cyanidehouse.ru:5060>
Call-ID: a94cac-0-13c4-4cc6c13c-5fe6db00-4cc6c13c
CSeq: 4 REGISTER
Via: SIP/2.0/UDP 217.147.44.48:5060;branch=z9hG4bK-4cc6c42f-e86e58a6-6be1b1d6
Max-Forwards: 70
Contact: <sip:3006@217.147.44.48:5060>
Expires: 1200
Content-Length: 0


<------------->
--- (10 headers 0 lines) ---
Sending to 217.147.44.48:5060 (no NAT)

<--- Transmitting (no NAT) to 217.147.44.48:5060 --->
SIP/2.0 404 Not found (unknown domain)
Via: SIP/2.0/UDP 217.147.44.48:5060;branch=z9hG4bK-4cc6c42f-e86e58a6-6be1b1d6;received=217.147.44.48
From: <sip:3006@cyanidehouse.ru:5060>;tag=a8c658-0-13c4-4cc6c42f-2b896461-4cc6c42f
To: <sip:3006@cyanidehouse.ru:5060>;tag=as3d5e5744
Call-ID: a94cac-0-13c4-4cc6c13c-5fe6db00-4cc6c13c
CSeq: 4 REGISTER
Server: SweetHome Agent
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Content-Length: 0


<------------>
[Oct 27 21:21:26] NOTICE[21981]: chan_sip.c:23417 handle_request_register: Registration from '<sip:3006@cyanidehouse.ru:5060>' failed for '217.147.44.48:5060' - Not a local domain
Comments:By: Luke H (luckman212) 2011-05-05 08:53:20

seems redundant to have to add 2 entries ('host' and 'host:port' ) for every domain, was there ever a patch for this?  I'm running 1.8.3.3 and see this is still an issue
By: Mark Michelson (mmichelson) 2012-02-01 09:10:40.059-0600

This issue has been fixed as of revision 344215 to the 1.8 branch. The fix is in versions of Asterisk from 1.8.8.0 and later.