[cisco-voip] Hmmm
Nate VanMaren
VanMarenNP at ldschurch.org
Thu Feb 21 16:02:38 EST 2013
She was using +E.164 for MWI on off codes in the SCCP integration.
From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Jason Aarons (AM)
Sent: Thursday, February 21, 2013 1:58 PM
To: cisco-voip (cisco-voip at puck.nether.net)
Subject: [cisco-voip] Hmmm
I thought E164 was supported all around on CXN 9x, but MWI On/Off is supported.
TAC Hot Issues
Symptom: While using CUC 9.x we are able to set the primary extension as E164 and the MWI extension for this user as E164 successfully. What is not being accepted on the admin page is to save the value of the MWI ON and MWI OFF extensions on the port group as E164 extensions, where it should match the MWI on and off that was set on Call Manager for this integration and get the following error "Mwi On Code contains invalid characters"
Conditions: NA
Workaround: Though 9.x release notes say this "Message Waiting Indicator extensions for the Connection System" http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/release/notes/901cucrn.html#wp1562242 Currently we dont support E.164 for MWI ON/OFF codes and is supported only for MWI extensions created for a user under user-->Message Waiting Indicators
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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20130221/024a8d10/attachment.html>
More information about the cisco-voip
mailing list