[Home]

Summary:ASTERISK-14084: [patch] registration fails if multiple peers are specified in sip.conf
Reporter:Federico Santulli (fsantulli)Labels:
Date Opened:2009-05-07 11:07:26Date Closed:2009-07-13 18:33:21
Priority:BlockerRegression?Yes
Status:Closed/CompleteComponents:Channels/chan_sip/Registration
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:( 0) chan_sip_bug_15052_[20090626204511].patch
( 1) chan_sip_bug_15052.patch
( 2) sip.conf.txt
Description:if i use only one register line and only one peer is configured in sip.conf, registration works okey. If i add a registration line for another proxy and i add the relative section, asterisk wants to resolve [section_name] as hostname and registration fails
Comments:By: Federico Santulli (fsantulli) 2009-05-07 11:09:06

the attached file works great over asterisk 1.6.0.9, otherwise on asterisk 1.6.1.0 registrations fails.

By: Leif Madsen (lmadsen) 2009-05-11 11:54:46

I used your attached file, but added 'externip' and 'localnet' (because I'm behind NAT).

I then added two users for my digium account, and my unlimitel account.

Both of these registered fine, so I don't quite understand what the problem is.

I used the [section_name] in the register line like you have in your example.

By: Federico Santulli (fsantulli) 2009-05-13 06:53:35

This is what i got, in effect, today with externip and localnet it registers two peers, but it usually fails when more or different peers are specified, with the following message:

      > doing dnsmgr_lookup for 'section_name'
[May 13 13:46:22] WARNING[23255]: acl.c:376 ast_get_ip_or_srv: Unable to lookup 'section_name'
[May 13 13:46:22] NOTICE[23255]: chan_sip.c:9923 sip_reg_timeout:    -- Registration for '666@evil' timed out, trying again (Attempt #1)

By: Örn Arnarson (orn) 2009-05-13 08:50:54

Have you tried putting a full hostname in the register string?

By: Federico Santulli (fsantulli) 2009-05-13 16:17:41

i'm used to configure codecs, t38 fields and other settings into sip [section_names] so, why should i change a configuration considered functional into other asterisk releases ? Do this can depend on dns servers configured in resolv.conf ? why this problem does not appear when using asterisk 1.6.0.9 ?

By: Leif Madsen (lmadsen) 2009-05-14 09:59:32

It doesn't appear in 1.6.0.9 because the change that is causing this regression isn't present there.

By: Leif Madsen (lmadsen) 2009-05-14 10:01:54

What do you mean "usually fails when more or different peers are specified". Originally you said this happens with just 2 registrations. Are you saying this happens only with more than 2 registrations?

By: Federico Santulli (fsantulli) 2009-05-14 10:22:41

the problem appears with two or more registrations. Easy :)

By: Leif Madsen (lmadsen) 2009-05-14 10:35:01

OK, so I was not able to reproduce this issue then. I tried with two registrations to separate locations (different hostnames) and everything worked fine for me.

By: Federico Santulli (fsantulli) 2009-05-14 11:13:27

in the main configuration i have about 100 accounts pointing to the same sip server.
Register lines appears as follows:

register => user1:pass1@trunk_name/0001
register => user2:pass2@trunk_name/0002
register => user3:pass3@trunk_name/0003
register => user4:pass4@trunk_name/0004

also

register => user1:pass1@second_trunk_name/0001

[trunk_name]
type=peer
insecure=invite,port
host=192.168.0.100
canreinvite=no
qualify=no
disallow=all
allow=g729

[second_trunk_name]
type=peer
insecure=invite,port
host=192.168.0.101
canreinvite=no
qualify=no
disallow=all
allow=g729

this kind of output also produce the defect as follow:
[May 14 18:07:50] WARNING[4317]: acl.c:376 ast_get_ip_or_srv: Unable to lookup 'trunk_name'
[May 14 18:07:50] WARNING[4317]: acl.c:376 ast_get_ip_or_srv: Unable to lookup 'trunk_name'
[May 14 18:07:50] WARNING[4317]: acl.c:376 ast_get_ip_or_srv: Unable to lookup 'trunk_name'
[May 14 18:07:50] WARNING[4317]: acl.c:376 ast_get_ip_or_srv: Unable to lookup 'trunk_name'
[May 14 18:07:50] WARNING[4317]: acl.c:376 ast_get_ip_or_srv: Unable to lookup 'trunk_name'
[May 14 18:07:50] WARNING[4317]: acl.c:376 ast_get_ip_or_srv: Unable to lookup 'trunk_name'
[May 14 18:07:51] WARNING[4317]: acl.c:376 ast_get_ip_or_srv: Unable to lookup 'trunk_name'
[May 14 18:07:51] WARNING[4317]: acl.c:376 ast_get_ip_or_srv: Unable to lookup 'trunk_name'
[May 14 18:07:51] WARNING[4317]: acl.c:376 ast_get_ip_or_srv: Unable to lookup 'trunk_name'
[May 14 18:07:51] WARNING[4317]: acl.c:376 ast_get_ip_or_srv: Unable to lookup 'trunk_name'
[May 14 18:07:51] WARNING[4317]: acl.c:376 ast_get_ip_or_srv: Unable to lookup 'trunk_name'
[May 14 18:07:51] WARNING[4317]: acl.c:376 ast_get_ip_or_srv: Unable to lookup 'trunk_name'
[May 14 18:07:51] WARNING[4317]: acl.c:376 ast_get_ip_or_srv: Unable to lookup 'trunk_name'
[May 14 18:07:51] WARNING[4317]: acl.c:376 ast_get_ip_or_srv: Unable to lookup 'trunk_name'
[May 14 18:07:51] WARNING[4317]: acl.c:376 ast_get_ip_or_srv: Unable to lookup 'trunk_name'
[May 14 18:07:51] WARNING[4317]: acl.c:376 ast_get_ip_or_srv: Unable to lookup 'trunk_name'
[May 14 18:07:51] WARNING[4317]: acl.c:376 ast_get_ip_or_srv: Unable to lookup 'trunk_name'
[May 14 18:07:52] WARNING[4317]: acl.c:376 ast_get_ip_or_srv: Unable to lookup 'trunk_name'
[May 14 18:07:52] WARNING[4317]: acl.c:376 ast_get_ip_or_srv: Unable to lookup 'trunk_name'
[May 14 18:07:52] WARNING[4317]: acl.c:376 ast_get_ip_or_srv: Unable to lookup 'trunk_name'
[May 14 18:07:52] WARNING[4317]: acl.c:376 ast_get_ip_or_srv: Unable to lookup 'trunk_name'
[May 14 18:07:52] WARNING[4317]: acl.c:376 ast_get_ip_or_srv: Unable to lookup 'trunk_name'
[May 14 18:07:52] WARNING[4317]: acl.c:376 ast_get_ip_or_srv: Unable to lookup 'trunk_name'
[May 14 18:07:52] WARNING[4317]: acl.c:376 ast_get_ip_or_srv: Unable to lookup 'trunk_name'
[May 14 18:07:52] WARNING[4317]: acl.c:376 ast_get_ip_or_srv: Unable to lookup 'trunk_name'
[May 14 18:07:52] WARNING[4317]: acl.c:376 ast_get_ip_or_srv: Unable to lookup 'trunk_name'
[May 14 18:07:52] WARNING[4317]: acl.c:376 ast_get_ip_or_srv: Unable to lookup 'trunk_name'
[May 14 18:07:52] WARNING[4317]: acl.c:376 ast_get_ip_or_srv: Unable to lookup 'trunk_name'
[May 14 18:07:53] WARNING[4317]: acl.c:376 ast_get_ip_or_srv: Unable to lookup 'trunk_name'
[May 14 18:07:53] WARNING[4317]: acl.c:376 ast_get_ip_or_srv: Unable to lookup 'trunk_name'
[May 14 18:07:53] WARNING[4317]: acl.c:376 ast_get_ip_or_srv: Unable to lookup 'trunk_name'
[May 14 18:07:53] WARNING[4317]: acl.c:376 ast_get_ip_or_srv: Unable to lookup 'trunk_name'
[May 14 18:07:53] WARNING[4317]: acl.c:376 ast_get_ip_or_srv: Unable to lookup 'trunk_name'
[May 14 18:07:53] WARNING[4317]: acl.c:376 ast_get_ip_or_srv: Unable to lookup 'trunk_name'
[May 14 18:07:53] WARNING[4317]: acl.c:376 ast_get_ip_or_srv: Unable to lookup 'trunk_name'
[May 14 18:07:53] WARNING[4317]: acl.c:376 ast_get_ip_or_srv: Unable to lookup 'trunk_name'
[May 14 18:07:53] WARNING[4317]: acl.c:376 ast_get_ip_or_srv: Unable to lookup 'trunk_name'
[May 14 18:07:53] WARNING[4317]: acl.c:376 ast_get_ip_or_srv: Unable to lookup 'trunk_name'
[May 14 18:07:53] WARNING[4317]: acl.c:376 ast_get_ip_or_srv: Unable to lookup 'trunk_name'
[May 14 18:07:54] WARNING[4317]: acl.c:376 ast_get_ip_or_srv: Unable to lookup 'trunk_name'
[May 14 18:07:54] WARNING[4317]: acl.c:376 ast_get_ip_or_srv: Unable to lookup 'trunk_name'
[May 14 18:07:54] WARNING[4317]: acl.c:376 ast_get_ip_or_srv: Unable to lookup 'trunk_name'
[May 14 18:07:54] WARNING[4317]: acl.c:376 ast_get_ip_or_srv: Unable to lookup 'trunk_name'
[May 14 18:07:54] WARNING[4317]: acl.c:376 ast_get_ip_or_srv: Unable to lookup 'trunk_name'
[May 14 18:07:54] WARNING[4317]: acl.c:376 ast_get_ip_or_srv: Unable to lookup 'trunk_name'
[May 14 18:07:54] WARNING[4317]: acl.c:376 ast_get_ip_or_srv: Unable to lookup 'trunk_name'
[May 14 18:07:54] WARNING[4317]: acl.c:376 ast_get_ip_or_srv: Unable to lookup 'trunk_name'
[May 14 18:07:54] WARNING[4317]: acl.c:376 ast_get_ip_or_srv: Unable to lookup 'trunk_name'
[May 14 18:07:54] WARNING[4317]: acl.c:376 ast_get_ip_or_srv: Unable to lookup 'trunk_name'
[May 14 18:07:55] WARNING[4317]: acl.c:376 ast_get_ip_or_srv: Unable to lookup 'trunk_name'
[May 14 18:07:55] WARNING[4317]: acl.c:376 ast_get_ip_or_srv: Unable to lookup 'trunk_name'
[May 14 18:07:55] WARNING[4317]: acl.c:376 ast_get_ip_or_srv: Unable to lookup 'trunk_name'
[May 14 18:07:55] WARNING[4317]: acl.c:376 ast_get_ip_or_srv: Unable to lookup 'second_trunk_name'
[May 14 18:07:55] WARNING[4317]: acl.c:376 ast_get_ip_or_srv: Unable to lookup 'trunk_name'
[May 14 18:07:55] WARNING[4317]: acl.c:376 ast_get_ip_or_srv: Unable to lookup 'trunk_name'
[May 14 18:07:55] WARNING[4317]: acl.c:376 ast_get_ip_or_srv: Unable to lookup 'trunk_name'
[May 14 18:07:55] WARNING[4317]: acl.c:376 ast_get_ip_or_srv: Unable to lookup 'trunk_name'
[May 14 18:07:55] WARNING[4317]: acl.c:376 ast_get_ip_or_srv: Unable to lookup 'trunk_name'
[May 14 18:07:56] WARNING[4317]: acl.c:376 ast_get_ip_or_srv: Unable to lookup 'trunk_name'
[May 14 18:07:56] WARNING[4317]: acl.c:376 ast_get_ip_or_srv: Unable to lookup 'trunk_name'
[May 14 18:07:56] WARNING[4317]: chan_sip.c:16334 handle_response_register: Got 200 OK on REGISTER, but there isn't a registry entry for 'user1' (we probably already got the OK)
[May 14 18:07:56] WARNING[4317]: acl.c:376 ast_get_ip_or_srv: Unable to lookup 'trunk_name'
[May 14 18:07:56] WARNING[4317]: acl.c:376 ast_get_ip_or_srv: Unable to lookup 'trunk_name'
[May 14 18:07:56] WARNING[4317]: acl.c:376 ast_get_ip_or_srv: Unable to lookup 'trunk_name'
[May 14 18:07:56] WARNING[4317]: chan_sip.c:16334 handle_response_register: Got 200 OK on REGISTER, but there isn't a registry entry for 'user2' (we probably already got the OK)
[May 14 18:07:56] WARNING[4317]: acl.c:376 ast_get_ip_or_srv: Unable to lookup 'trunk_name'
[May 14 18:07:56] WARNING[4317]: acl.c:376 ast_get_ip_or_srv: Unable to lookup 'trunk_name'
[May 14 18:07:56] WARNING[4317]: acl.c:376 ast_get_ip_or_srv: Unable to lookup 'trunk_name'
[May 14 18:07:56] WARNING[4317]: chan_sip.c:16334 handle_response_register: Got 200 OK on REGISTER, but there isn't a registry entry for 'user3' (we probably already got the OK)
[May 14 18:07:56] WARNING[4317]: acl.c:376 ast_get_ip_or_srv: Unable to lookup 'trunk_name'
[May 14 18:07:56] WARNING[4317]: chan_sip.c:16334 handle_response_register: Got 200 OK on REGISTER, but there isn't a registry entry for 'user4' (we probably already got the OK)
[May 14 18:07:56] WARNING[4317]: acl.c:376 ast_get_ip_or_srv: Unable to lookup 'trunk_name'
[May 14 18:07:56] WARNING[4317]: acl.c:376 ast_get_ip_or_srv: Unable to lookup 'trunk_name'
[May 14 18:07:57] WARNING[4317]: acl.c:376 ast_get_ip_or_srv: Unable to lookup 'trunk_name'
[May 14 18:07:57] WARNING[4317]: chan_sip.c:16334 handle_response_register: Got 200 OK on REGISTER, but there isn't a registry entry for 'user5' (we probably already got the OK)
[May 14 18:07:57] WARNING[4317]: acl.c:376 ast_get_ip_or_srv: Unable to lookup 'trunk_name'
[May 14 18:07:57] WARNING[4317]: acl.c:376 ast_get_ip_or_srv: Unable to lookup 'trunk_name'
[May 14 18:07:57] WARNING[4317]: acl.c:376 ast_get_ip_or_srv: Unable to lookup 'trunk_name'
[May 14 18:07:57] WARNING[4317]: acl.c:376 ast_get_ip_or_srv: Unable to lookup 'trunk_name'
[May 14 18:07:57] WARNING[4317]: acl.c:376 ast_get_ip_or_srv: Unable to lookup 'trunk_name'
[May 14 18:07:57] WARNING[4317]: acl.c:376 ast_get_ip_or_srv: Unable to lookup 'trunk_name'
[May 14 18:07:57] WARNING[4317]: acl.c:376 ast_get_ip_or_srv: Unable to lookup 'trunk_name'
[May 14 18:07:57] WARNING[4317]: acl.c:376 ast_get_ip_or_srv: Unable to lookup 'trunk_name'
[May 14 18:07:58] WARNING[4317]: acl.c:376 ast_get_ip_or_srv: Unable to lookup 'trunk_name'
[May 14 18:07:58] WARNING[4317]: acl.c:376 ast_get_ip_or_srv: Unable to lookup 'trunk_name'
[May 14 18:07:58] WARNING[4317]: acl.c:376 ast_get_ip_or_srv: Unable to lookup 'trunk_name'
[May 14 18:07:58] WARNING[4317]: acl.c:376 ast_get_ip_or_srv: Unable to lookup 'trunk_name'
[May 14 18:07:58] WARNING[4317]: acl.c:376 ast_get_ip_or_srv: Unable to lookup 'trunk_name'
[May 14 18:07:58] WARNING[4317]: acl.c:376 ast_get_ip_or_srv: Unable to lookup 'trunk_name'
[May 14 18:07:58] WARNING[4317]: acl.c:376 ast_get_ip_or_srv: Unable to lookup 'trunk_name'
[May 14 18:07:58] WARNING[4317]: acl.c:376 ast_get_ip_or_srv: Unable to lookup 'trunk_name'
[May 14 18:07:58] WARNING[4317]: acl.c:376 ast_get_ip_or_srv: Unable to lookup 'trunk_name'
[May 14 18:07:58] WARNING[4317]: acl.c:376 ast_get_ip_or_srv: Unable to lookup 'trunk_name'
[May 14 18:07:58] WARNING[4317]: acl.c:376 ast_get_ip_or_srv: Unable to lookup 'second_trunk_name'
[May 14 18:07:58] NOTICE[4317]: chan_sip.c:9923 sip_reg_timeout:    -- Registration for 'user1@trunk_name' timed out, trying again (Attempt #2)
[May 14 18:07:59] WARNING[4317]: acl.c:376 ast_get_ip_or_srv: Unable to lookup 'trunk_name'
[May 14 18:07:59] NOTICE[4317]: chan_sip.c:9923 sip_reg_timeout:    -- Registration for 'user2@trunk_name' timed out, trying again (Attempt #2)
[May 14 18:07:59] WARNING[4317]: acl.c:376 ast_get_ip_or_srv: Unable to lookup 'trunk_name'
[May 14 18:07:59] WARNING[4317]: acl.c:376 ast_get_ip_or_srv: Unable to lookup 'trunk_name'
[May 14 18:07:59] WARNING[4317]: acl.c:376 ast_get_ip_or_srv: Unable to lookup 'trunk_name'
[May 14 18:07:59] WARNING[4317]: chan_sip.c:16334 handle_response_register: Got 200 OK on REGISTER, but there isn't a registry entry for 'user6' (we probably already got the OK)
[May 14 18:07:59] WARNING[4317]: acl.c:376 ast_get_ip_or_srv: Unable to lookup 'trunk_name'
[May 14 18:07:59] WARNING[4317]: acl.c:376 ast_get_ip_or_srv: Unable to lookup 'trunk_name'
[May 14 18:07:59] WARNING[4317]: chan_sip.c:16334 handle_response_register: Got 200 OK on REGISTER, but there isn't a registry entry for 'user7' (we probably already got the OK)
[May 14 18:07:59] WARNING[4317]: chan_sip.c:16334 handle_response_register: Got 200 OK on REGISTER, but there isn't a registry entry for 'user8' (we probably already got the OK)
[May 14 18:07:59] WARNING[4317]: chan_sip.c:16334 handle_response_register: Got 200 OK on REGISTER, but there isn't a registry entry for 'user9' (we probably already got the OK)
[May 14 18:07:59] WARNING[4317]: chan_sip.c:16334 handle_response_register: Got 200 OK on REGISTER, but there isn't a registry entry for 'user10' (we probably already got the OK)
[May 14 18:07:59] WARNING[4317]: chan_sip.c:16334 handle_response_register: Got 200 OK on REGISTER, but there isn't a registry entry for 'user11' (we probably already got the OK)
[May 14 18:07:59] WARNING[4317]: acl.c:376 ast_get_ip_or_srv: Unable to lookup 'trunk_name'
[May 14 18:07:59] WARNING[4317]: acl.c:376 ast_get_ip_or_srv: Unable to lookup 'trunk_name'
[May 14 18:07:59] WARNING[4317]: chan_sip.c:16334 handle_response_register: Got 200 OK on REGISTER, but there isn't a registry entry for 'user12' (we probably already got the OK)
[May 14 18:07:59] WARNING[4317]: acl.c:376 ast_get_ip_or_srv: Unable to lookup 'trunk_name'
[May 14 18:07:59] WARNING[4317]: chan_sip.c:16334 handle_response_register: Got 200 OK on REGISTER, but there isn't a registry entry for 'user13' (we probably already got the OK)
[May 14 18:07:59] WARNING[4317]: acl.c:376 ast_get_ip_or_srv: Unable to lookup 'trunk_name'
[May 14 18:08:00] WARNING[4317]: acl.c:376 ast_get_ip_or_srv: Unable to lookup 'trunk_name'
[May 14 18:08:00] WARNING[4317]: chan_sip.c:16334 handle_response_register: Got 200 OK on REGISTER, but there isn't a registry entry for 'user14' (we probably already got the OK)
[May 14 18:08:00] WARNING[4317]: acl.c:376 ast_get_ip_or_srv: Unable to lookup 'trunk_name'
[May 14 18:08:00] WARNING[4317]: acl.c:376 ast_get_ip_or_srv: Unable to lookup 'trunk_name'


I have noticed that srvlookup=no in sip.conf let the sip accounts registerbut warnings are still there.

Also i noticed that in "sip show registry" i have DNSMGR column marked to N for every peer specified.

By: Leif Madsen (lmadsen) 2009-05-15 07:56:05

What is the exact sip.conf that you are using? I have tried to reproduce this, and I can't. I even have 3 registrations working, I've tried with and without srvlookup=<yes|no>, I've tried with and without dnsmgr.conf enabled and disabled.

This does not appear to be an issue in 1.6.1.0. Is this really the version you are using? I need more information to go on because I've tried every way that I can to reproduce this issue, and I simply can't get it to happen.

By: Leif Madsen (lmadsen) 2009-05-15 08:00:01

*CLI>        > doing dnsmgr_lookup for 'lmadsen'
      > doing dnsmgr_lookup for 'callcentric'
      > doing dnsmgr_lookup for 'lmadsen'
      > doing dnsmgr_lookup for 'callcentric'
sip show registry
Host                           dnsmgr Username       Refresh State                Reg.Time                
416479XXXX:5060                N      416479XXXX         485 Registered           Fri, 15 May 2009 06:56:41
lmadsen:5060                   N      lmadsen            485 Registered           Fri, 15 May 2009 06:56:41
callcentric:5060               N      1777289XXXX         45 Registered           Fri, 15 May 2009 06:56:41
3 SIP registrations.


; sip.conf

[general]
register => 1777289XXXX:welcome@callcentric/1777289XXXX
register => lmadsen:welcome@lmadsen/lmadsen
register => 416479XXXX:welcome@416479XXXX/lmentinc

externip=174.116.XXX.XXX
localnet=192.168.128.0/255.255.255.0

[authentication]


[416479XXXX]
type=friend
username=416479XXXX
host=sip02.unlimitel.ca
secret=welcome
context=inbound
disallow=all
allow=ulaw
allow=g729
nat=no
call-limit=5
insecure=invite,port

[lmadsen]
type=friend
username=lmadsen
fromuser=lmadsen
host=pbx.somewhere.com
secret=welcome
context=alt_inbound
disallow=all
allow=ulaw
nat=no
call-limit=5
insecure=invite,port

[callcentric]
type=peer
context=from-callcentric
host=callcentric.com
username=1777289XXXX
secret=canada
fromuser=1777289XXXX
fromdomain=callcentric.com
insecure=invite,port

By: Leif Madsen (lmadsen) 2009-05-15 08:15:17

After talking to file on IRC, he has asked I request a SIP debug of this failing to try and determine if the packets are not actually getting sent. Those messages may not actually be indicating the real issue.

He has mentioned that he was able to reproduce it by using a nameserver that doesn't resolve invalid hosts. So my network configuration must be causing this to not fail for me.

Thanks!

By: philipp2 (philipp2) 2009-05-17 12:47:10

Possibly related: https://issues.asterisk.org/view.php?id=15139

By: Brian Vargyas (bkvargyas) 2009-06-14 13:21:29

This is happening to me as well.  Just installed 1.6.1.1 x86, 32bit, PBXIAF and I have two registrations to the same provider, dnsmgr continues to log errors and a sip debug shows registration after registration to my provider, who eventually locks me out for too many registrations.

If I leave the register entries the same (i.e. pointed to the same host --- sip.broadvoice.com:5060) and just change the actual host= entrie to a different proxy (broadvoice has multiple), then it seems to work fine.  it's when there are multiple host= entries that match where I see the problem.

By: Federico Santulli (fsantulli) 2009-06-23 11:53:56

Asterisk 1.6.1.1 and trunk suffers it as well.

It seems that if i specify a [sectionname] into host part, asterisk tries to resolve "sectionname" from dns (and fails) instead of search into sip.conf [sectionname] for the host field value.

I think this bug should be set as blocking as chan sip is totally unusable for me.

By: ptorres (ptorres) 2009-06-24 13:01:12

We have experienced something like this ( asterisk version 1.4.18 ) even with only one register.

Somehow we think it has to do with DNS resolution problems, (but it may expand to other cases). As a workaround we use IP addresses instead of domain names when possible (most of the time luckily).

When this problem happens sip show registry shows 'request sent'  , but Chan_sip gets blocked, not a simple sip packet gets answered/sent to other peers we tried to remove the problematic register line but 'sip reload' does not work and after another attempt the console show something like "Previous reload is pending"
The only 'solution' to unblock everything was to restart *

By: Federico Santulli (fsantulli) 2009-06-25 03:35:27

I agree with PTorres, the bug appears even with only one register. I suppose it's only related to DNS operations, as i discovered that, when peer is in "Request Sent" state, even when registration fails appears on cli, an outgoing call to that peer will stop every message and the peer magically goes into "Registered" state.

Also, i think that Bugs on Asterisk >=1.4.18 and >=1.6.1.0 are different and should be separated.



By: Federico Santulli (fsantulli) 2009-06-25 07:45:10

I signed license and uploaded a patch that apply to the current trunk.
Anyway it will also work over 1.6.1.0 and 1.6.1.1.

The patch is just related to a DNS Manager call and it's not applicable over 1.4 so bug 15139 is not a duplicate and must be re-opened.

By: Leif Madsen (lmadsen) 2009-06-26 13:33:18

Per Russell on IRC, there is some stuff missing here, so moving this to "Feedback"

By: Federico Santulli (fsantulli) 2009-06-26 13:47:27

As Russel asked on IRC i added peer_unref to the patch, so please move back to "acknowledged"

By: Digium Subversion (svnbot) 2009-07-13 18:26:52

Repository: asterisk
Revision: 206280

U   trunk/channels/chan_sip.c

------------------------------------------------------------------------
r206280 | dvossel | 2009-07-13 18:26:51 -0500 (Mon, 13 Jul 2009) | 9 lines

dns lookup of peername rather than peer's host in transmit_register()

(closes issue ASTERISK-14084)
Reported by: fsantulli
Patches:
     chan_sip_bug_15052_[20090626204511].patch uploaded by fsantulli (license 818)
Tested by: fsantulli


------------------------------------------------------------------------

http://svn.digium.com/view/asterisk?view=rev&revision=206280

By: Digium Subversion (svnbot) 2009-07-13 18:27:36

Repository: asterisk
Revision: 206281

_U  branches/1.6.2/
U   branches/1.6.2/channels/chan_sip.c

------------------------------------------------------------------------
r206281 | dvossel | 2009-07-13 18:27:36 -0500 (Mon, 13 Jul 2009) | 15 lines

Merged revisions 206280 via svnmerge from
https://origsvn.digium.com/svn/asterisk/trunk

........
 r206280 | dvossel | 2009-07-13 18:26:51 -0500 (Mon, 13 Jul 2009) | 9 lines
 
 dns lookup of peername rather than peer's host in transmit_register()
 
 (closes issue ASTERISK-14084)
 Reported by: fsantulli
 Patches:
       chan_sip_bug_15052_[20090626204511].patch uploaded by fsantulli (license 818)
 Tested by: fsantulli
........

------------------------------------------------------------------------

http://svn.digium.com/view/asterisk?view=rev&revision=206281

By: Digium Subversion (svnbot) 2009-07-13 18:33:19

Repository: asterisk
Revision: 206282

_U  branches/1.6.1/
U   branches/1.6.1/channels/chan_sip.c

------------------------------------------------------------------------
r206282 | dvossel | 2009-07-13 18:33:19 -0500 (Mon, 13 Jul 2009) | 15 lines

Merged revisions 206280 via svnmerge from
https://origsvn.digium.com/svn/asterisk/trunk

........
 r206280 | dvossel | 2009-07-13 18:26:51 -0500 (Mon, 13 Jul 2009) | 9 lines
 
 dns lookup of peername rather than peer's host in transmit_register()
 
 (closes issue ASTERISK-14084)
 Reported by: fsantulli
 Patches:
       chan_sip_bug_15052_[20090626204511].patch uploaded by fsantulli (license 818)
 Tested by: fsantulli
........

------------------------------------------------------------------------

http://svn.digium.com/view/asterisk?view=rev&revision=206282