Hi, I am configuring an analog push button door phone that I want to follow a certain call path until someone answers. I come from a traditional PBX environment where I had this implemented succesfully with time-of-day coverage paths (Avaya terms).
I have the phone hotdialing a number when the button is pushed, I just need a point in the right direction so that I can get the DN to follow a certain path until a user amswers. This path will change based on the time of day also.
Example: Push button - extension 100 rings, no answer - ring extension 200, etc. After 5 pm? then ring extension 300, then 400 so on.
TOD routing is possible with partitions, time periods and time schedules.
1. Configure extension 100 with call forward no answer set to 200. so if 100 doesnt answer, 200 will ring.
2. Define a time period in Callmanager, say its called as BusinessHours (M-F, 8am-5pm). 3. Add this time period to a time schedule. 4. Apply this time schedule to a partition that you define, say its called DoorPhonePn. So partition DoorPhonePn is active only during M-F, 8am-5pm.
5. Create a second partition say DoorPhoneBackupPn. You may or may not define a time schedule for this pattern.
6. Set Call Forward No Answer on extn 300 to ring extn 400. So if 300 doesnt answer, 400 rings.
7. When you setup a Plar in Callmanager, you have to define a null translation pattern. For TOD to work with Plar, you will need to define two null translation patterns.
8. Put Null translation pattern 1 in DoorPhonePn partition
9. Set Null translation pattern 1 to translate to extn 100.
10. Put Null translation pattern 2 in DoorPhoneBackupPn
11. Set Null translation pattern 2 to translate to extn 300.
12. Make sure the translation patterns have a CSS that has access to the partitions in which extn, 100 and 300 are.
13. Create a new CSS, called DoorPhoneCSS and list the partitions in this order.
During business hours, DoorPhonePn is active
So it will plar to 100.
After hours, DoorPhoneBackupPn is active, So it will plar to 300.
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...