I have a call-forwarding/QSIG question. We have a CMM gateway with a QSIG PRI connection to our Avaya G3r PBX. If IP phone 66965 dials Avaya phone 77926 the call goes across the QSIG link. If 77926 does not answer, it correctly covers to the PBX's Intuity voicemail system (mailbox 77926).
Now if IP phone 66960 is "CFwdAll" to 77926 and IP phone 66965 calls 66960, the call correctly forwards across the QSIG link and Avaya phone 77926 rings. Yet in this case if 77926 does not answer the call covers to the PBX's Intuity system, yet the Intuity tries to send the call to the originally dialed number mailbox (66960) rather than the forwarded/redirected mailbox (77926). However this (PBX) Intuity does not have a voicemailbox for 66960 (IP phone).
The interesting part is in both cases the originally dialed number (redirecting number) is included in the facility message. If you look at the end of the facility message: 636393630 the number (66960) is included (separated by "3"'s). This is indeed the number - I've tried changing 66960 to another number and this field changes accordingly. It almost seems that if I could block this facility message I could get the behavior I desire.
1.Forward By Reroute Enabled : The parameter enables the Q.SIG Forward By Reroute feature.
2.Transform Forward by Reroute Destination : This parameter determines whether the called number transformations are applied to the call forward destination and sent as the called address in the call reroute application protocol data unit [APDU]. This parameter applies to QSIG calls that use the call diversion by reroute feature. Valid values specify True (apply called party transformations) or False (do not apply called party transformations).
Yes, I have tried changing each of those from the default individually and I've tried changing them both from the default at the same time - all with the same result.
I have also tried changing 'Always Forward Switch Voice Mail Calls' and 'Include Original Called Info for Q.SIG Call Diversions' again with no positive results.
I tried lowering the 'Forward No Answer Timer (sec)' to 6 seconds. My hope was that when the person at the forwarded phone did not answer that CallManager might pull the call back. However this did not happen - the call continued to ring for 12 seconds (my estimate) and then followed the PBX coverage. I'm not sure why this timer didn't have any effect. Perhaps it does not apply to calls to a gateway (only to other phones??).
You have reached the Cisco Logistics Support Center.. To Check Status of
your RMA, visit Product Returns & Replacements (RMA). Need help? Contact
us by Phone or Email. North Americas Phone: 1800 553 2447 Option 4
Email: firstname.lastname@example.org Europe Phone: +3...
The short answer is that you don't.... That isn't entirely true while at
the same time it kind of is, but for the most part you don't configure
the softkeys. You enable or disable them via TCL. Here is the long
answer. Be sure to read the whole thing or e...
Topology: IP Phone > Switches > Microsoft NPS setup to forward 802.1x
proxy to > ISE 2.1 patch 3 Authentication: EAP-TLS using Cisco MIC SANs
Phone Models 802.1X support? 802.1x flavor Addtl Comment EAP-MD5 EAP-TLS
Cisco 3905 Y Y N Cisco 6911 Y Y N Cisco ...