Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Community Member

Dial-peer problem

Hello all,

There?s my scenario:

Router A conected to a PBXA(dns 4XXX).

Router B conected to a PBXB(dns 6XXX).

Router A conf:

dial-peer voice 6 voip

destination-pattern 6...

session target ipv4:10.1.1.1

req-qos guaranteed-delay

ip precedence 5

dial-peer voice 1 pots

destination-pattern 4...

direct-inward-dial

port 2/0:15

prefix 4

Router B conf:

dial-peer voice 1 voip

description Llamadas Central Madrid

destination-pattern 4...

session target ipv4:10.1.1.2

req-qos guaranteed-delay audio

ip qos dscp cs5 media

dial-peer voice 6 pots

description Corporativos

destination-pattern 6...

direct-inward-dial

port 0/0/0:15

When I make a call from the PBx A with number 4000 to a 6xxx number I have a 12 seconds delay before the call run, I tested to make the call without the dialpeer 1 in router B and the call progress without delay.

any ideas??

1 ACCEPTED SOLUTION

Accepted Solutions
Community Member

Re: Dial-peer problem

Hi Carlos,

What's happening is the calling number (4149) is being matched to dial-peer 1. You'll see there's a 10 second delay between 11:26:29 and 11:26:39 just after it matches to dial-peer=1. When you remove the dial-peer it works OK because there's NO_MATCH.

On the one I've just implemented I had the PBX guys prefix 3 digit "steering" codes that get stripped off by the destination PBX, so I don't have this problem.

For example PBX A prepends 867 to the number dialled, which is sent to Router B. Because PBX B prepends 897 to it's dialled numbers, there's not a match.

Here's an extract from my config...

dial-peer voice 1 voip

description Mt Albert Extensions

destination-pattern 8679....

session target ipv4:10.16.255.252

!

dial-peer voice 1001 pots

description From Mt Albert

destination-pattern 8976T

port 0/0/0:0

!

In my case I had the PBX add and remove the 3 digit steering prefixes but you could simply add a translation-rule to your dial-peers so that router A adds a prefix, then router B strips it before sending to PBX B.

I hope my explaination's understandable

15 REPLIES
Community Member

Re: Dial-peer problem

Hello Carlos

Have some questions:

Are those the only two dial-peers on your system?

Are the calls on the other way working fine? (6000 calling to 4xxx)

Can you place a call 4000 to 6xxx and do a show call active voice brief

You will find there both legs of the call and you'll find out which dial peer is being matched on each one.

Then repeat the excersise removing the dial-peer to see which dial-peer works without delay.

Also, I see a prefix 5 on the first dial-peer (the "forward digits all" command could have work also) but I do not see a prefix 6 on the other pots dial-peer. Is that fine?

Community Member

Re: Dial-peer problem

Hi Jadidisitel,

thanks for your answer, here is the result from the call active voice command:

With dial-peer 1 (4...)

Telephony call-legs: 0

SIP call-legs: 0

H323 call-legs: 1

MGCP call-legs: 0

SCCP call-legs: 0

Multicast call-legs: 0

Total call-legs: 1

967 : 16444 -1232641072ms.1 +-1 pid:1 Answer 4199 connected

dur 00:00:00 tx:0/0 rx:0/0

IP 10.1.1.1:17806 SRTP: off rtt:0ms pl:0/0ms lost:0/0/0 delay:0/0/0ms g729r8 pre-ietf

media inactive detected:n media contrl rcvd:n/a timestamp:n/a

Telephony call-legs: 0

SIP call-legs: 0

H323 call-legs: 1

MGCP call-legs: 0

SCCP call-legs: 0

Multicast call-legs: 0

Total call-legs: 1

Without the dialpeer 1 (4...)

Telephony call-legs: 1

SIP call-legs: 0

H323 call-legs: 1

MGCP call-legs: 0

SCCP call-legs: 0

Multicast call-legs: 0

Total call-legs: 2

973 : 16450 -1232536202ms.1 +-1 pid:0 Answer 4199 connected

dur 00:00:00 tx:149/2942 rx:0/0

IP 10.1.1.1:19408 SRTP: off rtt:21ms pl:0/0ms lost:0/0/0 delay:70/260/10ms g729r8

media inactive detected:n media contrl rcvd:n/a timestamp:n/a

973 : 16451 -1232536122ms.1 +-1 pid:6 Originate 6445 connecting

dur 00:00:00 tx:0/0 rx:149/2942

Tele 0/0/0:15 (16451) [0/0/0.1] tx:5520/2960/0ms g729r8 noise:-84 acom:6 i/0:-79/-79 dBm

Telephony call-legs: 1

SIP call-legs: 0

H323 call-legs: 1

MGCP call-legs: 0

SCCP call-legs: 0

Multicast call-legs: 0

Total call-legs: 2

I think that the dialpeer is using the "calling number" instead the "called numer", and therefore it use the dialpeer 1 instead the dialpeer I want.

any ideas to resolve this problem?

thanks in advance

Community Member

Re: Dial-peer problem

Hi again Carlos.

The show you posted seems weird, if you notice, there is only one leg on the first one, so I wonder if the call was connected at that time. Anyway, you can see that the in the first show the dial peer being matched is the (pid) 1 and on the second one it turns to be the default dial-peer 0.

So it has to do something with the dial-peer altough I do not see anything out of place there.

could you please wait till the calls are connected and paste the show again. Also, which IOS version are you running on both routers? Are you using an ISDN PRI between the routers?

Gracias

Javier

Community Member

Re: Dial-peer problem

Hola Javier,

The IOS are:

Router A: 3640 12.1(5)T

Router B: 3825 12.3(11)T2

the routers are connected with a point to point line.

with dialpeer

Telephony call-legs: 1

SIP call-legs: 0

H323 call-legs: 1

MGCP call-legs: 0

SCCP call-legs: 0

Multicast call-legs: 0

Total call-legs: 2

117F : 16650 -986312502ms.1 +26600 pid:1 Answer 4149 active

dur 00:00:12 tx:0/0 rx:0/0

IP 10.1.1.1:18722 SRTP: off rtt:0ms pl:0/0ms lost:0/0/0 delay:0/0/0ms g729r8

media inactive detected:n media contrl rcvd:n/a timestamp:n/a

117F : 16651 -986302422ms.1 +16520 pid:6 Originate 6300 active

dur 00:00:12 tx:525/10462 rx:598/11730

Tele 0/0/0:15 (16651) [0/0/0.1] tx:28990/11820/0ms g729r8 noise:-57 acom:45 i/0:-43/-10 dBm

Telephony call-legs: 1

SIP call-legs: 0

H323 call-legs: 1

MGCP call-legs: 0

SCCP call-legs: 0

Multicast call-legs: 0

Total call-legs: 2

without dialpeer

Telephony call-legs: 1

SIP call-legs: 0

H323 call-legs: 1

MGCP call-legs: 0

SCCP call-legs: 0

Multicast call-legs: 0

Total call-legs: 2

119B : 16656 -986121432ms.1 +2530 pid:0 Answer 4149 active

dur 00:00:11 tx:216/4156 rx:278/5396

IP 10.1.1.1:18778 SRTP: off rtt:25ms pl:4960/0ms lost:0/0/0 delay:60/60/70ms g729r8

media inactive detected:n media contrl rcvd:n/a timestamp:n/a

119B : 16657 -986121352ms.1 +2450 pid:6 Originate 6300 active

dur 00:00:11 tx:278/5396 rx:216/4156

Tele 0/0/0:15 (16657) [0/0/0.1] tx:14100/4210/0ms g729r8 noise:-64 acom:26 i/0:-60/-65 dBm

Telephony call-legs: 1

SIP call-legs: 0

H323 call-legs: 1

MGCP call-legs: 0

SCCP call-legs: 0

Multicast call-legs: 0

Total call-legs: 2

thanks in advance

Community Member

Re: Dial-peer problem

by the way I just change prefix 5 for forward digits all, and in the other dial peer it?s correct that the prefix 6 doesnt appear.

thanks

Community Member

Re: Dial-peer problem

Hi Carlos,

I'm assuming that you're just setting up IP Trunking between the two sites, each PBX and router with a E1/T1 interface?

What I would suggest is run "debug voice dialpeer" on each router. When you dial the phone number you should see the digits immediately appear on the local router. If the digits only appear after the 12 second delay I would suggest that the problem lies with the PBX, possibly trying to go via the PSTN first then reverting back to the E1 trunk when that fails. It could also be that the dial string is configured using the inter-digit timeout rather than specifying that anything that starts with 4 or 6 should go via the E1 trunk (could be 12sec timeout).

I've just done the same thing and it works correctly, the numbers are passed immediately to the router, once the dialpeer is matched, it's passed directly to the remote router.

Hope that helps, let us know how you get on

Cheers,

John

Community Member

Re: Dial-peer problem

thanks for your fast answer John.

yes, the conexion between the router and the PBX is an E1 interface.

I ran a debug voice dialpeer on each router and the digits appear inmediatly in router A, and appear in router B as well. But the call need 12 seconds to initiate progress trough E1 in router B, but if I delete the dial-peer 1 in router B (dial-peer with destination pattern the calling number), it progress inmediatly. ??

Community Member

Re: Dial-peer problem

Hi Carlos,

Sorry I didn't read your post properly. With Dialpeer 1 in place, when you watch the dialpeer debug what dialpeer does it match to?

If the number is 6xxx then it should only match dialpeer 6, so I don't see why dialpeer 1 would have any impact - very strange. Is it possible that PBX B is receiving the call and routing it back to Router B with a "4" prepended to it? - you should see those appearing in the debug as well. What happens if you remove the destination-pattern from dialpeer 1?

Community Member

Re: Dial-peer problem

I don?t think that the PBX B is routing the call back, because there?s no communication between the router and PBX until those 12 seconds of delay.

these are traces with and without dial-peer (the trace without destination-pattern is the same that without dialpeer).

Notice than whith dialpeer 1, it take taht dialpeer, but without dialpeer 1, it takes dialpeer 0.

Thanks in advance

Community Member

Re: Dial-peer problem

Hi Carlos,

What's happening is the calling number (4149) is being matched to dial-peer 1. You'll see there's a 10 second delay between 11:26:29 and 11:26:39 just after it matches to dial-peer=1. When you remove the dial-peer it works OK because there's NO_MATCH.

On the one I've just implemented I had the PBX guys prefix 3 digit "steering" codes that get stripped off by the destination PBX, so I don't have this problem.

For example PBX A prepends 867 to the number dialled, which is sent to Router B. Because PBX B prepends 897 to it's dialled numbers, there's not a match.

Here's an extract from my config...

dial-peer voice 1 voip

description Mt Albert Extensions

destination-pattern 8679....

session target ipv4:10.16.255.252

!

dial-peer voice 1001 pots

description From Mt Albert

destination-pattern 8976T

port 0/0/0:0

!

In my case I had the PBX add and remove the 3 digit steering prefixes but you could simply add a translation-rule to your dial-peers so that router A adds a prefix, then router B strips it before sending to PBX B.

I hope my explaination's understandable

Community Member

Re: Dial-peer problem

Hello Carlos,

is the problem solved ? We had similar issue some time ago. In our case removing "req-qos..." statement from dial-peer config helped.

Regards,

Mikhail

Community Member

Re: Dial-peer problem

The problem was solved adding a prefix to the callingnumber in router A so in router B the calling number doesn?t match with dialpeer 1 (4...)

thanks to everybody

Community Member

Re: Dial-peer problem

I belive the issue might have been resolved by simply adding a peer for incoming w. "incoming called-number ." for incomfing calls.

http://cisco.com/en/US/customer/tech/tk652/tk90/technologies_tech_note09186a008010e6d1.shtml

Hall of Fame Super Gold

Re: Dial-peer problem

232
Views
17
Helpful
15
Replies
CreatePlease to create content