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. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

Single Number Reach (SNR) remote Destination, Problem

Hi,

After configure the SNR, a guy (John) call the ip-phone (with its internal and external number), my cell phone rings, I answer, the cell is stalled.

But the call between the John's phone and my cell John is not connected, in the John's phone, you always hear the bells, as if nobody had yet won.

if i test with a call forwarding (forward all or no answer), it's good, no problem

Who have a idea?

It's a french intallation BRI.

CUCM v9.1 (BE6000)

c2901 v15.4(1)T (i have test with 15.3 and 15.2 version)

no error message in the router's debug q931 when in test SNR

Routeur-CUCM#
Dec 22 16:31:20.660: ISDN BR0/0/1 Q931: RX <- SETUP pd = 8  callref = 0x75
        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 = 0x2183, 'JOHN PHONE'
                Plan:ISDN, Type:National
        Called Party Number i = 0xA1, 'External number IP-PHONE'
                Plan:ISDN, Type:National
        Sending Complete
Dec 22 16:31:20.680: ISDN BR0/0/1 Q931: TX -> CALL_PROC pd = 8  callref = 0xF5
        Channel ID i = 0x89
                Exclusive, B1
Dec 22 16:31:20.692: ISDN BR0/0/1 Q931: TX -> ALERTING pd = 8  callref = 0xF5
        Progress Ind i = 0x8088 - In-band info or appropriate now available
Dec 22 16:31:24.700: ISDN BR0/0/0 Q931: TX -> SETUP pd = 8  callref = 0x77
        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
        Calling Party Number i = 0x2183, 'External number IP-PHONE'

                Plan:ISDN, Type:National
        Called Party Number i = 0x80, 'My CELL PHONE number'
                Plan:Unknown, Type:Unknown
        Redirecting Number i = 0x00008F, '117'
                Plan:Unknown, Type:Unknown
Dec 22 16:31:24.768: ISDN BR0/0/0 Q931: RX <- CALL_PROC pd = 8  callref = 0xF7
        Channel ID i = 0x8A
                Exclusive, B2
Dec 22 16:31:29.804: ISDN BR0/0/0 Q931: RX <- ALERTING pd = 8  callref = 0xF7
        Channel ID i = 0x8A
                Exclusive, B2
        Progress Ind i = 0x8088 - In-band info or appropriate now available
Dec 22 16:31:31.984: ISDN BR0/0/0 Q931: RX <- CONNECT pd = 8  callref = 0xF7
        Channel ID i = 0x8A
                Exclusive, B2
        Facility i = 0x91A306020100020103
                Protocol Profile = Remote Operations Protocol
                0xA306020100020103
                Component = Return Error component
                        Invoke Id = 0

                        Error = 3 not available

20 REPLIES

Single Number Reach (SNR) remote Destination, Problem

It seems to be configuration issue with SNR.

Check this document- https://supportforums.cisco.com/docs/DOC-27111

Thanks

Manish

New Member

Single Number Reach (SNR) remote Destination, Problem

Thanks, i used this document for to check my configuration, but it does not solves my problem.

My SNR "works", the cell ring, but when i answer, the communication is not connected with John (external phone) and my cell, as if the CUCM did not see that the cell has answered.

New Member

Single Number Reach (SNR) remote Destination, Problem

I use a MGCP gateway, it's possible to just use the the SNR feature with this gateway's type?

Or it's requires a H323 gateway?

New Member

Single Number Reach (SNR) remote Destination, Problem

Hi, no idea for me?

I don't use the MVA, and for the MVA I know it takes a H323 gateway.

I tested with a trunk sip link and it's ok, SNR work.

It's possible to use the SNR with a MGCP gateway?

I have check with this document, but no succes for use with my MGCP gateway.

https://supportforums.cisco.com/docs/DOC-27111

Can you help me please?

Thanks.

Single Number Reach (SNR) remote Destination, Problem

HI Gilles.

Can you please attach a screenshot of both Remote Destination and Remote Destination Profile pages.

Thanks

Carlo

Please rate all helpful posts

"The more you help the more you learn"

Please rate all helpful posts "The more you help the more you learn"
New Member

Re: Single Number Reach (SNR) remote Destination, Problem

Hi Carlo, you can see my screenshot of both Remote Destination and Remote Destination Profile pages in the attached file.

Thanks

Re: Single Number Reach (SNR) remote Destination, Problem

Hi Gilles

Can you try to put Answer Too Soon timer to 500 instead of 1500 and send a deb isd q931 from your gateway?

Thanks

Regards

Carlo

Please rate all helpful posts

"The more you help the more you learn"

