asterisk users - Feb 2003 - SIP register= bug?

I am seeing some very peculiar things in the routines that REGISTER 
my * server with several accounts.

I saw this on my console:
.
.
.
NOTICE[5126]: File chan_sip.c, Line 1878 (sip_reg_timeout): 
Registration timed out, trying again
NOTICE[5126]: File chan_sip.c, Line 1878 (sip_reg_timeout): 
Registration timed out, trying again
NOTICE[5126]: File chan_sip.c, Line 1878 (sip_reg_timeout): 
Registration timed out, trying again
NOTICE[5126]: File chan_sip.c, Line 1878 (sip_reg_timeout): 
Registration timed out, trying again

and so, being curious, I did this to see what was happening during 
one of these "trying again" transactions:

garthim# tethereal port sip
Capturing on fxp0
   0.000000 asterisk.foo.com -> 10.0.1.100 SIP Request: REGISTER 
sip:195.37.77.101
   0.010619 10.0.1.100 -> asterisk.foo.com SIP Status: 501 Not Implemented
  10.021967 asterisk.foo.com -> 10.0.1.100 SIP Request: REGISTER 
sip:195.37.77.101
  10.036395 10.0.1.100 -> asterisk.foo.com SIP Status: 501 Not Implemented
^C
garthim#


What's wrong here?  you ask.

Well, asterisk appears to be trying to "REGISTER" with one of my 
ATA-186's, which is clearly not a Good Thing.  Somehow, * has swapped 
some IP address information somewhere in it's little head. 
10.0.1.100 is my ATA-186, and thus should not be getting REGISTER 
attempts _from_ asterisk, and is thus throwing errors.  Note that 
195.37.77.101 resolves to fox.iptel.org


Here's my sip.conf, distilled and anonymized:

[general]
disallow=gsm
allow=ulaw
port = 5060                     ; Port to bind to
bindaddr = 0.0.0.0              ; Address to bind to
context = from-sip              ; Default for incoming calls

register=65000:blahblahblah at inoc-dba.pch.net/65000
register=14155551212:blahblahblah at sipauth.deltathree.com/14155551212
register=18438:blahblahblah at fwd.pulver.com/18438
register=jtodd:blahblahblah at iptel.org/90764

[iconnect]
type=friend
secret=[blahblahblah]
username=[blahblahblah]
host=sipauth.deltathree.com

[fwd]
type=friend
secret=[blahblahblah]
username=18438
host=fwd.pulver.com


[coloco]
context=coloco
type=friend
;username=[blahblahblah]
;secret=[blahblahblah]
host=172.18.32.22


[inoc-dba]
type=friend
host=204.61.208.90
username=[blahblahblha]
secret=[blahblahblah]
context=inoc-dba

[2203]
type=friend
username=2203
secret=[blahblahblah]
host=10.0.1.100
permit=10.0.1.100/24
context=intern
canreinvite=no

On Sat, Feb 22, 2003 at 02:55:21PM -0800, John Todd
wrote:
> Well, asterisk appears to be trying to "REGISTER" with one of my 
> ATA-186's, which is clearly not a Good Thing.  Somehow, * has swapped 
> some IP address information somewhere in it's little head. 
I've seen this happen too; Asterisk will register itself with a SIP ITSP 
correctly for a few days, then for some reason the ITSP's address will get 
replaced with the address of one of my SIP devices.

Unfortunately I don't have enough time to track down this bug, and I've 
disabled all my register= lines since they seem to cause random crashes 
(presumably due to problems with the scheduler...).  -Nathan

-- 
*** Help filter spam!  PGP-sign your email.
*** Expand your PGP Web of Trust with http://www.biglumber.com/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 232 bytes
Desc: not available
URL:
<http://lists.digium.com/pipermail/asterisk-users/attachments/20030223/023cdfe0/attachment-0001.pgp>