CUBE Q.SIG e SIP supplementary services relativi al Call Completion
my question is really tecnichal . I need to Know if Cisco Cube on a ISR G2 equipped whit VWIC3 T1/E1 is able to making the interworking between Q.SIG end SIP of the supplementary services of the Call Completion. It should be supported the forwarding of CCBS and CCNA.
As far I know this type o services are not standardized in SIP but we have only a draft that is implemented on asterisk
CUBE Q.SIG e SIP supplementary services relativi al Call Complet
Short answer is yes with a disclaimer. The disclaimer first: This requires testing and validation in your environment. A free answer given on a forum should not be considered gospel on this topic.
Back to the 'yes.' CUBE isn't relevant here since you're interworking between ISDN Q.SIG and SIP; CUBE is only involved when all call legs are IP (i.e. not POTS/ISDN to IP).
IOS natively translates the ITU Q.850 cause codes into the equivalent SIP 4XX response. For example, a Q.850 cause code of 17 (User Busy) would translate into a SIP 486 Busy Here. I do not recall CUCM's response when the INVITE message expires (at 180 seconds by default); it would be a 4XX reason though.
Additionally, you can tunnel the actual QSIG messages over the SIP connection to CUCM if you desire. This allows even more of the Q.SIG functionality to work (e.g. MWI, Path Replacement, etc) since CUCM gets to see the actual Q.SIG payload. Previously you needed to use MGCP for this to work. Note that this is a relatively new feature and should be tested exhaustively to avoid user-impacting bugs.
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...