Please rate all helpful posts "The more you help the more you learn"
New Member

Re: Single Number Reach (SNR) remote Destination, Problem

Hi Carlo,

It's the same problème with "Answer Too Soon timer to 500", but i tested with H323 gateway and Trunk Sip and it's ok, but no with MGCP gateway :-(

Gateway-MGCP#debug isdn q931

debug isdn q931 is              ON.

Gateway-MGCP#

*Jan  9 17:31:47.135: ISDN BR0/0/0 Q931: RX <- SETUP pd = 8  callref = 0x0D

        Sending Complete

        Bearer Capability i = 0x9090A3

                Standard = CCITT

                Transfer Capability = 3.1kHz Audio

                Transfer Mode = Circuit

                Transfer Rate = 64 kbit/s

        Channel ID i = 0x89

                Exclusive, B1

        Calling Party Number i = 0x2083, '296622525'

                Plan:Unknown, Type:National

        Called Party Number i = 0x81, '1228'

                Plan:ISDN, Type:Unknown

*Jan  9 17:31:47.167: ISDN BR0/0/0 Q931: TX -> CALL_PROC pd = 8  callref = 0x8D

        Channel ID i = 0x89

                Exclusive, B1

*Jan  9 17:31:47.191: ISDN BR0/0/0 Q931: TX -> ALERTING pd = 8  callref = 0x8D

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

*Jan  9 17:31:51.191: ISDN BR0/0/0 Q931: TX -> SETUP pd = 8  callref = 0x04

        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

        Calling Party Number i = 0x2083, '0296642525'

                Plan:Unknown, Type:National

        Called Party Number i = 0x80, '0290035006'

                Plan:Unknown, Type:Unknown

        Redirecting Number i = 0x00008F, '2001'

                Plan:Unknown, Type:Unknown

*Jan  9 17:31:51.563: ISDN BR0/0/0 Q931: RX <- CALL_PROC pd = 8  callref = 0x84

        Channel ID i = 0x8A

                Exclusive, B2

*Jan  9 17:31:52.415: ISDN BR0/0/0 Q931: RX <- ALERTING pd = 8  callref = 0x84

*Jan  9 17:31:52.967: ISDN BR0/0/0 Q931: RX <- PROGRESS pd = 8  callref = 0x84

        Cause i = 0x87F2 - Unknown cause value

        Progress Ind i = 0x8281 - Call not end-to-end ISDN, may have in-band info

*Jan  9 17:31:55.127: ISDN BR0/0/0 Q931: RX <- CONNECT pd = 8  callref = 0x84

*Jan  9 17:32:02.123: ISDN BR0/0/0 Q931: RX <- DISCONNECT pd = 8  callref = 0x84

        Cause i = 0x8790 - Normal call clearing

*Jan  9 17:32:02.619: ISDN BR0/0/0 Q931: RX <- RELEASE pd = 8  callref = 0x0D

        Cause i = 0x8790 - Normal call clearing

*Jan  9 17:32:02.623: ISDN BR0/0/0 Q931: TX -> RELEASE_COMP pd = 8  callref = 0x8D

        Info Request i = 0x80

*Jan  9 17:32:32.179: ISDN BR0/0/0 Q931: RX <- RELEASE pd = 8  callref = 0x84

        Cause i = 0x8790 - Normal call clearing

*Jan  9 17:32:32.183: ISDN BR0/0/0 Q931: TX -> RELEASE_COMP pd = 8  callref = 0x04

        Info Request i = 0x80

*Jan  9 17:32:34.271: %ISDN-6-LAYER2DOWN: Layer 2 for Interface BR0/0/0, TEI 0 changed to down

*Jan  9 17:32:34.299: %ISDN-6-LAYER2UP: Layer 2 for Interface BR0/0/0, TEI 0 changed to up

Cisco Employee

Single Number Reach (SNR) remote Destination, Problem

I think if its a MGCP gateway then might need to re-route the call back to H.323 gw and back to CUCM. having said if its only mgcp gw in the call flow then it won't work.


Br,
Nadeem 

Please rate all useful post.

Br, Nadeem Please rate all useful post.

Re: Single Number Reach (SNR) remote Destination, Problem

Hi Gilles.
To be honest I always preferred SIP or H323 as signaling protocol.
Tomorrow I'll setup a LAB to test MGCP with SNR and I'll let you know



Regards

Carlo

Sent from Cisco Technical Support iPhone App

Please rate all helpful posts "The more you help the more you learn"
New Member

Re: Single Number Reach (SNR) remote Destination, Problem

ok Carlo, thank you very much for your help.

Re: Single Number Reach (SNR) remote Destination, Problem

Good morning Gilles.

I reproduded SNR configuration in my lab with mgcp gateway.

Adjusting following timers, all worked good.

Answer Too Soon Timer: 500

Answer Too Late Timer: 30000

Delay Before Ringing Timer:1000

Try this settings and let me know

Regards

Carlo

Please rate all helpful posts

"The more you help the more you learn"

Please rate all helpful posts "The more you help the more you learn"
New Member

Re: Single Number Reach (SNR) remote Destination, Problem

i have the same problem with this timers.

Re: Single Number Reach (SNR) remote Destination, Problem

Gilles,

Please collect a debbug isdn  q931 during these 3 situations

1) direct call to your mobile from an ip phone

