NortelGuy1979
Programmer
Hello,
We are working on a CS1000M running 5.0, connected via SIP to two other CS1000's (an E and an M, running 5.5) so we have an existing SIP service domain.
As a new project, we are wanting to add new SIP trunking to an Avaya S8720. The SIP service domain is *different* than our existing SIP service domain.
We had no problem adding the Avaya endpoint to our NRS as a static SIP endpoint, and adding routing entries as private.cdp (per an integration doc we have from the old Avaya). However, we cannot make calls in either direction.
We are in the process of obtaining PCAP traces on both sides, but in the mean time, the question has arisen if we need to have a separate signaling in a new telephony node, and new SIP domain (to match the Avaya S8720), and build a separate DCH / RDB / SIP trunks (and VGW's) for this setup.
Neither "Nortel" ETAS nor Avaya Professional Services seems to have a clear answer.
Anyone done anything similar to this?
Thanks,
Matthew
Matthew - Technical Support Engineer
We are working on a CS1000M running 5.0, connected via SIP to two other CS1000's (an E and an M, running 5.5) so we have an existing SIP service domain.
As a new project, we are wanting to add new SIP trunking to an Avaya S8720. The SIP service domain is *different* than our existing SIP service domain.
We had no problem adding the Avaya endpoint to our NRS as a static SIP endpoint, and adding routing entries as private.cdp (per an integration doc we have from the old Avaya). However, we cannot make calls in either direction.
We are in the process of obtaining PCAP traces on both sides, but in the mean time, the question has arisen if we need to have a separate signaling in a new telephony node, and new SIP domain (to match the Avaya S8720), and build a separate DCH / RDB / SIP trunks (and VGW's) for this setup.
Neither "Nortel" ETAS nor Avaya Professional Services seems to have a clear answer.
Anyone done anything similar to this?
Thanks,
Matthew
Matthew - Technical Support Engineer