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

Problems with incoming dialpeer

Hello,

I'm testing at the moment some dial-peers for Germany in my lab. One is to use a outgoing dial-peer without a 0 as destination-pattern. With them I have a couple of problems that the system is selecting the outgoing dialpeer also as incoming dialpeer at the ISDN interface. I have break down the problem in the lab to simple configuration where the issue appears.

Scenario is very simple. ISDN Interface 2/0 is conected to the service provider and to the CME is one phone on port 3/0 connected(number 20).

The config

voice translation-rule 1

rule 1 /^610268\(..\)/ /\1/

rule 2 /610268/ /20/

!

voice translation-profile ISDN

translate called 1

!

interface BRI2/0

no ip address

isdn switch-type basic-net3

isdn overlap-receiving T302 6000

isdn point-to-point-setup

isdn incoming-voice voice

isdn sending-complete

isdn static-tei 0

!

voice-port 2/0

compand-type a-law

cptone DE

timeouts interdigit 6

bearer-cap 3100Hz

!

voice-port 2/1

!

voice-port 3/0

cptone DE

timeouts initial 4

timeouts interdigit 2

bearer-cap 3100Hz

station-id name TEL

station-id number 20

caller-id enable

!

dial-peer voice 30 pots

#my outgoing dial-peer - for the first debug without "port 2/0"

destination-pattern ...T

!

dial-peer voice 50 pots

#this should be my incoming dialpeer

translation-profile incoming ISDN

incoming called-number 610268T

direct-inward-dial

!

dial-peer voice 11 pots

#in- and outgoing dialpeer for my analog phone

destination-pattern 20

port 3/0

Without "port 2/0" at the outgoing dial-peer an incoming call is matched correct to the incoming dial-peer 50. But if I add a the ISDN port to the outgoing dial-peer 30. An incoming call is immediately matched to dial-peer 30.

I don't understand why the incoming call is matched first to the "port" command. It should first match the incoming-called number.

Here the debugs "debug voice dialpeer"

debug without port 2/0 at dial-peer 30:

* *Mar 23 13:21:45.929: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:

   Calling Number=17600064700, Called Number=6102682, Voice-Interface=0x8432461C,

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

   Peer Info Type=DIALPEER_INFO_SPEECH

*Mar 23 13:21:45.929: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:

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

*Mar 23 13:21:45.929: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:

   Calling Number=17600064700, Called Number=6102682, Voice-Interface=0x0,

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

   Peer Info Type=DIALPEER_INFO_FAX

*Mar 23 13:21:45.933: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:

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

*Mar 23 13:21:45.933: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:

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

*Mar 23 13:21:45.933: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:

   Match Rule=DP_MATCH_DEST; Called Number=20

*Mar 23 13:21:45.933: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:

   Result=Success(0) after DP_MATCH_DEST

*Mar 23 13:21:45.933: //-1/xxxxxxxxxxxx/DPM/dpMatchPeers:

   Result=SUCCESS(0)

   List of Matched Outgoing Dial-peer(s):

     1: Dial-peer Tag=11

*Mar 23 13:21:45.957: //-1/F911BAC48025/DPM/dpMatchPeersCore:

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

*Mar 23 13:21:45.961: //-1/F911BAC48025/DPM/dpMatchPeersCore:

   Match Rule=DP_MATCH_DEST; Called Number=20

*Mar 23 13:21:45.961: //-1/F911BAC48025/DPM/dpMatchPeersCore:

   Result=Success(0) after DP_MATCH_DEST

*Mar 23 13:21:45.961: //-1/F911BAC48025/DPM/dpMatchPeersMoreArg:

   Result=SUCCESS(0)

   List of Matched Outgoing Dial-peer(s):

     1: Dial-peer Tag=11

debug with port 2/0 at dial-peer 30:

Mar 23 13:22:38.487: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:

   Calling Number=17600064700, Called Number=6102682, Voice-Interface=0x8432461C,

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

   Peer Info Type=DIALPEER_INFO_SPEECH

*Mar 23 13:22:38.491: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:

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

*Mar 23 13:22:38.491: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:

   Calling Number=17600064700, Called Number=6102682, Voice-Interface=0x0,

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

   Peer Info Type=DIALPEER_INFO_FAX

*Mar 23 13:22:38.491: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:

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

*Mar 23 13:22:44.501: //-1/186615328026/DPM/dpMatchPeersCore:

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

*Mar 23 13:22:44.501: //-1/186615328026/DPM/dpMatchPeersCore:

   Match Rule=DP_MATCH_DEST; Called Number=6102682T

*Mar 23 13:22:44.501: //-1/186615328026/DPM/dpMatchPeersCore:

   Result=Success(0) after DP_MATCH_DEST

*Mar 23 13:22:44.501: //-1/186615328026/DPM/dpMatchPeersMoreArg:

   Result=SUCCESS(0)

   List of Matched Outgoing Dial-peer(s):

     1: Dial-peer Tag=30

*Mar 23 13:22:44.509: //-1/186615328026/DPM/dpMatchPeersCore:

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

*Mar 23 13:22:44.509: //-1/186615328026/DPM/dpMatchPeersCore:

   Match Rule=DP_MATCH_DEST; Called Number=6102682

*Mar 23 13:22:44.509: //-1/186615328026/DPM/dpMatchPeersCore:

   Result=Success(0) after DP_MATCH_DEST

*Mar 23 13:22:44.509: //-1/186615328026/DPM/dpMatchPeersMoreArg:

   Result=SUCCESS(0)

   List of Matched Outgoing Dial-peer(s):

     1: Dial-peer Tag=30

Thanks

- Please rate helpful posts -
Everyone's tags (1)
11 REPLIES
New Member

Problems with incoming dialpeer

Hi , only thing that i can think of is ... "T" in your incoming dial peer (50) . my weird guess is router doesn't wait for "T" time to match dial peer when it can match it with dial peer 30 .

in first case ... (no port 2/0) ... only dial peer to which it could match has 'incoming called-number 610268T' where T says it to wait . so it waits and matches it when wait is over.

in 2nd case (with port 2/0) ... it has two dial peers .. one (dial peer 50) says it to wait for "T" time before matching , while other (dial peer 30) doesn't need to wait for  "T" time before matching . so it matches .

Now if I am wrong (which i strongly  feel i am , as i have never heard this crap before) , then it means .. presence of keyword "T" in any dial peer affects the router's dial peer matching time even for other dial peers ... and if we configure matching syntax as ".T" ... doesn't matter whatever number we dial ...router will surely wait for T time before matching dial peer .

so ... I don't know what is right and what is wrong . please guide me also .

New Member

Problems with incoming dialpeer

Hi aman,

thanks for your reply.

I have replaced the "incoming-called number 610268T" with "610268.." and called 61026820. This is now work with the outgoing dial-peer configured to a port. So you're right.

But now I have the problem that the incoming dial-peer is not waiting for the overlap timer to collect the remaining digits

That's is a debug from a digit-by-digit calling to the number 610268-20

*Mar 23 14:53:12.171: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:

   Calling Number=600000419, Called Number=6102682, Voice-Interface=0x8432461C,

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

   Peer Info Type=DIALPEER_INFO_SPEECH

*Mar 23 14:53:12.171: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:

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

*Mar 23 14:53:12.171: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:

   Calling Number=600000419, Called Number=6102682, Voice-Interface=0x0,

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

   Peer Info Type=DIALPEER_INFO_FAX

*Mar 23 14:53:12.171: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:

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

*Mar 23 14:53:12.880: //-1/BF1FBFBC802A/DPM/dpMatchPeersCore:

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

*Mar 23 14:53:12.880: //-1/BF1FBFBC802A/DPM/dpMatchPeersCore:

   Match Rule=DP_MATCH_DEST; Called Number=61026820

*Mar 23 14:53:12.880: //-1/BF1FBFBC802A/DPM/dpMatchPeersCore:

   Result=Partial Matches(1) after DP_MATCH_DEST

*Mar 23 14:53:12.880: //-1/BF1FBFBC802A/DPM/dpMatchPeersMoreArg:

   Result=MORE_DIGITS_NEEDED(1)

*Mar 23 14:53:18.874: //-1/BF1FBFBC802A/DPM/dpMatchPeersCore:

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

*Mar 23 14:53:18.874: //-1/BF1FBFBC802A/DPM/dpMatchPeersCore:

   Match Rule=DP_MATCH_DEST; Called Number=61026820T

*Mar 23 14:53:18.878: //-1/BF1FBFBC802A/DPM/dpMatchPeersCore:

   Result=Success(0) after DP_MATCH_DEST

*Mar 23 14:53:18.878: //-1/BF1FBFBC802A/DPM/dpMatchPeersMoreArg:

   Result=SUCCESS(0)

   List of Matched Outgoing Dial-peer(s):

     1: Dial-peer Tag=30

*Mar 23 14:53:18.882: //-1/BF1FBFBC802A/DPM/dpMatchPeersCore:

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

*Mar 23 14:53:18.882: //-1/BF1FBFBC802A/DPM/dpMatchPeersCore:

   Match Rule=DP_MATCH_DEST; Called Number=61026820

*Mar 23 14:53:18.886: //-1/BF1FBFBC802A/DPM/dpMatchPeersCore:

   Result=Success(0) after DP_MATCH_DEST

*Mar 23 14:53:18.886: //-1/BF1FBFBC802A/DPM/dpMatchPeersMoreArg:

   Result=SUCCESS(0)

   List of Matched Outgoing Dial-peer(s):

     1: Dial-peer Tag=30

- Please rate helpful posts -
New Member

Problems with incoming dialpeer

Hi ,

thanks ,

is following link useful to you ?

http://www.cisco.com/en/US/tech/tk801/tk133/technologies_tech_note09186a00800b48cb.shtml

i think it is related to your problem .

VIP Super Bronze

Re: Problems with incoming dialpeer

Hi,

You ca resolve this by using preferences on  the dial-peers. So give dial-peer 50 a lower preference  and dial-peer 30 a higher preference. SO dial-peer 30 will have preference 1 and dial-peer 50 can be left at the default of preference 0 . You then need to change the voice gateway dial-peer selection algorithm using the command

dial-peer hunt 2,

the dial-peer hunt available are as follows:

0—Longest match in phone number, explicit preference, random selection.

1—Longest match in phone number, explicit preference, least recent use.

2—Explicit preference, longest match in phone number, random selection.

3—Explicit preference, longest match in phone number, least recent use.

4—Least recent use, longest match in phone number, explicit preference.

5—Least recent use, explicit preference, longest match in phone number.

6—Random selection.

7—Least recent use 0—Longest match in phone number, explicit preference, random selection.
1—Longest match in phone number, explicit preference, least recent use.
2—Explicit preference, longest match in phone number, random selection.
3—Explicit preference, longest match in phone number, least recent use.
4—Least recent use, longest match in phone number, explicit preference.
5—Least recent use, explicit preference, longest match in phone number.
6—Random selection.
7—Least recent use

Please rate all useful posts "The essence of christianity is not the enthronement but the obliteration of self --William Barclay"
New Member

Problems with incoming dialpeer

Hi aokanlawon,

I tried it as you described it, but it's still the same problem. The call is directly matched to dial-peer 30

new configuration

dial-peer voice 30 pots

preference 10

destination-pattern ...T

port 2/0

!

dial-peer voice 50 pots

translation-profile incoming ISDN

incoming called-number 610268T  ### I tried it with 610268.. and with 610268T

direct-inward-dial

!

dial-peer voice 51 pots

incoming called-number 6102680

direct-inward-dial

!

dial-peer voice 11 pots

destination-pattern 20

port 3/0

!

- Please rate helpful posts -
VIP Super Bronze

Problems with incoming dialpeer

did you change your dial-peer hunt algorithm to 2?

Please rate all useful posts "The essence of christianity is not the enthronement but the obliteration of self --William Barclay"
New Member

Problems with incoming dialpeer

Yes, I also configured dial-peer hunt 2. Just forgot to write here.

- Please rate helpful posts -
VIP Super Bronze

Problems with incoming dialpeer

In this scenario, you need to avoid using overlapping patterns as I think this is the problem you are running into. So on your dial-peer 30 why dont you define a more specific dial-peer rather than ...T Or use should use a prefix to differentiate between your incoming and out bound calls..Eg dial-peer 30 can be destination-pattern 9T

Please rate all useful posts "The essence of christianity is not the enthronement but the obliteration of self --William Barclay"
New Member

Problems with incoming dialpeer

Of course, this would be possible. But my target is to use it without a prefix.

By now I figured out this solution:

dial-peer voice 1000 pots

destination-pattern 6[^10268].T

no digit-strip

port 2/0

dial-peer voice 1001 pots

destination-pattern [0-5,7-9]..T

no digit-strip

port 2/0

I tried this  already a couple of days ago, but with this configuration I had some problems with incoming calls. I will make tomorrow some test and post the debug.

- Please rate helpful posts -

Problems with incoming dialpeer

Why dont you just strip digits on the ISDN voice port?

voice translation-rule 1

rule 1 /^61026802/ /2/       (this will strip called number to 2. , so you might need to tweak this to include you whole DID                                              block)

voice translation-profile PSTN_Inbound

translate called 1

voice-port 2/0

translation-profile incoming PSTN_Inbound

dial-peer voice 30 pots

destination-pattern 0T           (make this pattern whatevcer you want to make outbound PSTN calls, this is an example                                                   that uses 0 for extrenal calls)

progress_ind setup enable 3

incoming called-number .

fax rate disable

direct-inward-dial

port 2/0

dial-peer voice 11 pots

#in- and outgoing dialpeer for my analog phone

destination-pattern 20

port 3/0

Please remember to rate useful posts, by clicking on the stars below.

New Member

Problems with incoming dialpeer

Hi minkdennis,

If i would do that, the nummber is translated before it arrived complete. Because we are using digit-by-digit calling in Germany, the first ISDN message is 610268 and a little bit later there is a second message with the 0 to complete the number to 61026820. So I need to wait in the dial-peer witht the T pattern for the complete number.

But in this case the the incoming call is matched to my outgoing dial-peer.

I tried it with this to prevent

dial-peer voice 1000 pots

destination-pattern 6[^10268].T

no digit-strip

port 2/0

dial-peer voice 1001 pots

destination-pattern [0-5,7-9]..T

no digit-strip

port 2/0

But some calls are still routed to the dial-peer 1001 as incoming dial-peer.

- Please rate helpful posts -
694
Views
0
Helpful
11
Replies