2) forward your extension to your mobile and call your extension from another ip phone

3) From an ip phone, call your extensions removing call forward settings.

Thanks

Carlo

Please rate all helpful posts

"The more you help the more you learn"

Please rate all helpful posts "The more you help the more you learn"
New Member

Re: Single Number Reach (SNR) remote Destination, Problem

Hi Carlo, this is my Q931 debug:

Thanks.

  • 1) direct call to your mobile from an ip phone

Gateway-MGCP#

*Jan 13 09:18:38.615: ISDN BR0/0/0 Q931: TX -> SETUP pd = 8 callref = 0x07

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

Calling Party Number i = 0x0081, '02966412xx'

Plan:Unknown, Type:Unknown

Called Party Number i = 0x80, '067197xxxx'

Plan:Unknown, Type:Unknown

*Jan 13 09:18:39.015: ISDN BR0/0/0 Q931: RX <- CALL_PROC pd = 8 callref = 0x87

Channel ID i = 0x8A

Exclusive, B2

*Jan 13 09:18:42.867: ISDN BR0/0/0 Q931: RX <- ALERTING pd = 8 callref = 0x87

*Jan 13 09:18:44.435: ISDN BR0/0/0 Q931: RX <- CONNECT pd = 8 callref = 0x87

*Jan 13 09:18:44.439: ISDN BR0/0/0 Q931: TX -> CONNECT_ACK pd = 8 callref = 0x07

*Jan 13 09:19:00.415: ISDN BR0/0/0 Q931: TX -> DISCONNECT pd = 8 callref = 0x07

Cause i = 0x8090 - Normal call clearing

*Jan 13 09:19:01.087: ISDN BR0/0/0 Q931: RX <- RELEASE pd = 8 callref = 0x87

*Jan 13 09:19:01.091: ISDN BR0/0/0 Q931: TX -> RELEASE_COMP pd = 8 callref = 0x07

*Jan 13 09:19:03.159: %ISDN-6-LAYER2DOWN: Layer 2 for Interface BR0/0/0, TEI 0 changed to down

*Jan 13 09:19:03.187: %ISDN-6-LAYER2UP: Layer 2 for Interface BR0/0/0, TEI 0 changed to up

Gateway-MGCP#

  • 2) forward your extension to your mobile and call your extension from another ip phone

Gateway-MGCP#

*Jan 13 09:26:30.751: ISDN BR0/0/0 Q931: RX <- RELEASE pd = 8 callref = 0x89

Cause i = 0x8790 - Normal call clearing

*Jan 13 09:26:30.755: ISDN BR0/0/0 Q931: TX -> RELEASE_COMP pd = 8 callref = 0x09

Info Request i = 0x80

*Jan 13 09:26:32.843: %ISDN-6-LAYER2DOWN: Layer 2 for Interface BR0/0/0, TEI 0 changed to down

*Jan 13 09:26:32.871: %ISDN-6-LAYER2UP: Layer 2 for Interface BR0/0/0, TEI 0 changed to up

*Jan 13 09:26:48.923: ISDN BR0/0/0 Q931: TX -> SETUP pd = 8 callref = 0x0A

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

Calling Party Number i = 0x0081, '02966410xx'

Plan:Unknown, Type:Unknown

Called Party Number i = 0x80, '067197xxxx'

Plan:Unknown, Type:Unknown

Redirecting Number i = 0x00008F, '2001'

Plan:Unknown, Type:Unknown

*Jan 13 09:26:49.287: ISDN BR0/0/0 Q931: RX <- CALL_PROC pd = 8 callref = 0x8A

Channel ID i = 0x8A

Exclusive, B2

*Jan 13 09:26:53.119: ISDN BR0/0/0 Q931: RX <- ALERTING pd = 8 callref = 0x8A

*Jan 13 09:26:56.931: ISDN BR0/0/0 Q931: RX <- CONNECT pd = 8 callref = 0x8A

