The CTI ports in our IPCCX 3.5 installation have been implemented using 300 numbers from our DDI space. This seems to be an inefficient use of DDI space, as CTI ports are not dialled directly; the CTI Route Point redirects the call to a CTI port.
Is it be possible to renumber the CTI ports using another 'internal' CTI numbering scheme, say, 90XXX? Should the CTI ports be in their own partition and only be referenced in the CSS of the CTI Route Points?
You are absolutely correct, you do not want waste DID range on your cti ports. You can easily change them or delete and create new ones with another range. Make sure your jtapi subsystem configuration reflects the change.
It is a best practice to assign cti ports into their own partition.
Thanks for that. When an IPCCX script is running, is it running in the context of the CSS of the CTI port (as opposed to the CSS of the CTI Route Point). If the script needs to redirect a call, say to a voice mail pilot number, then should this number be included in the CSS of the CTI ports?
On a related point, when a call is redirected from a Route Point to a CTI port, is the CSS of the Route Point or the original calling device used? Ideally, I want to place CTI ports in their own partition and only reference them in the CSS of the Route Point.
I've just tried this in the lab and it appears that the calling devices need access to the partition of the CTI ports (in addition to the Route Point partition), so it does appear that the RP doesn't use its own CSS for redirection to CTI ports. Can this behaviour be changed?
Looks like we're going to have to renumber those CTI ports. :(
IntroductionCUCM Routing RulesDial String implementation PolicyCUCM Routing LogicSIP URI Call Routing Analysis+++ Case Study: 1 ++++++ Case Study: 2 +++Conclusion
Over the last few months, I have had the privilege of working on SI...
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...