[Asterisk-Users] Multiple IAX "register" lines?

Rich Adamson radamson at routers.com
Fri Mar 26 06:36:11 MST 2004


> >>There is nothing to it really register lines are pretty simple..
> >>
> >>register => user1:pass1 at server1.domain1.tld
> >>register => user2:pass2 at server2.domain2.tld
> >>
> >> From the cli "iax2 show registry" only shows the first entry..
> >>
> >>These are for inbound services not outbound, I didn't think it was 
> >>nesesary to "register" for outbound calls because the call is being 
> >>initiated from inside..
> >>    
> >>
> >
> >If the iax destination site is static, you don't even need the registration
> >process. Simply set up a type=user (for inbound iax calls) with some
> >appropriate security parameters (host, secret, context). The associated
> >extensions.conf entry might look something like:
> >  exten => _9.,1,Dial(IAX2/userid:mysecret at 1.2.3.4/${EXTEN:1})
> >which will connect with type=user just fine. Have several of these in 
> >production.
> >
> >Of coarse, if you don't have access/cooperation to the remote iax2 servers,
> >or if any site is using dynamic IP addresses, then your stuck with
> >resolving the original registration problem. (Does a "iax2 debug" show
> >anything useful?)
> >
> >Rich
> >
> >
> >  
> >
> Thats the problem I have a dynamic IP on my side which is why I need the 
> "register" line in the iax.conf..
> 
> iax2 debug shows that it is registering the first line but not the second..

I assume you've tried the easy stuff... separate the two statements with
some additional cf-lf, add a useless/redundant statement in between the two 
registrations, move one of them to the bottom of the config file, 
"database show" to ensure entries are accurate, etc, etc.

(I had a similar problem months ago that involved an incorrect /IAX entry
in the database. If I recall correctly, iaxtel changed IP addresses or
something like that. At that time, I didn't know some of these things were
actually stored in the database, and no one responded on the list to my
question. If I would have simply deleted the database entry (assuming I
knew it was there in the first place), my problem would have been fixed.)

Rich







More information about the asterisk-users mailing list