Ingate. On Fri, Apr 2, 2010 at 11:05 AM, McIlvin, Don <[email protected]>wrote:
> Certainly, having remote survivable offices is a great addition (I voted > for it). > > But I don’t see how it would solve the call routing issue I have (number > overlap on remaining digits after truncation of delivered digits from ITSP). > > > > What is the independent SBC you use to strip and then add digits? > > > > Don > > > > *From:* Tony Graziano [mailto:[email protected]] > *Sent:* Friday, April 02, 2010 10:46 AM > > *To:* McIlvin, Don > *Cc:* [email protected] > *Subject:* Re: [sipx-users] Improvement to Customized Dialplan > > > > I see. We do this here with an independent SBC that can strip digits on > inbound calls using its own dialplan. > > > > At the same time there is a "branch" feature in 4.1.x (development). Have > you looked at that? > > > > Here's one of the relevant tracker items... > > > > http://track.sipfoundry.org/browse/XX-4819 > > > > This might well address that for you. > > On Fri, Apr 2, 2010 at 10:30 AM, McIlvin, Don < > [email protected]> wrote: > > We have one sipx system that interfaces to two ITSPs. > > > > This is for inbound calls to DIDs. > > > > *From:* Tony Graziano [mailto:[email protected]] > *Sent:* Friday, April 02, 2010 10:11 AM > *To:* McIlvin, Don > *Cc:* [email protected] > *Subject:* Re: [sipx-users] Improvement to Customized Dialplan > > > > But you can do this already, with a custom dialplan... > > > > create a siptrunk to the other sipx system, create a dialplan that says if > prefix is 12 and 2 digits, then send all 4 digits to the siptrunk. > > > > 4 digit dialing between offices, bypassing itsp or pstn. > > On Fri, Apr 2, 2010 at 10:07 AM, McIlvin, Don < > [email protected]> wrote: > > I entered an idea for improvement to the customized Dial plan capabilities. > > > > The existing capability allows truncation of delivered digits from the > ITSP. > > > > The improvement is allow adding digits in front of the remaining digits > after truncation. > > > > http://track.sipfoundry.org/browse/XX-7935 > > > > This solves the problem where, with multiple locations, there is an overlap > on the last four digits after truncation. > > > > Example; location A has DID set 781-123-(1200 to 1299) > > Location B has DID set 617-123-(1200 to 1299) > > Location B also has set 617-456-(1300 to 1399) > > Location C has DID set 781-456 –(1800 to 1899) > > > > If you truncate the first six or even just the first three there is a DID > overlap on the last 4 between Location A and Location B. > > If your extension plan (User-ID) became 7 digits mapping to DID exchange > for the first three, you still can have over laps. > > > > A solution is to have a dial plan where Location A has extensions 100nnnn, > Location B has extensions 200nnnn, and Location C has extensions 300nnnn. > > > > To make this work in a customized dial plan, you would truncate the first > six, and then add back the 3 digits for your internal Location designation. > > > > So inbound calls to 781-123-1200, become 1001200. > > Inbound calls to 617-123-1210 become 2001210. > > Inbound calls to 617-456-1325 become 2001325. > > Inbound calls to 781-456-1835 become 3001835. > > > > All this would take is an additional text box for added digits that are > inserted in front of the remaining digits after truncation. > > > > Our various locations are on an internal WAN, where the topology has two > large connections in separate locations to two ITSPs. > > > > Regards, > > Don McIlvin > > > > Telecom Department > > Realogy/Coldwell Banker > > 1601 Trapelo Rd. > > Waltham, MA 02451 > > Office 781-684-5669 > > > > > > > > "The information in this electronic mail message is the sender's > confidential business and may be legally privileged. It is intended solely > for the addressee(s). Access to this internet electronic mail message by > anyone else is unauthorized. If you are not the intended recipient, any > disclosure, copying, distribution or any action taken or omitted to be taken > in reliance on it is prohibited and may be unlawful." > > > > "The sender believes that this E-mail and any attachments were free of any > virus, worm, Trojan horse, and/or malicious code when sent. This message and > its attachments could have been infected during transmission. By reading the > message and opening any attachments, the recipient accepts full > responsibility for taking protective and remedial action about viruses and > other defects. The sender's employer is not liable for any loss or damage > arising in any way from this message or its attachments." [v1.0.07.109] > > > _______________________________________________ > 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/ > > > > > -- > ====================== > Tony Graziano, Manager > Telephone: 434.984.8430 > Fax: 434.984.8431 > > Email: [email protected] > > LAN/Telephony/Security and Control Systems Helpdesk: > Telephone: 434.984.8426 > 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. > > > > > -- > ====================== > Tony Graziano, Manager > Telephone: 434.984.8430 > Fax: 434.984.8431 > > Email: [email protected] > > LAN/Telephony/Security and Control Systems Helpdesk: > Telephone: 434.984.8426 > 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. > -- ====================== Tony Graziano, Manager Telephone: 434.984.8430 Fax: 434.984.8431 Email: [email protected] LAN/Telephony/Security and Control Systems Helpdesk: Telephone: 434.984.8426 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-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/
