I´m deploying CUCM integrated to an old Windows application using CTI, and also to a third party using SIP Trunk. The CTI app has an internal timer with a limit, so it expects the calling process to be quite short. The original deployment had a Gateway with FXO interfaces that provided an immediate connected state for the calls. Now, with SIP Trunk, we have the usual "180 trying", "183 sessiong in progress", after several seconds of ringback we get a "200 OK", and then finally a connected state. By the time the call is connected, the app internal timer expired and the call is dropped.
We can´t modify the windows app, so removing the annoying timer is not possible.
Is there any way of forcing a connected state in CUCM just as soon the calling process begins?? (we have a router that can be used as CUBE if that helps...)
I know that Asterisk can do what I want (thanks to the answer() function), but I´d like not to add a non-cisco box to our deployment.
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...