[cisco-voip] Mobile Connect (Single Number Reach)

[Nate VanMaren]

\+.@ or \+.1[2-9]XX[2-9]XXXXXX

Just do it as a translation pattern that turns it into your normal 9.1[2-9]XX[2-9]XXXXXX

-Nate

-----Original Message-----
From: michael.p.king at gmail.com [mailto:michael.p.king at gmail.com] On Behalf Of Mike King
Sent: Thursday, December 09, 2010 2:09 PM
To: Nate VanMaren
Cc: Cisco VoIPoE List
Subject: Re: [cisco-voip] Mobile Connect (Single Number Reach)

That should be

9+1XXXXXXXXXX

On Thu, Dec 9, 2010 at 4:09 PM, Mike King <me at mpking.com> wrote:
> How do you put that in?
>
> 0+1XXXXXXXXXX
>
> On Thu, Dec 9, 2010 at 4:06 PM, Nate VanMaren <VanMarenNP at ldschurch.org> wrote:
>> If it's LD we have a +1 pattern too. :)
>>
>> -----Original Message-----
>> From: michael.p.king at gmail.com [mailto:michael.p.king at gmail.com] On Behalf Of Mike King
>> Sent: Thursday, December 09, 2010 2:02 PM
>> To: Nate VanMaren
>> Cc: Cisco VoIPoE List
>> Subject: Re: [cisco-voip] Mobile Connect (Single Number Reach)
>>
>> On Thu, Dec 9, 2010 at 3:55 PM, Nate VanMaren <VanMarenNP at ldschurch.org> wrote:
>>> Mike,
>>>
>>> The rule is exact match causes the problem.  So we have our system setup to route the call properly regardless of the way the user dials it, so 918015551212 and 98015551212 call the same way.
>>>
>>> Also to match inbound anchoring you do it like 8015551212 if that is the caller id you get from the carrier.  It seems to use application dial rules to route the call.
>>>
>>> That is a few options.
>>>
>>> -Nate
>>>
>>
>> That is so cool.  Unfortunately, "De De DA To complete calls beyond
>> your calling area, you must dial a 1......."
>>
>>
>>  NOTICE: This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.
>>
>>
>>
>