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.
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
I use webdav. I found the issue. i have nat beetween ctm and exchange. ctm address, 192.168.15.21 is translated in 192.168.150.243. 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 ( 192.168.150.243 ), but i found the notification was sent with destination address 220.127.116.11 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 ?
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?
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 accordingly.
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 18.104.22.168 for example. In this case 22.214.171.124 is the real ip address of the CTS Manager but it has been nat'd to another ip address for example 126.96.36.199 on the firewall. Because the Exchange Event Subscriber is saying send notifications back to 188.8.131.52 but it's nat'd ip address is 184.108.40.206, 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.
I'm not able to access my old voice mail messages all of a sudden. The recording says something like 'the message is currently not available'. This has never happened before in all the years I have been using this system. I have t...
If you have 2 ISR routers, one acting as Failover, do we need to have both the same number of SRST licenses on the 2 routers?
No. You will only need the SRST licenses on the primary router. Because this feature...
You have reached the Cisco Logistics Support Center.. To Check Status of your RMA, visit Product Returns & Replacements (RMA).
Need help? Contact us by Phone or Email.
Phone: 1800 553 2447 Option 4