John Todd said:
Robert - IAX as a protocol is completely dependent on the far-end gateway, and not on any specifications you can change. All the gateways at the moment only support SIP; none support IAX or IAX2, though hopefully that will change since some of them are actually running Asterisk as the media gateway.
As soon as they offer IAX in addition to SIP, then we'll also need to re-examine the way that Asterisk handles ENUM lookups since currently only one NAPTR is handed back to the dialplan. For those nations that have multiple gateways or providers, I have put all the entries in a round-robin fashion so that the answers will be rotated by most standard DNS resolver libraries. However, this quickly becomes unworkable with multiple responses with different protocols, and there is already a "preference" factor built into NAPTR records that should be accessible from the dialplan when an EnumLookup is returned.
Anyone want to take a swing at it? Otmar? :-)
JT
John, Thanks for the info. I'll leave the code commented out in the dialplan. If I put in the NAT SIP patch then will reenable it. Is an interesting concept for some long snowy night reading!
You might as well leave the code in there, and just make the GotoIf statement look only at IAX as a comparison. Things may magically start to work someday, and you'll never even notice it. :-) If your resolver chain is in working order, it only adds ~1/5 of a second or so (maybe less) to the dial process.
JT _______________________________________________ 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
