I would be interested in seeing the configuration posted in a previous thread outlining a successful Cisco to Genesys implementation.
I am setting up a Cisco ip2ip gateway to work in conjunction with the Genesys auto answer feature. While I am slightly baffled at what is happening there, seeing a standardized config would help considerably. I am sure there is some setting that would greatly aid in the implementation. I would be happy to post my config if it would help.
Attached are the sip messages related to the auto answer.
It appears as if it sends a notify to the Cisco device, but the Cisco responds with SIP/2.0 489 Bad Event - Malformed/Unsupported Event.
Is there anything that can be done to support the subscribe / notify that is being received from the Genesys?
489 is indeed a response to a subscription request or notification containing an Event package that is unknown or not supported. It's also used to reject subscription requests that do not specify an Event package at all.
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...