Genesys CTI User Forum
Genesys CTI User Forum => Genesys CTI Technical Discussion => Topic started by: Peter on July 10, 2009, 10:46:12 AM
-
Dear Genesys Experts:
I have noticed a "Contact" UserData field that contains IP address of voice gateway that has received the call. How is this data modified? Is it kept constant or is it updated every time call passed from one site to another?
-
It could be anything at all, since it is designated "UserData"...
If you have access to your Routing, you should be able to find out which variable/constant it is based on - and where it is used/updated, too...
T
-
Hey, Peter,
for Genesys SIP Server, "Contact" field is auto-attached by SIP Server as soon as it detects a new call arriving. Contact field by default contains the URI of where INVITE was sent from, including port and sort of protocol (tcp/udp/tsl)
This information, as far as I know, remains contact through out the life of the call as long as call does not go to a different site. The reasoning behind it is rather simple: stream manager, for example, needs to know the real IP address of where RTP are being sent to. It should be equal to contact-field value of SDP message.
-
Hi Peter,
I've never seen SIP Server adding "Contact" key to UserData automatically. Has not been you SIP Server configured to do so? That feature is called "Mapping SIP Header and SDP Messages".
I don't think that any change of that key will be propagated to SIP messages. Theoretically, it should be possible but I would consider that as very dangerous as you can broke SIP communication that way.
[quote]This information, as far as I know, remains contact through out the life of the call as long as call does not go to a different site. The reasoning behind it is rather simple: stream manager, for example, needs to know the real IP address of where RTP are being sent to. It should be equal to contact-field value of SDP message.[/quote]
Vic, information stored in UserData are not used for SIP communication. For example, Stream Manager is pure SIP client = it doesn't "talk" TLib protocol so it can't read UserData.
R.