*Jan 13 09:26:56.939: ISDN BR0/0/0 Q931: TX -> CONNECT_ACK pd = 8 callref = 0x0A

*Jan 13 09:27:03.431: ISDN BR0/0/0 Q931: TX -> DISCONNECT pd = 8 callref = 0x0A

Cause i = 0x8090 - Normal call clearing

*Jan 13 09:27:03.915: ISDN BR0/0/0 Q931: RX <- RELEASE pd = 8 callref = 0x8A

*Jan 13 09:27:03.919: ISDN BR0/0/0 Q931: TX -> RELEASE_COMP pd = 8 callref = 0x0A

*Jan 13 09:27:05.995: %ISDN-6-LAYER2DOWN: Layer 2 for Interface BR0/0/0, TEI 0 changed to down

*Jan 13 09:27:06.023: %ISDN-6-LAYER2UP: Layer 2 for Interface BR0/0/0, TEI 0 changed to up

Gateway-MGCP#

  • 3) From an ip phone, call your extensions removing call forward settings.

Gateway-MGCP#

*Jan 13 09:29:35.527: ISDN BR0/0/0 Q931: RX <- RELEASE pd = 8 callref = 0x8B

Cause i = 0x8790 - Normal call clearing

*Jan 13 09:29:35.531: ISDN BR0/0/0 Q931: TX -> RELEASE_COMP pd = 8 callref = 0x0B

Info Request i = 0x80

*Jan 13 09:29:37.639: %ISDN-6-LAYER2DOWN: Layer 2 for Interface BR0/0/0, TEI 0 changed to down

*Jan 13 09:29:37.667: %ISDN-6-LAYER2UP: Layer 2 for Interface BR0/0/0, TEI 0 changed to up

*Jan 13 09:30:11.667: ISDN BR0/0/0 Q931: TX -> SETUP pd = 8 callref = 0x0C

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

Calling Party Number i = 0x0081, '02966410xx'

Plan:Unknown, Type:Unknown

Called Party Number i = 0x80, '067197xxxx'

Plan:Unknown, Type:Unknown

Redirecting Number i = 0x00008F, '2001'

Plan:Unknown, Type:Unknown

*Jan 13 09:30:12.035: ISDN BR0/0/0 Q931: RX <- CALL_PROC pd = 8 callref = 0x8C

Channel ID i = 0x8A

Exclusive, B2

*Jan 13 09:30:16.595: ISDN BR0/0/0 Q931: RX <- ALERTING pd = 8 callref = 0x8C

*Jan 13 09:30:18.411: ISDN BR0/0/0 Q931: RX <- CONNECT pd = 8 callref = 0x8C

*Jan 13 09:30:26.243: ISDN BR0/0/0 Q931: RX <- DISCONNECT pd = 8 callref = 0x8C

Cause i = 0x8790 - Normal call clearing

Gateway-MGCP#

New Member

Re: Single Number Reach (SNR) remote Destination, Problem

The source of my problem may come from a mismatch or misconfiguration of my MGCP gateway, or BRI ?

New Member

Re: Single Number Reach (SNR) remote Destination, Problem

New Member

Re: Single Number Reach (SNR) remote Destination, Problem

It's not possible with MGCP + BRI:

See the latest version of the Unified Mobility chapter of the 9.1 Features and

Services Guide:

http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/admin/9_1_1/ccmfeat/CUCM_BK_C3E0EFA0_00_cucm-features-services-guide-91_chapter_010001.html#CUCM_RF_L399F788_00__section835

which still clearly states "Mobile Connect features do not get supported for T1 CAS, FXO, FXS and BRI.".  And a bit further down: "The Mobile Connect feature is supported only for Primary Rate Interface (PRI) public switched telephone network (PSTN) connections. For SIP trunks, Mobile Connect is supported over IOS gateways or intercluster trunks.

Re: Single Number Reach (SNR) remote Destination, Problem

Hi Gilles.

Thanks for your info +5 to you.

So MGCP is still ok on PRI

Carlo

Please rate all helpful posts

"The more you help the more you learn"

Please rate all helpful posts "The more you help the more you learn"
New Member

I realize this is later, and

I realize this is later, and a few version up, but MGCP is not mentioned at all on that page, so why do you think it is just MGCP+BRI? I know MGCP+PRI SNR works, and MGCP+FXO SNR does not. Have not tested H.323+FXO SNR yet.

Though I should mention I saw another post stating switching from MGCP to H.323 made Unified Mobility (possibly SNR) work with an FXO.

3107
Views
26
Helpful
20
Replies