I am currently designing two voip sites in the same city. Each one has its own T1 pri trunk to PSTN. For incoming calls, is it possible to virtual-bundle them together to do load balancing? ( they are around 10 miles away from each other physically.) Also if it is, can it do it with number preference? Say, site A has local range 416-555-2000 to 3000, and site B has local range 416-555-4000 to 5000. I would prefer A over B to receive 2000 to 3000, but B over A to receive 4000 to 5000. Do we have that option from carrier?
I know it is a question for service provider. I am just wondering if anyone using this service from their local telecom carrier?
If you want to have inbound calls treated the same (sharing the T1s) the carrier would need to be able to link the T1s together for inbound calls. This is done through the local telco switch. If the same serving switch (central office) is used to provide the T1s they can be combined to the same route index, which would allow the telco to sieze trunks from either low to high (in order of the trunk members), or high to low, depending on how they do it in your area. The telco will be the glare master, which means if a call outbound and a call inbound attempt to sieze the same trunk the telco wins and the outbound call backs off based on a preset algorithm to attempt completion on a different channel.
If the T1s are serverd from different telco switches you would need to check with them to see if they can extend one to the other's serving switch (this can sometimes be done at additional cost to the customer).
You can create a route group and route list in the CCM cluster that contains both T1s and order them based on which is first in the hunting from the telco end. All users can share the route list, or you can specify overflow.
Remember that telco network timing signals will be sent on the first T1 if they are combined on one route index.
The route index in the telco switch is a pointer to the trunk group(s) that serve you. Most service providers can have up to 60 T1/PRIs in a trunk group, depending on the end office type - 5ESS, DMS100/200/500, Ericsson, etc. The DIDs are pointed to the route index which allows completion to your inbound gateways.
LNP can accomodate most 10 digit numbers in a LATA (local access transport area). If you are intraLATA the telco should be able to port your DIDs with little or no trouble. Long distance toll charges are usually the only show stopper, and at 10 miles between your host and remote sites I would not imagine this is an issue for you.
I'm not able to access my old voice mail messages all of a sudden. The recording says something like 'the message is currently not available'. This has never happened before in all the years I have been using this system. I have t...
If you have 2 ISR routers, one acting as Failover, do we need to have both the same number of SRST licenses on the 2 routers?
No. You will only need the SRST licenses on the primary router. Because this feature...
You have reached the Cisco Logistics Support Center.. To Check Status of your RMA, visit Product Returns & Replacements (RMA).
Need help? Contact us by Phone or Email.
Phone: 1800 553 2447 Option 4