VG248 - MWI Messages Queued and not sent to CM (3.2)
We are attempting to configure a VG248 to integrate with a BayPoint voicemail. The log in the VG248 shows the MWI messages are being received, and they are queued in the VG248, so we know the SMDI messages are being received and processed, however, they never make it to the CallManager.
All ports are registered and up, as well as the virtual voicemail port, they are all in the same partition, and CSS. We have configured the MWI DN's properly and checked their functionality.
At the same time, the VG248 should toss out an error if the MWI DN's in the VG248 are setup incorrectly, we set them up wrong, on purpose, so we could test if it would throw the error, and it did not.
Something tells me these messages are not reaching call manager.
Re: VG248 - MWI Messages Queued and not sent to CM (3.2)
Further to Justin's post,
When I generate a Lamp on SMDI message into the VG248 ASYNC 1 port (with SMDI and SCCP logging turned on), I see that the message is received (RX 1:OP:MWI 2003!^D) and then an SCCP message is sent to Call Manager (TX: SCCP_OFFHOOK_CALLING_PARTY_NUMBER 2003).
I see this message received on Call Manager in the CCM traces but there is no response back to the VG248. As a result, the LampOn remains queued on the VG248 and it continues to regularly send the same SCCP message in an attempt to send the LampOn message to Call Manager.
I beleive I must have something missconfigured in Call Manager but based on the documentation, can not find anything that I may have missed.
BTW, I'm just using a little app called "SMDI Tester" to generate LampOn and LampOff SMDI messages out of my Com port.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...