Cisco Support Community
Showing results for 
Search instead for 
Did you mean: 
New Member

event notification beetween exchange and ctsm

dear all,

I migrated exchange serveur, 2003 to 2007. All are ok excep the event notification. This occur on udp port 3621 and sent by exchange server when there is a new meeting in a room. How ctsm subscribe to this exchange service ? In exchange 2007 there is a modification with this service ?

At present, when there is a new meeting, l do a manual synchro and the meeting appear in the ctsm.

Is anybody meet this issue ?



Re: event notification beetween exchange and ctsm

Are you using Webdav or EWS?

For Webdav you are correct we use UDP3261


Subscription will happen when CTM starts and synch with exchange, In case of Webdav

CTM will send a "SUBSCRIBE" request to the exchange server
for the usersr  mailbox in order to recieve notifications, if this subcription is succesfull we should recieve indication of an event change from Exchange

You can see if theres a FW in the middle or check also Exchange Event viewer for any errors

New Member

Re: event notification beetween exchange and ctsm

Thank for your reply.

I use webdav. I found the issue. i have nat beetween ctm and exchange. ctm address, is translated in Nat is static.

On the exchange server there are 2 interfaces, one in telepresence vpn and the other, witch is the default, to manage it.

I expected to see the notification with destination address, the translated address ( ), but i found the notification was sent with destination address witch isn't the translated address so the notification left to the wrong interface.

I don't know why this happen ? Is the correct functionnaly ?

New Member

Re: event notification beetween exchange and ctsm

My question is how does Exchange know to respond to CTS Manager on udp port 3621?   Udp port 3621 is an Epson port.  Does the subscribe notification during the webdav process tell the Exchange server to notify the user that was created for CTS Manager to connect to Exchange and listen on UDP port 3621 for mailbox notifications?

New Member

Re: event notification beetween exchange and ctsm

You are correct . But this is per design. Exchange send Notification to CTS Man on UDP port 3621.
CTS-Manager listening on UDP port 3621

Cisco TelePresence Firewall and Access List Considerations :

When the CTSMan server starts, CTSMan will use the CTSMan super user configured on the
Microsoft Exchange in the field "SMTP LHS" to subscribe to all the TP rooms that CTSMan
discovered from the appuser in CUCM.  To "subscribe" to the TP rooms accounts means the
CTSMan super user is allowed to listen on the UDP port 3621 for any event happened to the
TP room account's calendar.

When a TP room is invited by a scheduler in a meeting, the invitation email arrives on the
room mailbox.  When the invite is accepted (either manually by someone login to the room
account, or by auto accept agent), the meeting is placed on the room calendar.  At this
time, the room calendar has a change event happened.  Exchange server will trigger an
event notification on UDP port 3621.  An event will be triggered whenever there is a
change on the room calendars, whether it is meeting creation, meeting modification, or
meeting deletion.

Upon receiving the event on UDP port 3621, CTSMan learns that there is something it needs
to act upon.  Depending on the event type, CTSMan will query Exchange to get necessary
information of the meeting involves the TP rooms account from Exchange and process it

You can get more details from the following link:

New Member

Re: event notification beetween exchange and ctsm

Concerning your question : At present, when there is a new meeting, l do a manual synchro and the meeting appear in the ctsm.

[Answer] : If manual synch works successfully [Done via TCP port 80] and automatic doesn't , means UDP port 3621 isn't open between
Exchange server and CTS-Manager.

New Member

Re: event notification beetween exchange and ctsm

Actually it is open.  Here is what seems to be the issue that the firewall cannot nat the ip address of the CTS Manager to a different IP address than what is in the invitation from the CTS Manager or the Exchange server will not have a route to for example.  In this case is the real ip address of the CTS Manager but it has been nat'd to another ip address for example on the firewall.   Because the Exchange Event Subscriber is saying send notifications back to but it's nat'd ip address is, the network doesn't know where to send it.  Nothing in the documentation says you can't NAT the CTS Manager.  They actually show examples of the CTS Manager on the other side of a firewall but nothing says you can't have the firewall in between the CTS Manager and the customer's Exchange server with nat'd ip addresses.   I have looked and opened a TAC case too.

18 Nov 2010 18:40:22,189 [GA-EAInternalEventThreadPool-Thread-1] events.ExchangeEventSubscriber - Subscription success for roomSerialId=[1]; roomName=[]; callback=[httpu://]; id=[1]; path=[]; displayName=[Telepresence  New Jersey]

CreatePlease to create content