I've been working on deploying a SME to migrate us off our h.323 gatekeeper voice and video infrastructure to SIP. I'm running into issues with the SIP trunk going from the SME to the VCS-C for video calls going to the VCS-E. When ever I place a call from a 9951 registered to a CUCM cluster route the call to the SME in order to get to the VCS-C&E the SME is staying in the signaling path. When ever I go and look in the VCS-C the source of the call shows up at 123XXXX@ip address of the SME. Anyone else have this problem or have any idea as to how to fix it?
Is that causing a problem? Maybe there is a translation in the SME that can adjust the originating address or a translation in the VCS-C that can remove/replace the @ipaddress.
Learn, share, save
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
