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.

CCME and incoming PRI dial-peer matching

Hi,

I have a CCME router (2951) with a PRI connected to the telco.

I would like to translate incoming calls to the internal extension number 5000, so i created an incoming pots dial peer for the PRI and bound a translation profile to it:

dial-peer voice 1 pots

description **Incoming PRI**

translation-profile incoming INCOMING

incoming called-number .T

port 0/0/0:15

no sip-register

!

voice translation-rule 1

rule 1 /.*/ /5000/

!

voice translation-profile INCOMING

translate called 1

!

interface Serial0/0/0:15

no ip address

encapsulation ppp

isdn switch-type primary-net5

isdn overlap-receiving T302 2000

isdn incoming-voice voice

isdn send-alerting

isdn bchan-number-order ascending

isdn sending-complete

!

When I did incoming calls to the PRI I noticed, that the dial-peer 1 is never been chosen, so the incoming

digit translation of course is not working as well.

My current solution is binding the incoming profile directly to the voice-port of the PRI:

voice-port 0/0/0:15

translation-profile incoming INCOMING

which is working fine.

However, my questions now are the following:

1) Why is the dial-peer 1 not chosen for incoming PRI calls, although it contains the port 0/0/0:15 statement?

2) What are the best practices for placing incoming translation profiles? Should they be placed on the dial peers
or directly on the voice-ports?

Thanks

Heinz

1 ACCEPTED SOLUTION

Accepted Solutions
Hall of Fame Super Silver

Re: CCME and incoming PRI dial-peer matching

Can you change dial-peer 1 to :

dial-peer voice 1 pots

incoming called-number .

and try again?

Chris

8 REPLIES

CCME and incoming PRI dial-peer matching

Hi Heinz,

First of all, you have a mistake. The translation profile command is incomplete, you're missing the Translation Rule.  it shoud be:

voice translation-profile INCOMING

translate called      ; In your case should be "1".

Are you sure call is not hitting Dial-Peer 1? Please send: debug voice ccapi inout

Regards

Please remember to rate useful posts clicking on the stars below.
Favor calificar todos las respuestas útiles dando click en las estrellas de mas abajo.
___________________________________________
LinkedIn Profile: do.linkedin.com/in/leosalcie

Please remember to rate useful posts clicking on the stars below. Favor calificar todos las respuestas útiles dando click en las estrellas de mas abajo. ___________________________________________ LinkedIn Profile: do.linkedin.com/in/leosalcie
Hall of Fame Super Silver

CCME and incoming PRI dial-peer matching

Heinz had correct profile. 

To answer the question, there is no best practice where to apply translations, it is up to you to decide.

As to why it did not work please post "debug voice dialpeer" output from the call, perhaps you are matching another inbound dialpeer, posting full config would be helpful as well.

HTH,

Chris

Re: CCME and incoming PRI dial-peer matching

Hi,

a "debug voice dialpeer" shows, that this (voip) dial peer is being chosen when there is an incoming call over the PRI:

!

dial-peer voice 1001 voip

destination-pattern [1-9]...

session protocol sipv2

session target ipv4:10.1.1.1

session transport tcp

!

It´s an internal dial peer which points to a different CCME system. I dont understand why this is beeing chosen when there is a call coming in from the PRI.

Debug output:

001828: Nov  1 19:53:11.256 GST: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:

   Calling Number=00446935350, Called Number=9993803, Voice-Interface=0x13D99B2C,

   Timeout=FALSE, Peer Encap Type=ENCAP_VOICE, Peer Search Type=PEER_TYPE_VOICE,

   Peer Info Type=DIALPEER_INFO_SPEECH

001829: Nov  1 19:53:11.256 GST: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:

   Result=Success(0) after DP_MATCH_ORIGINATE; Incoming Dial-peer=101

001830: Nov  1 19:53:11.256 GST: //-1/xxxxxxxxxxxx/DPM/dpMatchSafModulePlugin:

   dialstring=NULL, saf_enabled=0, saf_dndb_lookup=0, dp_result=0

001831: Nov  1 19:53:11.256 GST: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:

   Calling Number=00446935350, Called Number=9993803, Voice-Interface=0x0,

   Timeout=FALSE, Peer Encap Type=ENCAP_VOICE, Peer Search Type=PEER_TYPE_VOICE,

   Peer Info Type=DIALPEER_INFO_FAX

001832: Nov  1 19:53:11.256 GST: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:

   Result=NO_MATCH(-1) After All Match Rules Attempt

001833: Nov  1 19:53:11.256 GST: //-1/xxxxxxxxxxxx/DPM/dpMatchSafModulePlugin:

   dialstring=NULL, saf_enabled=0, saf_dndb_lookup=0, dp_result=-1

001834: Nov  1 19:53:13.260 GST: //-1/8B3E1EA4801A/DPM/dpMatchPeersCore:

   Calling Number=, Called Number=9993803T, Peer Info Type=DIALPEER_INFO_SPEECH

001835: Nov  1 19:53:13.260 GST: //-1/8B3E1EA4801A/DPM/dpMatchPeersCore:

   Match Rule=DP_MATCH_DEST; Called Number=9993803T

001836: Nov  1 19:53:13.260 GST: //-1/8B3E1EA4801A/DPM/dpMatchPeersCore:

   Result=Success(0) after DP_MATCH_DEST

001837: Nov  1 19:53:13.260 GST: //-1/8B3E1EA4801A/DPM/dpMatchSafModulePlugin:

   dialstring=9993803T, saf_enabled=1, saf_dndb_lookup=0, dp_result=0

001838: Nov  1 19:53:13.260 GST: //-1/8B3E1EA4801A/DPM/dpMatchPeersMoreArg:

   Result=SUCCESS(0)

  List of Matched Outgoing Dial-peer(s):

     1: Dial-peer Tag=1001

001839: Nov  1 19:53:13.260 GST: //-1/8B3E1EA4801A/DPM/dpMatchPeersCore:

   Calling Number=, Called Number=9993803, Peer Info Type=DIALPEER_INFO_SPEECH

001840: Nov  1 19:53:13.260 GST: //-1/8B3E1EA4801A/DPM/dpMatchPeersCore:

   Match Rule=DP_MATCH_DEST; Called Number=9993803

001841: Nov  1 19:53:13.260 GST: //-1/8B3E1EA4801A/DPM/dpMatchPeersCore:

   Result=Success(0) after DP_MATCH_DEST

001842: Nov  1 19:53:13.260 GST: //-1/8B3E1EA4801A/DPM/dpMatchSafModulePlugin:

   dialstring=9993803, saf_enabled=0, saf_dndb_lookup=1, dp_result=0

001843: Nov  1 19:53:13.260 GST: //-1/8B3E1EA4801A/DPM/dpMatchPeersMoreArg:

   Result=SUCCESS(0)

   List of Matched Outgoing Dial-peer(s):

     1: Dial-peer Tag=1001

001844: Nov  1 19:53:13.260 GST: //-1/8B3E1EA4801A/DPM/dpMatchPeersCore:

   Calling Number=, Called Number=9993803, Peer Info Type=DIALPEER_INFO_SPEECH

001845: Nov  1 19:53:13.260 GST: //-1/8B3E1EA4801A/DPM/dpMatchPeersCore:

   Match Rule=DP_MATCH_DEST; Called Number=9993803

001846: Nov  1 19:53:13.260 GST: //-1/8B3E1EA4801A/DPM/dpMatchPeersCore:

   Result=Success(0) after DP_MATCH_DEST

001847: Nov  1 19:53:13.260 GST: //-1/8B3E1EA4801A/DPM/dpMatchSafModulePlugin:

   dialstring=9993803, saf_enabled=0, saf_dndb_lookup=1, dp_result=0

001848: Nov  1 19:53:13.260 GST: //-1/8B3E1EA4801A/DPM/dpMatchPeersMoreArg:

   Result=SUCCESS(0)

   List of Matched Outgoing Dial-peer(s):

     1: Dial-peer Tag=1001

001849: Nov  1 19:53:13.260 GST: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:

   Calling Number=9993803, Called Number=9993803, Peer Info Type=DIALPEER_INFO_SPEECH

001850: Nov  1 19:53:13.260 GST: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:

   Match Rule=DP_MATCH_DEST; Called Number=9993803

001851: Nov  1 19:53:13.260 GST: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:

   Result=Success(0) after DP_MATCH_DEST

001852: Nov  1 19:53:13.260 GST: //-1/xxxxxxxxxxxx/DPM/dpMatchSafModulePlugin:

   dialstring=9993803, saf_enabled=0, saf_dndb_lookup=1, dp_result=0

001853: Nov  1 19:53:13.260 GST: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersMoreArg:

   Result=SUCCESS(0)

   List of Matched Outgoing Dial-peer(s):

     1: Dial-peer Tag=1001

001854: Nov  1 19:53:13.260 GST: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:

   Calling Number=9993803, Called Number=, Voice-Interface=0x0,

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

   Peer Info Type=DIALPEER_INFO_SPEECH

001855: Nov  1 19:53:13.260 GST: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:

   Result=Success(0) after DP_MATCH_ORIGINATE; Incoming Dial-peer=1001

001856: Nov  1 19:53:13.260 GST: //-1/xxxxxxxxxxxx/DPM/dpMatchSafModulePlugin:

   dialstring=NULL, saf_enabled=0, saf_dndb_lookup=0, dp_result=0

001857: Nov  1 19:53:13.260 GST: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:

   Calling Number=9993803, Called Number=, Voice-Interface=0x0,

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

   Peer Info Type=DIALPEER_INFO_SPEECH

001858: Nov  1 19:53:13.260 GST: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:

   Result=Success(0) after DP_MATCH_ORIGINATE; Incoming Dial-peer=1001

001859: Nov  1 19:53:13.260 GST: //-1/xxxxxxxxxxxx/DPM/dpMatchSafModulePlugin:

   dialstring=NULL, saf_enabled=0, saf_dndb_lookup=0, dp_result=0

001860: Nov  1 19:53:13.260 GST: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:

   Calling Number=, Called Number=9993803, Peer Info Type=DIALPEER_INFO_SPEECH

001861: Nov  1 19:53:13.260 GST: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:

   Match Rule=DP_MATCH_DEST; Called Number=9993803

001862: Nov  1 19:53:13.260 GST: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:

   Result=Success(0) after DP_MATCH_DEST

001863: Nov  1 19:53:13.260 GST: //-1/xxxxxxxxxxxx/DPM/dpMatchSafModulePlugin:

   dialstring=9993803, saf_enabled=0, saf_dndb_lookup=1, dp_result=0

001864: Nov  1 19:53:13.260 GST: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersMoreArg:

   Result=SUCCESS(0)

   List of Matched Outgoing Dial-peer(s):

     1: Dial-peer Tag=1001

001865: Nov  1 19:53:13.260 GST: //-1/8B3E1EA4801A/DPM/dpMatchPeersCore:

   Calling Number=, Called Number=9993803, Peer Info Type=DIALPEER_INFO_SPEECH

001866: Nov  1 19:53:13.260 GST: //-1/8B3E1EA4801A/DPM/dpMatchPeersCore:

   Match Rule=DP_MATCH_DEST; Called Number=9993803

001867: Nov  1 19:53:13.264 GST: //-1/8B3E1EA4801A/DPM/dpMatchPeersCore:

   Result=Success(0) after DP_MATCH_DEST

001868: Nov  1 19:53:13.264 GST: //-1/8B3E1EA4801A/DPM/dpMatchSafModulePlugin:

   dialstring=9993803, saf_enabled=1, saf_dndb_lookup=1, dp_result=0

001869: Nov  1 19:53:13.264 GST: //-1/8B3E1EA4801A/DPM/dpMatchPeersMoreArg:

   Result=SUCCESS(0)

   List of Matched Outgoing Dial-peer(s):

     1: Dial-peer Tag=1001

The dialed number is: 9993803

Any ideas?


CCME and incoming PRI dial-peer matching

I was sure the traslation-profile was incomplete :

voice translation-profile INCOMING

translate called

Maybe I'm tired

Please remember to rate useful posts clicking on the stars below.
Favor calificar todos las respuestas útiles dando click en las estrellas de mas abajo.
___________________________________________
LinkedIn Profile: do.linkedin.com/in/leosalcie

Please remember to rate useful posts clicking on the stars below. Favor calificar todos las respuestas útiles dando click en las estrellas de mas abajo. ___________________________________________ LinkedIn Profile: do.linkedin.com/in/leosalcie
Hall of Fame Super Silver

Re: CCME and incoming PRI dial-peer matching

   Result=Success(0) after DP_MATCH_ORIGINATE; Incoming Dial-peer=101

Can you post dial peer 101?

Re: CCME and incoming PRI dial-peer matching

Dial-Peer 101 is the Outgoing-Dialpeer for the PRI:

dial-peer voice 101 pots

description **Outgoing Dial Peer**

translation-profile outgoing OUTGOING

destination-pattern 0T

port 0/0/0:15

no sip-register

!

and dial-peer 1 shoud act as the incoming one:

dial-peer voice 1 pots

description **Incoming Dial Peer PRI**

translation-profile incoming INCOMING

incoming called-number .T

port 0/0/0:15

no sip-register

!

Maybe there is a conflict because I use "port 0/0/0:15" on both dial-peers?

Hall of Fame Super Silver

Re: CCME and incoming PRI dial-peer matching

Can you change dial-peer 1 to :

dial-peer voice 1 pots

incoming called-number .

and try again?

Chris

Re: CCME and incoming PRI dial-peer matching

Hi Chris,

that did the trick. Many thanks!

Have a good one

Heinz

235
Views
0
Helpful
8
Replies