Using seperate FXO ports on the same H.323 voice gateway
We are using CCM 5.1 and 1 2821 H.323 voice gateway with 2 4FXO cards. There are 8 telephone lines on those fxo cards. We want to seperate fxo ports for the calling number. I mean 16XX extensions will use voice port 1 2 3 4, and 17XX will use 5 6 7 8 for outgoing calls.
We cannot use MGCP cause cannot monitor caller id with mgcp gateway. Does anyone know how to do this? Any parameter or way of restrictions for calling number on router?
Re: Using seperate FXO ports on the same H.323 voice gateway
I have always handled situations like this by setting up seperate Calling Search Spaces for each group of extensions. So have the 16xx group use a 16XX-Outbound CSS and have the 17XX group use a 17XX-Outbound CSS. Have each CSS point to their own partition with its own outbound route patterns. Have the route patterns point at seperate Route Lists. And in one of the groups route lists drop the standard trunk access code and prefix a different one.
for example if 17XX makes a call using 9 as trunk access like 95551212 drop the 9 and add an 8 so when it is sent to the router it goes as 85551212.
This way you can have dial peers using port 1-4 with a destionation pattern such as 9T for the 16XX extensions and ports 5-8 with a destination pattern of 8T for the 17XX extensions.
there might be a cleaner way but this has always done the trick.
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...