11-26-2012 06:23 AM - edited 03-19-2019 05:55 AM
Hi all--I'm looking at potentially having to change the integration method of my Unity Connection deployment from SCCP to SIP to address an issue with caller-id showing up incorrectly and preventing users from simply tapping the number on the SMTP notification on their smartphones. My question is how painful is it going to be to change integration types, and are there any major risks or gotchas that we need to be aware of before we move forward with the change?
thanks all
SJ
Solved! Go to Solution.
11-26-2012 08:36 AM
This is not challenging at all, simply delete current integration on CUCM and UCXN completely i.e. on CUCM:
VM hunt pilot/hunt lists/line groups/SCCP ports
and VM ports and port group in UCXN
then follow the SIP integration guide to build new integration, i.e.
CUCM:
SIP trunks
Route Patterns/Route Lists/Route Groups
UCXN:
port groups (SIP)
ports
HTH,
Chris
11-26-2012 08:36 AM
This is not challenging at all, simply delete current integration on CUCM and UCXN completely i.e. on CUCM:
VM hunt pilot/hunt lists/line groups/SCCP ports
and VM ports and port group in UCXN
then follow the SIP integration guide to build new integration, i.e.
CUCM:
SIP trunks
Route Patterns/Route Lists/Route Groups
UCXN:
port groups (SIP)
ports
HTH,
Chris
11-26-2012 08:40 AM
Thanks Chris--kind of thought that would be case, but wanted to confirm there wasn't anything that would come back and bite me later.
Appreciate it!
SJ
09-16-2019 11:47 AM
Chris,
Is the process the same with version 12.5.1? I suspect it is...but never hurts to ask...
Cheers
Paul
02-26-2025 07:44 AM
Yes its the same process
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide