You should change the destination pattern on your FXS port pots dial peer, or change the way you're dialing from the other site. It's hard to tell you without details.

-nick

Is this enough?

I'm ready to try destination-pattern 548. since exact match doesn't.

!

dial-peer voice 1 voip

voice-class codec 1

incoming called-number .

modem passthrough nse codec g711ulaw

no vad

!

!

dial-peer voice 21 pots

description for test on port 0/1/1

destination-pattern 5486

port 0/1/1

forward-digits 0

!

debug voice dialpeer inout

!

FS-Voice-RT02#

*Feb 20 17:00:20.799: //-1/6990207680A9/DPM/dpAssociateIncomingPeerCore:

Calling Number=8005551212, Called Number=5486, Voice-Interface=0x0,

Timeout=TRUE, Peer Encap Type=ENCAP_VOIP, Peer Search Type=PEER_TYPE_VOICE,

Peer Info Type=DIALPEER_INFO_SPEECH

*Feb 20 17:00:20.799: //-1/6990207680A9/DPM/dpAssociateIncomingPeerCore:

Result=Success(0) after DP_MATCH_INCOMING_DNIS; Incoming Dial-peer=1

*Feb 20 17:00:20.799: //-1/6990207680A9/DPM/dpAssociateIncomingPeerCore:

Calling Number=8005551212, Called Number=5486, Voice-Interface=0x0,

Timeout=TRUE, Peer Encap Type=ENCAP_VOIP, Peer Search Type=PEER_TYPE_VOICE,

Peer Info Type=DIALPEER_INFO_SPEECH

*Feb 20 17:00:20.799: //-1/6990207680A9/DPM/dpAssociateIncomingPeerCore:

Result=Success(0) after DP_MATCH_INCOMING_DNIS; Incoming Dial-peer=1

FS-Voice-RT02#

You would need to post the part that has the --cisco-dest:

(it's a big block of debugs in debug voip ccapi inout)

It's very possible that you're not getting exactly 4 digits - try configuring the destination-pattern as the 10 digit number or however the other gateway is receiving it from the PSTN.

-nick

First I have to thank you for the help.

I'm going nuts and don't see what is wrong.

I think I have all of the information in here. xxxxxxx is me taking actual numbers out. 7053 is my cell phone, 5486 is the destination fax. To me it looks like it never matches to the destination.

****

!

voice class codec 1

codec preference 1 g711ulaw

!

!

!

voice class h323 1

h225 timeout tcp establish 3

h225 timeout setup 2

!

!

interface BVI1

description To FS-Core-SW01

ip address 10.18.150.5 255.255.255.0

h323-gateway voip interface

h323-gateway voip bind srcaddr 10.18.150.5

!

!

voice-port 0/1/1

description FXS-port for fax test

station-id name Fanshack test

station-id number xxxxxxx5486

caller-id enable type 1

!

!

dial-peer voice 3 voip

modem passthrough nse codec g711ulaw

voice-class codec 1

incoming called-number 54..

no vad

!

!

dial-peer voice 21 pots

description for test on port 0/1/1

destination-pattern 548.

port 0/1/1

forward-digits 0

!

FS-Voice-RT01#debug voip ccapi inout

voip ccapi inout debugging is on

FS-Davie-Voice-RT01#

*Feb 24 15:06:02.969: //-1/1AC6D4BC8161/CCAPI/cc_api_create_cc_entry_common:

Interface=0x46E8850C, Call Id=22,

Call Info=9546957053(TON=National, NPI=ISDN, Screening=Network, Presentation=Allowed),

Called Number=5486(TON=Unknown, NPI=Unknown),

FinalDestinationFlag=TRUE, Incoming Dial-peer=3

*Feb 24 15:06:02.969: //-1/xxxxxxxxxxxx/CCAPI/cc_get_feature_vsa:

*Feb 24 15:06:02.969: :cc_get_feature_vsa malloc success

*Feb 24 15:06:02.969: //-1/xxxxxxxxxxxx/CCAPI/cc_get_feature_vsa:

*Feb 24 15:06:02.969: cc_get_feature_vsa count is 1

*Feb 24 15:06:02.969: //-1/xxxxxxxxxxxx/CCAPI/cc_get_feature_vsa:

*Feb 24 15:06:02.969: :FEATURE_VSA attributes are: feature_name:0,fearture_time:1181895768,feature_id:22

*Feb 24 15:06:02.985: //22/1AC6D4BC8161/CCAPI/cc_api_delete_cc_entry:

Interface=0x46E8850C, Disposition=0x0, Tag=0x0, Call Id=22

*Feb 24 15:06:02.985: //-1/xxxxxxxxxxxx/CCAPI/cc_free_feature_vsa:

*Feb 24 15:06:02.985: :cc_free_feature_vsa freeing 46724C50

*Feb 24 15:06:02.985: //-1/xxxxxxxxxxxx/CCAPI/cc_free_feature_vsa:

*Feb 24 15:06:02.985: vsacount in free is 0

FS-Voice-RT01#

FS-Voice-RT01#no debug voip ccapi inout

voip ccapi inout debugging is off

FS-Voice-RT01#

FS-Voice-RT01#Debug voice dialpeer inout

voip dialpeer inout debugging is on

FS-Voice-RT01#

*Feb 24 15:10:08.494: //-1/AD1EAEAC8162/DPM/dpAssociateIncomingPeerCore:

Calling Number=xxxxxxx7053, Called Number=5486, Voice-Interface=0x0,

Timeout=TRUE, Peer Encap Type=ENCAP_VOIP, Peer Search Type=PEER_TYPE_VOICE,

Peer Info Type=DIALPEER_INFO_SPEECH

*Feb 24 15:10:08.494: //-1/AD1EAEAC8162/DPM/dpAssociateIncomingPeerCore:

Result=Success(0) after DP_MATCH_INCOMING_DNIS; Incoming Dial-peer=3

*Feb 24 15:10:08.494: //-1/AD1EAEAC8162/DPM/dpAssociateIncomingPeerCore:

Calling Number=9546957053, Called Number=5486, Voice-Interface=0x0,

Timeout=TRUE, Peer Encap Type=ENCAP_VOIP, Peer Search Type=PEER_TYPE_VOICE,

Peer Info Type=DIALPEER_INFO_SPEECH

*Feb 24 15:10:08.494: //-1/AD1EAEAC8162/DPM/dpAssociateIncomingPeerCore:

Result=Success(0) after DP_MATCH_INCOMING_DNIS; Incoming Dial-peer=3

FS-Voice-RT01#

Looks like it should match the outgoing dial peer.

What does 'show dial-peer voice summary' show for the outgoing dial peer?

-nick

The show dp v sum is UP UP.

I've rearranged the dial-peer order, I've changed the dp in different trys.

The call comes in on the voip dial-peer and will not go to the FXS.

I can call fxs port to fxs port, so the destination dp works. The voip dp is not searching the dp list from the top after the call comes in.

This is a new fxs card that I installed.

The station to station tells me it is ok.

What next?

Thank you again for your help.

The ccapi debugs you sent weren't complete. Either something is causing that problem also, or it just wasn't the full debugs.

It sounds like there is some other configuration playing a part here.

-nick

This was a site router with CME and CUE configured at one time. With consolidation, it is currently a router on a stick used for overhead paging through an FXO (works) and the FXS that was just added for a fax machine. I've removed the sccp and shutdown all the unused interfaces and the service-engine/0. There is some more I could remove, but all shutdown. What bothers me is the debug voice dialpeer inout showing that the call comes in on the right voip dp but never goes to the dp pots with the destination coded on it. I've rearranged the order of the dial peers so that the exact match pots is prior to the dial peer voip. I thought once the call came in on a dial peer, a linear search of dial peers from the top occured to determine if the call was destined for somewhere else. That search is not happening or is happening incorrectly.

Thank you again for you help.

Phil

Hi Phil,

Try this:

dial-peer voice 3

shut

Since the destination-pattern is 54.. it is overlapping with the other dial peer.

If you were to add:

voice service voip

allow h323 to h323

You would probably see this call routing out that way.

hth,

nick