I SUSPECT that ISN dialing needs to be directly and specifically
supported in the dial plan, because:
if a third party, dials a DID*ITAD, and that DID isn't local to the sipx
server, and it matches one of the 'normal' dial plans, the call will be
redirected to the ITSP.
I think you can mitigate this by not using wildcard ISN DNS, or restrict it.
an example: anyone with ISN outbound dialing enabled: this should
work: (will get our AA)
ISN: 5000*1300
(our ITAD is 1300)
HOWEVER, I just dialed (mycell phone)*1300 from the office, and it went
out the ITSP.
before I restrict the DNS NAPTR wildcard to extensions only, someone
tell me I am wrong.
(and, yes +1 for having this in the dial plan and not in 'servers')
--
Michael Scheidell, CTO
Phone: 561-999-5000, x 1259
> *| *SECNAP Network Security Corporation
* Certified SNORT Integrator
* 2008-9 Hot Company Award Winner, World Executive Alliance
* Five-Star Partner Program 2009, VARBusiness
* Best in Email Security,2010: Network Products Guide
* King of Spam Filters, SC Magazine 2008
______________________________________________________________________
This email has been scanned and certified safe by SpammerTrap(r).
For Information please see http://www.secnap.com/products/spammertrap/
______________________________________________________________________
_______________________________________________
sipx-users mailing list [email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
sipXecs IP PBX -- http://www.sipfoundry.org/
