Isn't the issue here that remote survivability wouldn't work? I currently have my dial plans set to handle dropping prefixes - but had considered/dreaded putting that on the gateway to enable outbound dialing in the event the phones couldn't reach the sipx server.
-----Original Message----- From: sipx-users-boun...@list.sipfoundry.org [mailto:sipx-users-boun...@list.sipfoundry.org] On Behalf Of Picher, Michael Sent: Wednesday, May 19, 2010 9:46 PM To: Scott Lawrence; sipx-users@list.sipfoundry.org Subject: Re: [sipx-users] +1 Dialing ITSP with incoming +1 Caller ID Problem Yes, this is generally an easier method to manage the system. Keep the gateways as simple and similar as you can (sometimes that is unavoidable... ). -----Original Message----- From: sipx-users-boun...@list.sipfoundry.org [mailto:sipx-users-boun...@list.sipfoundry.org] On Behalf Of Scott Lawrence Sent: Wednesday, May 19, 2010 9:15 PM To: sipx-users@list.sipfoundry.org Subject: Re: [sipx-users] +1 Dialing ITSP with incoming +1 Caller ID Problem On 2010-05-19 11:26, Tony Graziano wrote: > 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>". An even simpler approach is to not make any change to numbers in the gateway and let the proxy do all manipulation of the address. Then it's easy to make a set of rules that covers whatever cases you need, and you only have one place to look to debug any routing problem. _______________________________________________ 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/ This message and any files transmitted with it are intended only for the individual(s) or entity named. If you are not the intended individual(s) or entity named you are hereby notified that any disclosure, copying, distribution or reliance upon its contents is strictly prohibited. If you have received this in error, please notify the sender, delete the original, and destroy all copies. Email transmissions cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. Garrett County Government therefore does not accept any liability for any errors or omissions in the contents of this message, which arise as a result of email transmission. Garrett County Government, 203 South Fourth Street, Courthouse, Oakland, Maryland 21550 www.garrettcounty.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/
