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

[Nate VanMaren]

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

-----Original Message-----
From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Mike King
Sent: Thursday, December 09, 2010 1:09 PM
To: Cisco VoIPoE List
Subject: [cisco-voip] Mobile Connect (Single Number Reach)

I have a request to do Single Number Reach, but on a weird schedule.
7am-9am, and 6pm-10pm

I tried to setup two remote destinations for one profile, but the
system balked, telling the destination number had already been used
(Was duplicate)


Is there some elegant way to pull this off?   I'm sure I could do it
with a translation pattern, which is fine for a one off.  But I see
this request becoming common, and would rather not have to make this a
manual process of them calling me to set this up.

Mike
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip


 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.