10-10-2013 07:20 AM - edited 03-16-2019 07:50 PM
Hi all,
I have a problem to make work call-forwarding on an IP Phone of a customer. When an external phone (PSTN) calls on an IP phone of the company (where forwarding to an external number is setted), the forwarding is not possible on an analogic phone (PSTN) and the call fails.
Here is the trace of call failure generated with "debug isdn q931" command on the Cisco 2900 Gateway :
000744: Oct 10 14:15:37.593: ISDN BR0/1/1 Q931: RX <- SETUP pd = 8 callref = 0x3B
Sending Complete
Bearer Capability i = 0x8090A3
Standard = CCITT
Transfer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0x89
Exclusive, B1
Calling Party Number i = 0x2083, <SOURCE PHONE (PSTN)>
Plan:Unknown, Type:National
Called Party Number i = 0x81, <IP PHONE EXTENSION>
Plan:ISDN, Type:Unknown
000745: Oct 10 14:15:37.601: ISDN BR0/1/1 Q931: TX -> CALL_PROC pd = 8 callref = 0xBB
Channel ID i = 0x89
Exclusive, B1
000746: Oct 10 14:15:37.621: ISDN BR0/1/1 Q931: TX -> SETUP pd = 8 callref = 0x08
Sending Complete
Bearer Capability i = 0x8090A3
Standard = CCITT
Transfer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0x8A
Exclusive, B2
Progress Ind i = 0x8083 - Origination address is non-ISDN
Calling Party Number i = 0x2083, '647359024'
Plan:Unknown, Type:National
Called Party Number i = 0x80, '0231205423'
Plan:Unknown, Type:Unknown
000747: Oct 10 14:15:38.045: ISDN BR0/1/1 Q931: RX <- CALL_PROC pd = 8 callref = 0x88
Channel ID i = 0x8A
Exclusive, B2
000748: Oct 10 14:15:39.805: ISDN BR0/1/1 Q931: RX <- PROGRESS pd = 8 callref = 0x88
Cause i = 0x87F2 - Unknown cause value
Progress Ind i = 0x8281 - Call not end-to-end ISDN, may have in-band info
000749: Oct 10 14:15:39.805: ISDN BR0/1/1 Q931: TX -> PROGRESS pd = 8 callref = 0xBB
Cause i = 0x87F2 - Unknown cause value
Progress Ind i = 0x8281 - Call not end-to-end ISDN, may have in-band info
000750: Oct 10 14:15:41.597: ISDN BR0/1/1 Q931: RX <- RELEASE_COMP pd = 8 callref = 0x3B
Cause i = 0x87E2 - Message not compatible with call state or not implemented
000751: Oct 10 14:15:41.601: ISDN BR0/1/1 Q931: TX -> DISCONNECT pd = 8 callref = 0x08
Cause i = 0x8090 - Normal call clearing
The problem occurs only when forwarding on a pstn phone, on a mobile or an other IP Phone it works perfectly.
A "Cause i = 0x87F2 - Unknown cause value" is generated when the call fails and I don't know where it comes from.
Does anyone can help me please ?
Regards,
Camille
10-10-2013 12:01 PM
Can you share the isdn config into VG
Please rate all useful posts
Regards
Chrysostomos
""The Most Successful People Are Those Who Are Good At Plan B""
10-11-2013 02:39 AM
Here is the config of BRI ports on the GW :
interface BRI000
no ip address
isdn switch-type basic-net3
isdn tei-negotiation first-call
isdn point-to-point-setup
isdn incoming-voice voice
isdn bind-l3 ccm-manager service mgcp
isdn send-alerting
isdn sending-complete
isdn static-tei 0
trunk-group 1
!
interface BRI001
no ip address
isdn switch-type basic-net3
isdn tei-negotiation first-call
isdn point-to-point-setup
isdn incoming-voice voice
isdn bind-l3 ccm-manager service mgcp
isdn send-alerting
isdn sending-complete
isdn static-tei 0
trunk-group 1
!
interface BRI010
no ip address
isdn switch-type basic-net3
isdn tei-negotiation first-call
isdn point-to-point-setup
isdn incoming-voice voice
isdn bind-l3 ccm-manager service mgcp
isdn send-alerting
isdn sending-complete
isdn static-tei 0
trunk-group 1
!
interface BRI011
no ip address
isdn switch-type basic-net3
isdn tei-negotiation first-call
isdn point-to-point-setup
isdn incoming-voice voice
isdn bind-l3 ccm-manager service mgcp
isdn send-alerting
isdn sending-complete
isdn static-tei 0
trunk-group 1
The calling number is in the right format and voice-ports have been checked.
10-10-2013 12:05 PM
Does the calling number is in the right format and is something that belongs to your DID range??
HTH
java
if this helps, please rate
www.cisco.com/go/pdihelpdesk
10-11-2013 02:22 AM
Here is the config of BRI ports on the GW :
interface BRI000
no ip address
isdn switch-type basic-net3
isdn tei-negotiation first-call
isdn point-to-point-setup
isdn incoming-voice voice
isdn bind-l3 ccm-manager service mgcp
isdn send-alerting
isdn sending-complete
isdn static-tei 0
trunk-group 1
!
interface BRI001
no ip address
isdn switch-type basic-net3
isdn tei-negotiation first-call
isdn point-to-point-setup
isdn incoming-voice voice
isdn bind-l3 ccm-manager service mgcp
isdn send-alerting
isdn sending-complete
isdn static-tei 0
trunk-group 1
!
interface BRI010
no ip address
isdn switch-type basic-net3
isdn tei-negotiation first-call
isdn point-to-point-setup
isdn incoming-voice voice
isdn bind-l3 ccm-manager service mgcp
isdn send-alerting
isdn sending-complete
isdn static-tei 0
trunk-group 1
!
interface BRI011
no ip address
isdn switch-type basic-net3
isdn tei-negotiation first-call
isdn point-to-point-setup
isdn incoming-voice voice
isdn bind-l3 ccm-manager service mgcp
isdn send-alerting
isdn sending-complete
isdn static-tei 0
trunk-group 1
The calling number is in the right format and voice-ports have been checked.
10-11-2013 03:28 AM
Hi Camille.
Can you please share a debug isdn q931 in a working case (Mobile forward)?
Thanks
Regards
Carlo
Please rate all helpful posts
"The more you help the more you learn"
10-11-2013 04:35 AM
Here is the working case when forwarding on a mobile phone :
Oct 11 11:40:28.869: ISDN Se0/0/0:15 Q931: RX <- SETUP pd = 8 callref = 0x00CC
Bearer Capability i = 0x8090A3
Standard = CCITT
Transfer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xA98399
Exclusive, Channel 25
Calling Party Number i = 0x2083,
Plan:Unknown, Type:National
Called Party Number i = 0x81,
Plan:ISDN, Type:Unknown
Sending Complete
Oct 11 11:40:28.893: ISDN Se0/0/0:15 Q931: TX -> CALL_PROC pd = 8 callref = 0x80CC
Channel ID i = 0xA98399
Exclusive, Channel 25
Oct 11 11:40:28.897: ISDN Se0/0/0:15 Q931: TX -> SETUP pd = 8 callref = 0x0005
Sending Complete
Bearer Capability i = 0x8090A3
Standard = CCITT
Transfer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xA98381
Exclusive, Channel 1
Calling Party Number i = 0x2083,
Plan:Unknown, Type:National
Called Party Number i = 0x80,
Plan:Unknown, Type:Unknown
Oct 11 11:40:29.249: ISDN Se0/0/0:15 Q931: RX <- CALL_PROC pd = 8 callref = 0x8005
Channel ID i = 0xA98381
Exclusive, Channel 1
Oct 11 11:40:33.881: ISDN Se0/0/0:15 Q931: RX <- ALERTING pd = 8 callref = 0x8005
Oct 11 11:40:33.885: ISDN Se0/0/0:15 Q931: TX -> ALERTING pd = 8 callref = 0x80CC
Progress Ind i = 0x8088 - In-band info or appropriate now available
Regards,
Camille
10-11-2013 04:00 AM
Hi Camille,
From the debug it seems that your call has been forwarded out to ISDN BR0/1/1 and the call is released with unknown cause value from remote end (can be seen in RX <- PROGRESS message received).
Are you able to dial that call forwarded number directly?
If yes, then please check the calling and called number format from debug isdn q931.
If no, then what you can do is co-ordinate with the remote end and check with your calling and called number format and ask the reason for releasing the call.
Regards,
Nishant Savalia
10-11-2013 04:29 AM
Yes, I can call the forwarded number directly. The format of calling and called numbers are ok (same as a working case when redirecting to a mobile).
Regards,
Camille
10-11-2013 04:35 AM
Can you share the debug of that forwarded call number which is dialed directly.
Regards,
Nishant Savalia
10-11-2013 04:38 AM
Here it is :
Oct 11 11:32:54.649: ISDN Se0/0/0:15 Q931: TX -> SETUP pd = 8 callref = 0x0002
Sending Complete
Bearer Capability i = 0x8090A3
Standard = CCITT
Transfer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xA98381
Exclusive, Channel 1
Called Party Number i = 0x80,
Plan:Unknown, Type:Unknown
Oct 11 11:32:54.965: ISDN Se0/0/0:15 Q931: RX <- CALL_PROC pd = 8 callref = 0x8002
Channel ID i = 0xA98381
Exclusive, Channel 1
Oct 11 11:32:55.813: ISDN Se0/0/0:15 Q931: RX <- PROGRESS pd = 8 callref = 0x8002
Cause i = 0x87F2 - Unknown cause value
Progress Ind i = 0x8281 - Call not end-to-end ISDN, may have in-band info
In that case, the same "0x87F2 - Unknown cause value" message appears but the call is successful...
10-11-2013 05:05 AM
This call is being sent out of E1 and not BRI.
Also can you please share full debug i.e from setup to release complete message for the above call.
Regards,
Nishant Savalia
10-11-2013 05:15 AM
The debug above is from tests realised in our lab (same behaviour and errors at the customer's office). Out of E1 or BRI the problem is the same.
Full trace :
Oct 11 12:23:54.401: ISDN Se0/0/0:15 Q931: TX -> SETUP pd = 8 callref = 0x000C
Sending Complete
Bearer Capability i = 0x8090A3
Standard = CCITT
Transfer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xA98381
Exclusive, Channel 1
Called Party Number i = 0x80, '0160208331'
Plan:Unknown, Type:Unknown
Oct 11 12:23:54.721: ISDN Se0/0/0:15 Q931: RX <- CALL_PROC pd = 8 callref = 0x800C
Channel ID i = 0xA98381
Exclusive, Channel 1
Oct 11 12:23:55.565: ISDN Se0/0/0:15 Q931: RX <- PROGRESS pd = 8 callref = 0x800C
Cause i = 0x87F2 - Unknown cause value
Progress Ind i = 0x8281 - Call not end-to-end ISDN, may have in-band info
Oct 11 12:24:00.929: ISDN Se0/0/0:15 Q931: TX -> DISCONNECT pd = 8 callref = 0x000C
Cause i = 0x8090 - Normal call clearing
Oct 11 12:24:01.021: ISDN Se0/0/0:15 Q931: RX <- RELEASE pd = 8 callref = 0x800C
Oct 11 12:24:01.045: ISDN Se0/0/0:15 Q931: TX -> RELEASE_COMP pd = 8 callref = 0x000C
10-11-2013 05:30 AM
I would suggest to co-ordinate with remote end that why they are sending unknown cause value in progress message and for what reason they are sending release message with "message not compatible".
May be you can get some clue from them or some sort of correction can be done from their side.
Regards,
Nishant Savalia
01-02-2014 03:58 AM
Hi Camille,
have you had a chance to fix this issue? I'm facing the same issue as yours. Please let me know if you have fix for this issue.
Thanks
Suresh
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: