Gus,Thats the problem I have a dynamic IP on my side which is why I need the "register" line in the iax.conf..
There is nothing to it really register lines are pretty simple..
register => user1:[EMAIL PROTECTED] register => user2:[EMAIL PROTECTED]
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:[EMAIL PROTECTED]/${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
iax2 debug shows that it is registering the first line but not the second..
Later..
_______________________________________________ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
