________________________________________ From: [email protected] [[email protected]] On Behalf Of Michael Scheidell [[email protected]]
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. ________________________________ Heh... What is the problem? You dialed, from your office phone, XXX XXX XXXX *1300. It is parsed as an ISN call, the mapping is processed, and the call is presented to your proxy again as a call to XXX XXX XXXX. That number is processed as an outgoing call and checked for outgoing call permission -- which the call has, since you dialed it from your office phone. So the call is sent to your ITSP. (Permissions do not control what the dialed number *means*, but they do control whether the caller is permitted to carry out a call with that meaning.) Dale _______________________________________________ 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/
