Tony, your instructions worked perfectly. Implemented the changes last night and all dialing works as needed, including the +1 missed calls from the handset. Thanks!
Ly Tran From: Tony Graziano [mailto:tgrazi...@myitdepartment.net] Sent: Wednesday, May 19, 2010 10:44 AM To: Tran, Ly V. Cc: Gerald Harper; sipx-users@list.sipfoundry.org Subject: Re: [sipx-users] +1 Dialing ITSP with incoming +1 Caller ID Problem I understand. EVEN if you are using siptrunking, making a dial plan change during working hours will not disrupt any in progress calls (only proxy and registrar are reloaded). This type of change is designed to be flexible and implemented during the work day. If you were making a change to the trunking service itself, using the internal SBC, that would pose a different result of services to be restarted, and would tear down calls in progress to the itsp. On Wed, May 19, 2010 at 11:40 AM, Tran, Ly V. <lt...@rrtgi.com> wrote: Thanks Tony, I believe this should solve our problem and will configure it as shown in your document. Can't do now during business hours, but will later this evening. Ly Tran From: Tony Graziano [mailto:tgrazi...@myitdepartment.net] Sent: Wednesday, May 19, 2010 10:26 AM To: Gerald Harper Cc: Tran, Ly V.; sipx-users@list.sipfoundry.org Subject: Re: [sipx-users] +1 Dialing ITSP with incoming +1 Caller ID Problem I think you miss his point. Dialing from the "missed calls" on the handset shows the +1 (and 10 digits) on the display. The outbound call fails because +1 is ALSO being added at the gateway. Not all carriers do this, not all phones display the +1 properly either. His question is a simple one, and in this case has a simple answer, but not everyone encounters it. In his case, a dial plan rule to see "+1" and <10digits> needs to strip the <+1> and send the matching suffix to the gateway, which will add it back, but not DUPLICATE it showing "+1+1<10digits>". I sent him a link to a document I drafted some time ago, and explains it simply. This is the approach he needs to implement. No changes on handset dialing plans or gateways is needed. It's a standard way we implement things when a carrier is used that sends the "+1" if we don't use an SBC that can strip this. At the same time, the document shows a streamlines dial plan entry when using a carrier who sends the "+1" character to allow 7 digit local dialing, etc. "This_always_works." On Wed, May 19, 2010 at 11:16 AM, Gerald Harper <ger...@sustaa.com> wrote: Have you tired creating a 1+XXX the XXX being local area codes and have the resulting call drop the 1? Then if a person dials 1 or not for a local call it would go through. ie: for greater Vancouver: Prefix = 1604 and 7 digits Resulting call = dial 604 and append matched suffix Prefix = 1778 and 7 digits Resulting call = dial 778 and append matched suffix The when your gateway inserts the one again, all is good! From: Tran, Ly V. <mailto:lt...@rrtgi.com> Sent: Wednesday, May 19, 2010 7:35 AM To: sipx-users@list.sipfoundry.org Subject: [sipx-users] +1 Dialing ITSP with incoming +1 Caller ID Problem We have a minor problem with the setup with our current ITSP that uses +1 as the prefix. The way we have it configured now is that we have +1 as the prefix on the gateway for this ITSP. Our dial plan is 10 digits for all calls, -local, LD and Toll Free. The problem we have is all the incoming Caller IDs shows +1-xxx-xxx-xxxx. We have LG-Nortel 6812 phones, that has the Call Log feature to see the incoming, missed and called numbers and dial those numbers listed. In the missed calls, we can select the number on the phone and press dial. However, the call is not successful because it is listed with the +1 which is already being appended at the gateway. Anyway to work around this? Ly Tran ________________________________ _______________________________________________ sipx-users mailing list sipx-users@list.sipfoundry.org 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/ _______________________________________________ sipx-users mailing list sipx-users@list.sipfoundry.org 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 sip: tgrazi...@voice.myitdepartment.net Fax: 434.984.8431 Email: tgrazi...@myitdepartment.net LAN/Telephony/Security and Control Systems Helpdesk: Telephone: 434.984.8426 sip: helpd...@voice.myitdepartment.net 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 sip: tgrazi...@voice.myitdepartment.net Fax: 434.984.8431 Email: tgrazi...@myitdepartment.net LAN/Telephony/Security and Control Systems Helpdesk: Telephone: 434.984.8426 sip: helpd...@voice.myitdepartment.net 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 sipx-users@list.sipfoundry.org 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/
