Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Converting 1 SIP carrier to another

hebegb41

Technical User
Aug 28, 2008
86
US
I have a SIP CM 10.2 with Sys Mgr and 2 Session Mgrs. We currently have Verizon as our SIP carrier and we had a contractor install a separate carrier as a back up to Verizon. Now the cust wants to convert to that carrier permanently and eliminate Verizon altogether. I know the "new" carrier has an entity and entity link built in the Session Mgrs. They did it so that they could easily "roll" between the 2 carriers if needed. That particular contractor is no longer available for the conversion so they left it to me. I am not an expert here so I need to know if the conversion is as easy as just "denying new service" to the old Verizon entity and "allowing service" to the new carrier entity links. Could anyone here give me the bullet point areas I need to touch if not just denying/allowing service. And I shouldn't need to touch the CM at all I believe (please feel free to smack me in the head there if incorrect)
All of the IP and info for the new carrier is in the system. I just don't know all the areas I may need to touch to convert them....the new carrier is porting all of their DID's to them from Verizon and I need to change the Avaya end.
 
I would highly recommend engaging a BP or another person who does know these products well -- hands on is the only reliable analysis.

A few bullet points?
  • Gain understanding of
    • your session and server flows in the ASBCE (and the many associated objects and settings)
    • your "Routing" section in System Manager -- this controls the flows in and out of the ASM
    • your CM trunk-groups,
    • the order in which outbound calls (route pattern, TG, ars etc) and inbound calls are processed in CM (ports, domains etc)

From here you can make a determination of how deny new service will play out and what it will take to roll the carriers over.

Ideally both systems are online at the same time and then you change a routing decision somewhere to take the new path instead of the old path. This allows easiest roll back and most opportunity to test the links.
 

Part and Inventory Search

Sponsor

Back
Top