Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

QSIG Forwarding/Redirect Problem

Hi,

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).

Any ideas how this can be corrected?

Thanks! Rob.

5 REPLIES
Green

Re: QSIG Forwarding/Redirect Problem

There is a field:

Redirecting Number IE Delivery - Outbound checkbox on the Gateway Configuration page in Cisco CallManager Administration

Not sure if this will help with Qsig since Call Diversion uses DivertingLegInformation2 and divertingNr fields

I remember this:

DDTS:

CSCsd93062

Your scenario is kind of complicated since we normally want to preserve the RDNIS not to remove it.

Let me know if that helps.

HTH

New Member

Re: QSIG Forwarding/Redirect Problem

Hi,

Thanks for your reply. I am running CallManager 4.1(3)ES62, so I assume the bug(s) you mentioned are fixed in my version (listed as fixed in 4.1(3)ES54).

I have tried that field - both checked and unchecked. When checked it definitely adds that info (see debug isdn q931 output, below), however the results are the same.

Debug ISDN Q931 without redirect box checked:

GVODLAB01#

GVODLAB01#

Sep 27 13:56:46.559: ISDN Se1/0:23 Q931: TX -> SETUP pd = 8 callref = 0x0001

Sending Complete

Bearer Capability i = 0x8090A2

Standard = CCITT

Transfer Capability = Speech

Transfer Mode = Circuit

Transfer Rate = 64 kbit/s

Channel ID i = 0xA98397

Exclusive, Channel 23

Facility i = 0x9FAA068001008201008B0100A11C02010102011530140201010A01018

00101A109A00780053636393630

Calling Party Number i = 0x2981, '66965'

Plan:Private, Type:National

Called Party Number i = 0xA9, '77926'

Plan:Private, Type:National

Sep 27 13:56:46.603: ISDN Se1/0:23 Q931: RX <- CALL_PROC pd = 8 callref = 0x800

1

Channel ID i = 0xA98397

Exclusive, Channel 23

Sep 27 13:56:46.619: ISDN Se1/0:23 Q931: RX <- ALERTING pd = 8 callref = 0x8001

Debug ISDN Q931 with redirect box checked:

GVODLAB01#

GVODLAB01#

Sep 27 13:53:56.125: ISDN Se1/0:23 Q931: TX -> SETUP pd = 8 callref = 0x005D

Sending Complete

Bearer Capability i = 0x8090A2

Standard = CCITT

Transfer Capability = Speech

Transfer Mode = Circuit

Transfer Rate = 64 kbit/s

Channel ID i = 0xA98397

Exclusive, Channel 23

Facility i = 0x9FAA068001008201008B0100A11C02010102011530140201010A01018

00101A109A00780053636393630

Calling Party Number i = 0x2981, '66965'

Plan:Private, Type:National

Called Party Number i = 0xA9, '77926'

Plan:Private, Type:National

Redirecting Number i = '!', 0x008F, '66960'

Plan:ISDN, Type:National

Sep 27 13:53:56.173: ISDN Se1/0:23 Q931: RX <- CALL_PROC pd = 8 callref = 0x805

D

Channel ID i = 0xA98397

Exclusive, Channel 23

Sep 27 13:53:56.189: ISDN Se1/0:23 Q931: RX <- ALERTING pd = 8 callref = 0x805D

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.

Thanks - Rob.

Green

Re: QSIG Forwarding/Redirect Problem

Hi Rob,

Call Diversion over Qsig normally works with Diversion APDU's and Redirecting Number

IE is not valid over QSIG.

Normally Q.SIG integrations are for preserving features like RDNIS, MWI, Callername, CallBack, Path replacement, etc.

Is there any reason why u have Q.SIG integration?

There is a Service Parameters that may help, but havent test it in lab,

Include Original Called Info for Q.SIG Call Diversions*

Otherwise u may change the PRI protocol or open a TAC to confirm that for Outbound/Inbound there is no way to "disable" the divert feature.

New Member

Re: QSIG Forwarding/Redirect Problem

Have you tried the Callmanager service parameter

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).

New Member

Re: QSIG Forwarding/Redirect Problem

Hi,

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??).

Thanks - Rob.

1987
Views
0
Helpful
5
Replies
CreatePlease to create content