Solved: CER transition from conventional to redsky intrado

Keith Abbott · ‎06-15-2023

Good Day,

We are in the process of switching from our established conventional ERLs in CER, to Redsky using Intrado.
(Redsky will be via SIP trunk rather than PSTN)

I have a couple of 'safety valve' questions before I break something in a regrettable way.

First - Id like to verify that creating an intrado route pattern will not break my conventional ERLs - can anyone verify that for me?

Second - Im trying to figure out a way I can 'pre-populate' our existing ERLs into redsky (presumably using the migration tool) while keeping our conventional ERLs active. Id guess I have to create a duplicate ERL with different ELIN - and migrate that? any other ideas?

Thirdly - how can I set up the call manager side so I can test calls to redsky - while maintaining conventional ERLs for everyone but the testers - I presume I could configure a separate Emergency CSS (Emerg-Redsky ie) - but a 911 call will still route to CER and get treated - and still come back to CM as normal 911 that routes to the carrier rather than redsky.
Any Ideas?

Thanks for any help you can provide
W

TechLvr · ‎06-15-2023

1. Creating an Intrado route pattern alone in CER does not impact anything.

2. Check out link below for Conventional ERL to Intrado ERL migration
https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cer/10_0_1/english/administration/guide/CER0_BK_CA66317A_00_cisco-emergency-responder-administration-10_0/CER0_BK_CA66317A_00_cisco-emergency-responder-administration-10_0_chapter_0101.pdf

3. You do not need a separate CSS to test Redsky in your scenario. Here is what you need to do.
In CER, create an Intrado Route Pattern, let's say 1111.911. Next, create an Intrado ERL and select 1111.911 for route pattern under the drop down list then enter your ELIN in the ELIN field. Next, I suggest you assign a test phone or a few test phones manually to this ERL for testing. You could also use the