[cisco-voip] Prefix for Missed Calls
Heim, Dennis
Dennis.Heim at wwt.com
Thu Sep 12 10:42:59 EDT 2013
If you have transformation patterns, you should use them.
At the ingress gateway you append the necessary digits, a 9 or 91, based on the CSS. On the phone you use the calling party transformation, to have a css that contains a partition that has a transformation pattern that will strip off the necessary digits, like 9, 91, from the display of the phone.
If you need more details let me know. This will make it so when the call comes in you see the 10 digits, and when you hit the missed calls directory the 9 or 91 or already populated.
Dennis Heim | Solution Architect (Collaboration)
World Wide Technology, Inc. | 314-212-1814
PS Engineering: Innovate & Ignite.
From: cisco-voip [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Haas, Neal
Sent: Thursday, September 12, 2013 7:38 AM
To: Lisa Notarianni; cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Prefix for Missed Calls
No, I tried to work on this same area for several months but never did anything except for create overlapping dial plans.
I was told the easiest thing to do was to create a phone service that would take care of this for you. I have never had time to look into this.
Neal Haas
From: cisco-voip [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Lisa Notarianni
Sent: Thursday, September 12, 2013 7:31 AM
To: cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
Subject: [cisco-voip] Prefix for Missed Calls
(Call Manager 8.6.6)
Has anyone ever successfully utilized translation patterns to prefix 91 so that when Dial is pressed in Missed or Received Calls, it will automatically populate the 91 for calls that were missed or received from outside of network callers?
We had done some testing but it caused an overlap in route patterns which therefore caused a timeout delay for internal calling.
Here is what we built:
{2-9]xx xxx xxxx would automatically add 91 prefix
[2-9]xxx Is for internal calling
If an internal call was made for example to 4357, Call Manager would wait to see if the caller was done dialing and after about 15 seconds it would time out and then the call would go through. The system was comparing the 2 route patterns above and was not sure which was being used which caused the delay.
I know there are other suggested ways of accomplishing this but if there is a workaround to Cisco’s preferred way of showing 91 prefix on each incoming call we would rather that.
Thank you in advance.
Lisa
[cid:image001.gif at 01CEAF8B.B3FB9F50]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20130912/453039e2/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.gif
Type: image/gif
Size: 10828 bytes
Desc: image001.gif
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20130912/453039e2/attachment.gif>
More information about the cisco-voip
mailing list