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

Call forwarding towards mobile

this is a debug isdn q931 because the calls do not work towards mobile. Why?

pr 30 23:17:37.921: %LINK-3-UPDOWN: Interface BRI0/3/0, changed state to up

Apr 30 23:17:37.997: ISDN BR0/3/0 Q931: RX <- SETUP pd = 8 callref = 0x6F

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 = 0x0183, '3351234567'

Plan:ISDN, Type:Unknown

Called Party Number i = 0xA1, '64470345'

Plan:ISDN, Type:National

Sending Complete

Apr 30 23:17:38.013: ISDN BR0/1/0 Q931: Applying typeplan for sw-type 0x1 is 0x0 0x1, Calling num 3357660463

Apr 30 23:17:38.065: %LINK-3-UPDOWN: Interface BRI0/1/0, changed state to up

Apr 30 23:17:38.889: ISDN BR0/3/0 **ERROR**: L3_Go: Multi nlcb DL_EST, cid 0x2B30 cr 0xEF ev 0x300 ces 1

Apr 30 23:17:38.889: ISDN BR0/3/0 Q931: TX -> CALL_PROC pd = 8 callref = 0xEF

Channel ID i = 0x89

Exclusive, B1

Apr 30 23:17:39.025: ISDN BR0/1/0 Q931: TX -> SETUP pd = 8 callref = 0x6C

Bearer Capability i = 0x8090A3

Standard = CCITT

Transfer Capability = Speech

Transfer Mode = Circuit

Transfer Rate = 64 kbit/s

Channel ID i = 0x81

Preferred, B1

Calling Party Number i = 0x0183, '3351234567'

Plan:ISDN, Type:Unknown

Called Party Number i = 0xA1, '3397654321'

Plan:ISDN, Type:National

Sending Complete

Apr 30 23:17:39.117: ISDN BR0/1/0 Q931: RX <- CALL_PROC pd = 8 callref = 0xEC

Channel ID i = 0x89

Exclusive, B1

Apr 30 23:17:39.465: ISDN BR0/1/0 Q931: RX <- DISCONNECT pd = 8 callref = 0xEC

Cause i = 0x8281 - Unallocated/unassigned number

Progress Ind i = 0x8288 - In-band info or appropriate now available

Apr 30 23:17:39.473: ISDN BR0/3/0 Q931: TX -> DISCONNECT pd = 8 callref = 0xEF

Cause i = 0x8081 - Unallocated/unassigned number

Progress Ind i = 0x8288 - In-band info or appropriate now available

Apr 30 23:17:39.541: ISDN BR0/3/0 Q931: RX <- RELEASE pd = 8 callref = 0x6F

Apr 30 23:17:39.541: ISDN BR0/3/0 Q931: TX -> RELEASE_COMP pd = 8 callref = 0xEF

Apr 30 23:17:39.549: ISDN BR0/1/0 Q931: TX -> RELEASE pd = 8 callref = 0x6C

Apr 30 23:17:39.605: ISDN BR0/1/0 Q931: RX <- RELEASE_COMP pd = 8 callref = 0xEC

Apr 30 23:17:50.613: ISDN BR0/3/0 Q931: Ux_DLRelInd: DL_REL_IND received from L2

1 ACCEPTED SOLUTION

Accepted Solutions
New Member

Re: Call forwarding towards mobile

Cause i = 0x8081 - Unallocated/unassigned number so pls go through the link http://www.cisco.com/en/US/tech/tk801/tk133/technologies_tech_note09186a00800b48cb.shtml

hope this helps

3 REPLIES
Bronze

Re: Call forwarding towards mobile

Your called number is 64470345. That is 8 digits. How many does your telco want to see? Can you dial 64470345 from a phone with the exact same CSS that the remote destination has?

Another possibility I've seen is that carriers will use the calling number for authentication to allow or reject the call to go out. Is the calling party going out a number known on your trunk?

Please rate if this helped.

New Member

Re: Call forwarding towards mobile

interface BRI0/1/0

isdn map address 3.* plan unknown type unknown

New Member

Re: Call forwarding towards mobile

Cause i = 0x8081 - Unallocated/unassigned number so pls go through the link http://www.cisco.com/en/US/tech/tk801/tk133/technologies_tech_note09186a00800b48cb.shtml

hope this helps

579
Views
0
Helpful
3
Replies
CreatePlease login to create content