Answered by:
problem with OCS - CUCM 6.1

Question
-
Hello everybody,
I am having problems with the integration of OCS and CUCM6. I have the following scenario:
Cisco CallManager6.1 [10.56.1.1] <---------> [10.56.1.3] MEDIATOR [10.56.1.5] <--------------->OCS [10.56.1.10]
And I was able to make calls from OCS ---> CUCM, but not CUCM -> Mediator -> OCS. The error is as follows:
Source Destination Protocol Info
10.56.1.1 10.56.1.5 SIP/SDP Request: INVITE sip:1563@10.56.1.3:5060, with session description
...
10.56.1.5 10.56.1.1 ICMP Destination unreachable (Port unreachable)
...
Finally, indicate that all machines are virtualized with vmware.
Any idea?
Thank's.Wednesday, November 19, 2008 6:34 PM
Answers
-
Solved!
The problem is the security option for sip trunk configuration in CallManager. By default listens on TCP port 5060 but must be put in UDP.
This is done from "System> Security Profile> SIP Trunk Security Profile".
Thank you all.
A greeting.
Jesus MartinezTuesday, December 9, 2008 9:52 AM
All replies
-
Hve you seen this article?
http://communicationsserverteam.com/archive/2008/09/30/302.aspx
Your CUCM 6.1 should actually connect to IP 10.56.1.3 and not to 10.56.1.5
10.56.1.3 listens on 5060
10.56.1.5 listens on 5061
Wednesday, November 19, 2008 9:53 PM -
Sorry,
It has been a failure to write in the forum, communication with the CUCM is always through the address 10.56.1.3.
Currently, the mediation server has 2 interfaces, one to talk to the CUCM and one with the OCS.
I followed all the correct steps to create the trunk with the CallManager, configuration of the mediator and the front-end of the OCS.
Also, when I make a call from OCS-> CUCM, but the call sounds when you answer the call ends with error.
Thanks for the help.
A greeting.Thursday, November 20, 2008 8:49 AM -
Hi,
So your signalling works well but you dont have the voice or RTP stream. If you look at the client side for logging - do you see any port errors?
Check if there are any firewall issues - I assume not. I think that the packet is being sent to the incorrect port - maybe you see port 0 being used? Port 0 should not be used and therefore the remote host correctly responds with an ICMP destination port unreachable message.
The ports and IP addresses specified in the Session Description (SD) portion of the SIP message. Ensure that the remote party will be able to connect to both the IP address and the port specified.
Regards
Anesh
Thursday, December 4, 2008 2:44 PM -
Solved!
The problem is the security option for sip trunk configuration in CallManager. By default listens on TCP port 5060 but must be put in UDP.
This is done from "System> Security Profile> SIP Trunk Security Profile".
Thank you all.
A greeting.
Jesus MartinezTuesday, December 9, 2008 9:52 AM -
Mediation Server will only connect over TCP not UDPTuesday, December 9, 2008 10:00 PM
-
Sorry, I wrote wrong.
A greeting.Sunday, December 14, 2008 4:23 PM -
Good morning!
So you have solved a problem? If yes, as?
At me too a problem with integration.
Calls with Microsoft Office Communicator 2007 do not go on IP phones.
SIP a trunk like did under the instruction. But it why that does not rise.- Proposed as answer by Cherry3010 Wednesday, February 18, 2009 6:03 AM
Monday, February 16, 2009 7:37 AM -
Hi,
Agreed with Deli, the mediation server does nothing with UDP.
Regards
Anesh
AneshMonday, March 16, 2009 3:23 PM