http://article.gmane.org/gmane.comp.telephony.pbx.sipfoundry.general/19404/match=nxx
I hope this explains it easier. Example: Everything in NPA is not local. When receiving callerid (missed or received calls on Polycom, via PRI) we always get "10 digits". We also have another NPA overlay where only certain NXX's are local (7 digit dialing). I need a dialplan to look at the NPA's that are "local" to us, and know whether to send 10 or 7 digits, even though we might send "10" to the proxy. In other words, "when to stip the NPA or not". \\Since there might be dozens, there is not easy way to create such a rule in the dialplan as it now exists. On Tue, Jun 15, 2010 at 12:53 PM, Mossman, Paul (Paul) <[email protected]> wrote: > Tony wrote: >> Hopefully this leads to a more easily crafted dial plan to >> put many nxx's in a custom dialplan to use least cost >> routing. Right now we deal with areas that have dozens of >> nxx's covered under a different local npa, and are dialed >> without the npa under tariff with the lec. >> There's no way to import those, so you have to craft dozens >> one at a time. > > Can you give me a few of these? Include the type and the setting values. I > don't need the Permission and Gateways details. (Assuming of course that > they have at least one Gateway...) > > > -Paul > [email protected] > > -- ====================== Tony Graziano, Manager Telephone: 434.984.8430 sip: [email protected] Fax: 434.984.8431 Email: [email protected] LAN/Telephony/Security and Control Systems Helpdesk: Telephone: 434.984.8426 sip: [email protected] Fax: 434.984.8427 Helpdesk Contract Customers: http://www.myitdepartment.net/gethelp/ Why do mathematicians always confuse Halloween and Christmas? Because 31 Oct = 25 Dec. _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
