Missing Redirect number from ISDN produces @ in transfur to unity
I have raised a case regarding redirected calls and have discovered from some ISDN exchanges (AXE10) to callmanager the Q931setup is not supplying the redirect number ,not a problem in itself but if the call is then sent to unity , @ is used in the dialed and forwarding number and hence goes to the openning message ,has anybody seen is problem before ,is it related to the bug ref CSCdv66602 and more importantly has anyone found a workarround/fix ?
Re: Missing Redirect number from ISDN produces @ in transfur to
Unity's decision as to what the forwarding number is going to be is pretty simple. From the skinny message called "stationcallinfo", that's passed at the onset of an incoming call, Unity will check to see if the "orginalCalledVoiceMailbox" field is present. If it is, that is used as the "forwarding" number. If that field is not present, the Unity will use the "originalCalledParty" as the "forwarding" number. That logic in the TSP is hard-coded, and I'd imagine that one of those fields previously mentioned contained the "@".
Unity doesn't have any control over what gets into those fields, so I'm not sure there is going to be a workaround in Unity.
Can you provide a detailed call-flow example describing how the call was presented to Unity?
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...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.