[cisco-voip] 2 stage inbound to FXO port issues

Wed Feb 27 13:38:13 EST 2013

Problem solved.  Replaced the FXS card and all is well.

It was a brand new card too....

Thanks for all the input....

Jeff

________________________________
From: Ryan Ratliff [rratliff at cisco.com]
Sent: Wednesday, February 27, 2013 1:24 PM
To: Jeffrey Girard
Cc: ccieid1ot; cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] 2 stage inbound to FXO port issues

What's the config for the 2951 look like with respect to that FXO port?  The FXS is just going to signal the FXO to ring, it isn't capable of sending digits across (except caller-id if enabled).  If there is an inbound dial-peer on the 2951 I'd expect you to get secondary dialtone as mentioned, if there's a connection-plar configured then an outbound call will be initiated to that destination and used to connect to the incoming call on the FXO port.

-Ryan

On Feb 27, 2013, at 12:25 PM, Jeffrey Girard <jeffrey.girard at girardinc.com<mailto:jeffrey.girard at girardinc.com>> wrote:

Thanks for the reply, but unfortunately, I dont think that is correct.

http://www.cisco.com/en/US/docs/voice_ip_comm/cucme/admin/configuration/guide/cmetoll.html

On page 497, under the heading of Blocking Two-stage Dialing Service on Analog and Digital FXO Ports

Blocking Two-stage Dialing Service on Analog and Digital FXO Ports
Cisco Unified CME 8.1 and later versions block the two-stage dialing service which is initiated when an Analog or Digital FXO port goes offhook and the private line automatic ringdown (PLAR) connection is not setup from the voice-port. As a result, no outbound dial-peer is selected for an incoming analog or digital FXO call and no dialed digits are collected from an FXO call. Cisco Unified CME and voice gateways disconnect the FXO call with cause-code "unassigned-number (1)". Cisco Unified CME uses the no secondary dialtone command by default from FXO voice-port to block the two-stage dialing service on Analog or digital FXO ports.

This implies that if I do not configure connection plar on the FXO port, I should get secondary dialtone.  This is what I always thought to be true.

This document did, however, lead me to discover that the "no secondary dialtone" command was on by default on the FXO port.  I reversed the command, but still no secondary dial-tone.

I am going to do some more testing, which will include replacing the FXO and FXS cards

Anyone else with suggestions?

Jeff
________________________________
From: ccieid1ot [ccieid1ot at gmail.com<mailto:ccieid1ot at gmail.com>]
Sent: Tuesday, February 26, 2013 1:49 PM
To: Jeffrey Girard
Cc: cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
Subject: Re: [cisco-voip] 2 stage inbound to FXO port issues

For calls inbound to FXO ports, you would need to configure connection plar.

On Mon, Feb 25, 2013 at 10:38 AM, Jeffrey Girard <jeffrey.girard at girardinc.com<mailto:jeffrey.girard at girardinc.com>> wrote:
Simplified diagram is attached.  Lab network.

Scenario:  Using a 2811 router as a PSTN emulator.  Has a 2 port FXS card installed.  One port has an analog phone attached, other port is connected to a 4 port FXO card installed into a 2951 router.  2951 is H323 with CUCM 8.6.  Simple/test dial peers configured.  Snippets below:

PSTN Emulator:
!
voice-port 0/0/0
!
voice-port 0/0/1
!
!
!
!
dial-peer voice 1 pots
description Emulating legacy PATCOM number
destination-pattern 0999
port 0/0/1
!
dial-peer voice 2 pots
description Emulating tie line to Access Terminal
destination-pattern 9999
port 0/0/0

H323 Gateway Router
!
voice-port 0/1/0
trunk-group FXO
cptone PK
!
voice-port 0/1/1
trunk-group FXO
cptone PK
!
voice-port 0/1/2
trunk-group FXO
cptone PK
!
voice-port 0/1/3
trunk-group FXO
cptone PK
!
!
dial-peer voice 1 pots
description Incoming Call Routing
incoming called-number .
direct-inward-dial
!
dial-peer voice 2 voip
description Incoming Call Routing
incoming called-number .
voice-class codec 1
dtmf-relay h245-alphanumeric
no vad
!
!
voice-port 0/1/0
trunk-group FXO
cptone PK
!
voice-port 0/1/1
trunk-group FXO
cptone PK
!
voice-port 0/1/2
trunk-group FXO
cptone PK
!
voice-port 0/1/3
trunk-group FXO
cptone PK
!
!
dial-peer voice 999 pots
description Dummy dial peer to test BYOPBX
destination-pattern 0999
port 0/1/0
forward-digits all
!

I have other dial-peers on this router (not shown) that will take the inbound digits.  However, Im never able to pass the digits.

Calls from the VoIP network to the simulated PSTN work fine.  Calls from the PSTN to the VoIP network fail.

When I pick up the analog phone, I get the expected dial tone.  I enter "9999" and the call rings to the FXS port and I hear the FXO port answer.  I get the expected secondary (2 stage) dial tone, but then before I can press any digits, the FXo port hangs up and I am left with the PSTN router dial tone.

debug voip dialpeer on the H323 router shows no results at all when I try to place the call.
debug voip dialpeer on the PSTN router shows the expected dial peer matching and the expected result.  File is attached.

Additionally, when I observe the output of show voice port summary while I place the call, I see the FXS port (the one that is tied to the FXO port) go off hook and then go back on hook (file also attached)

So, the FXO port appears to be looking for something from the FXS when it answers the call, doesnt get it (or doesnt like what it gets) so it hangs up.

Looking for help...

Jeff

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip

--
duy
CCIE #27737 Voice
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20130227/a1636b03/attachment.html>