04-26-2017 09:03 AM - edited 03-17-2019 10:10 AM
Hello,
Can brackets be used to create call parks without any adverse effect? The documentation I found stated 1 or 2 X's can be used and a range up to 100 numbers can be created but nothing about any other wildcard usage. As a test, I created a call park range 111[01]X and found I was able to access the full 20 slots as anticipated. I'd prefer that 1 entry rather than creating 2 entries 1110X and 1111X. Has anyone else tried this and encountered an issues?
The reason I'm looking for this type of wildcard solution is to reduce the amount of call parks created in our call park redesign to meet requirements to implement a new operator console software solution. We have 240+ sites and 8 nodes.
CUCM version 10.5
Thanks
Solved! Go to Solution.
04-26-2017 09:12 AM
There should be no problem doing it that way, if the system does not accept a wildcard, it will tell you without allowing you to save it.
04-26-2017 10:08 AM
It Would be no problem some more things to keep in mind.
Enter the call park extension number. You can enter literal digits or the wildcard character X (the system allows one or two Xs). For example, enter 5555 to define a single call park extension number of 5555 or enter 55XX to define a range of call park extension numbers from 5500 to 5599.
Note |
You can create a maximum of 100 call park numbers with one call park range definition. Make sure that the call park numbers are unique. |
Note |
You cannot overlap call park numbers between Cisco Unified Communications Manager servers. Ensure that each Cisco Unified Communications Manager server has its own number range. |
Note |
The call park range is selected from the list of servers where the call originates. For example, if phone A (registered to node A) calls phone B (registered to node B) and the phone B user presses Park, phone B requires a call park range in the CSS that resides on node A. In a multinode environment where phones and gateways communicate with various nodes and where calls that originate from any server may need to be parked, the phones require a CSS that contains call park ranges from all servers. |
(Rate if it helps)
JB
04-26-2017 09:12 AM
There should be no problem doing it that way, if the system does not accept a wildcard, it will tell you without allowing you to save it.
04-28-2017 05:36 AM
Thanks for the confirmation!
04-26-2017 10:08 AM
It Would be no problem some more things to keep in mind.
Enter the call park extension number. You can enter literal digits or the wildcard character X (the system allows one or two Xs). For example, enter 5555 to define a single call park extension number of 5555 or enter 55XX to define a range of call park extension numbers from 5500 to 5599.
Note |
You can create a maximum of 100 call park numbers with one call park range definition. Make sure that the call park numbers are unique. |
Note |
You cannot overlap call park numbers between Cisco Unified Communications Manager servers. Ensure that each Cisco Unified Communications Manager server has its own number range. |
Note |
The call park range is selected from the list of servers where the call originates. For example, if phone A (registered to node A) calls phone B (registered to node B) and the phone B user presses Park, phone B requires a call park range in the CSS that resides on node A. In a multinode environment where phones and gateways communicate with various nodes and where calls that originate from any server may need to be parked, the phones require a CSS that contains call park ranges from all servers. |
(Rate if it helps)
JB
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide