Summary: If i remove the incoming corlist on the ephone-dn 10 the calls go through fine but with the incoming corlist on the ephone-dn 10 i get a busy tone.... also strange if I apply the "Ladies-Access" corlist as the incoming corlist to my Mens Extensions (ephone-dn 10) the calls go through fine using the FXO ports of the ladies trunk group..... i've tried alot to find out what I'm doing wrong but i failed.... would really appreciate some help here.................. calls from the ladies extensions go out fine using their configured "Ladies-Lines" trunkgroup.....
We have 2 Departments, one for Men and the other for Ladies and we have 4 lines from the Telco Provider connected to 4 FXO ports in the UC540....
They require that two of the lines be dedicated for the Ladies Division and 2 for the Men for Outgoing Calls.... so when anyone for the Ladies dept. dials out they use either of the two FXO ports dedicated to them and similarly for the Men, the Men should not use the ladies lines and vice versa.... to simplify the config below i'll just mention what i did with respect to dialing mobile number.....
I Implemented CoR List to achieve the following as follows (please find attached my configuration relevant to this attached....)
I first Added two of the voice ports for Men in a Trunk Group called Men-Lines and similarly for Ladies called Ladies-Lines......
Step 1: I created a custom cor as follows:
dial-peer cor custom
name Mobile_Ladies (similarly partitions for local, national, etc for ladies and men... see attached .txt pls)
Step 2: Next I created a cor list
### CorlistFor Ladies Dial-Peers ###
dial-peer cor list call-mobile-ladies (similarly corlist for local, national, etc... for ladies.... see attached .txt pls) member Mobile_Ladies
dial-peer cor list Ladies-Access member Local_Ladies
member Mobile_Ladies member National_Ladies member Intl_Ladies member 905_Ladies member Emrg_Ladies member 800_900_Ladies
### CorlistFor Men Dial-Peers ###
dial-peer cor list call-mobile-Men (similarly corlist for local, national, etc... for ladies.... see attached .txt pls) member Mobile_Men
dial-peer cor list Men-Access member Local_Men member Mobile_Men member National_Men member Intl_Men member 905_Men member Emrg_Men member 800_900_Men
Step 3: I created the Dial-Peers for each of the type of calls (local, mobile, national, etc.... for men and ladies )
dial-peer voice 31 pots (similarly i created another 6 dial-peers and assigned them the appropriate outgoing corlist for the ladies dial-peers)
corlist outgoing call-mobile-ladies
description Mobile Calls Ladies
dial-peer voice 41 pots (similarly i created another 6 dial-peers and assigned them the appropriate outgoing corlist for the mens dial-peers)
corlist outgoing call-mobile-Men
description Mobile Calls Men
Step 4: Finally I added the incoming corlist to the ephone-dn for the Ladies and Men's Extensions as follows:
thanks acampbell... it worked.... initially it still gave me a busy but was not giving me a busy with the other voice-port in the trunk group for the Mens Lines... then i tested the fault voice port for voltage and it showed 0x00 so that is taken care of now....
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...
[toc:faq]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 discusse...