Greetings, previous to the current project im working on ive only ever used either ISDN or SIP for inbound and outbound call connectivity.
The current prospect im looking at is a single site which will be using SIP as the primary VOIP transport, SDSL for Data and ISDN as a backup, configuration of this setup isnt a problem but there is one issue i haven't thought of before.
For example a block of DDI's will be assigned to the incomming SIP trunk's. In this scenario lets say they are the following:
0121 872 0211
0121 872 0212
0121 872 0213
0121 872 0214
0121 872 0215
0121 872 0216
0121 872 0217
Could someone let me know how i would achieve fault tolerance using an ISDN connection should the WAN connection drop by continuing to allow for incomming calls using the existing DDI range as of course the SIP trunk and ISDN connection are two seperate entities.
We would have control of the customer equipment but not the service provider.
Its a tricky one as im unsure how the incomming main number would be switched over to ISDN when the SIP connection drops out.
For example customers may ring 0121 872 0211 as the primary number for the business, this is associated too the SIP trunk, when the WAN connection dies and the SIP trunk is lost how then would the number 0121 872 0211 be transferred switched too the ISDN network transparently whilst the SIP trunk is down?
That is what I was trying to say, you cannot transit the call on ISDN natively because the numbers are different, the only thing you can do is an IASD data backup, but you would need to terminate it in some place that nevers goes down ,and to which you ITSP can reroute SIP calls.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...