Diall-peer issue

Unanswered Question
Mar 25th, 2009
User Badges:

Can someone help me with the folloing dial-peer problem?

CallManager Ver6 withh voip Gateway

- when i dial internatioal call 000.... it are using some time voip and other time pots dial peer :

The router pater its oK


dial-peer voice 1 pots

destination-pattern 0T

port 0/0/0:15

!

dial-peer voice 8 pots

description ** BRI pots dial-peer **

translation-profile incoming 2300

incoming called-number .

direct-inward-dial

port 0/0/0:15

!

dial-peer voice 4 pots

destination-pattern 000T

port 0/0/0:15

prefix 00

!

dial-peer voice 500 voip

destination-pattern 5..

session target ipv4:172.19.101.99

dtmf-relay h245-alphanumeric

codec g711ulaw

!

dial-peer voice 2301 pots

incoming called-number .

direct-inward-dial

port 0/0/0:15

!




!

dial-peer voice 2300 voip

destination-pattern 2602...

session target ipv4:172.19.0.253

incoming called-number .

dtmf-relay h245-alphanumeric

codec transparent


dial-peer voice 300 voip

destination-pattern 3..

session target ipv4:172.19.0.253

dtmf-relay h245-alphanumeric

codec transparent

no vad

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Jaime Valencia Wed, 03/25/2009 - 14:24
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    2011

at least looking at the dial-peers you posted there is no possibility it could use a VoIP dial-peer, destination patterns simply do not match.


check how many digits and what digits you're sending from CUCM to see what dial-peer they would match.


you can run a debug voip ccapi inout to see the whole process of what GW receives and processes, dial-peers matched will be shown there


HTH


java


if this helps, please rate

Nicholas Matthews Wed, 03/25/2009 - 15:01
User Badges:
  • Red, 2250 points or more

Can you post "show dial-peer voice summary"? This is the best way to look at the dial plan.


As well, do a 'debug voip dialpeer' for both the good and the bad calls and make sure the numbers are as you expect them.



It looks like you have an overlapping dial plan between dial peer 1 and 4. I wouldn't be surprised if it was load balancing between those two dial peers. Changing that would require changing the way you dial one of those two types of numbers.


Additionally, they're doing the same thing. You could get rid of dial peer 4 completely.


hth,

nick


-nick

Afragoso2009 Thu, 03/26/2009 - 02:40
User Badges:

I putting in attachments the voip ccapi debug - showing a call to 000351.........

using Voip Dial peer. I am not seeing why its happining



dial-peer voice summary

dial-peer hunt 0

AD PRE PASS OUT

TAG TYPE MIN OPER PREFIX DEST-PATTERN FER THRU SESS-TARGET STAT

PORT

500 voip up up 5.. 0 syst ipv4:172.19.101.99

2301 pots up up 0 down

0/0/0:15

4 pots up up 00 000T 0 up

0/0/0:15

1 pots up up 0T 0 up

0/0/0:15

8 pots up up 0 down

0/0/0:15

2300 voip up up 2602... 0 syst ipv4:172.19.0.253

300 voip up up 3.. 0 syst ipv4:172.19.0.253



Attachment: 
Nicholas Matthews Thu, 03/26/2009 - 09:40
User Badges:
  • Red, 2250 points or more

What happens if you do this:


dial-p v 1

preference 1


or


dial-p v 4

preference 2




These dial peers are being matched for both types of international and normal calls.


-nick

Afragoso2009 Thu, 03/26/2009 - 10:00
User Badges:

Hi

I continue tha have the 000... call match with the voip DP 2300


Ayodeji Okanlawon Thu, 03/26/2009 - 10:19
User Badges:
  • Super Bronze, 10000 points or more
  • Cisco Designated VIP,

    2017 IP Telephony

Hi,


Here is your problem...When a call is passed from Callmanager to a Voice gateway, it uses a voip dial-peer leg. In normal situations, you should have an incoming voip dial-peer just as you have for incoming pots dial-peer.


Your call leg in this situation will be 2..One coming from callmanager to the gateway and the other from the gateway to the PSTN.


In this case, the gateway is using the dial-peer 2300 which has incoming called number. (because th . aloow all calls) as its incoming dial-peer and using dial-peer 4 for outbound calls.


To resolve this porblem, configure the following


dial-peer voice 99999 voip

voice-class codec 1

incoming called-number .

dtmf-relay h245-alphanumeric

fax rate disable

no vad


HTH

Afragoso2009 Thu, 03/26/2009 - 10:52
User Badges:

I keep all the dial-peer and add this one but the problem is the same


Ayodeji Okanlawon Thu, 03/26/2009 - 11:00
User Badges:
  • Super Bronze, 10000 points or more
  • Cisco Designated VIP,

    2017 IP Telephony

Did you see this post I sent to you...


Hi,


Here is your problem...When a call is passed from Callmanager to a Voice gateway, it uses a voip dial-peer leg. In normal situations, you should have an incoming voip dial-peer just as you have for incoming pots dial-peer.


Your call leg in this situation will be 2..One coming from callmanager to the gateway and the other from the gateway to the PSTN.


In this case, the gateway is using the dial-peer 2300 which has incoming called number. (because th . aloow all calls) as its incoming dial-peer and using dial-peer 4 for outbound calls.


To resolve this porblem, configure the following


dial-peer voice 99999 voip

voice-class codec 1

incoming called-number .

dtmf-relay h245-alphanumeric

fax rate disable

no vad


HTH



Afragoso2009 Thu, 03/26/2009 - 11:04
User Badges:

Yes

I added this dial-peer bu the problem is still the same


Ayodeji Okanlawon Thu, 03/26/2009 - 11:21
User Badges:
  • Super Bronze, 10000 points or more
  • Cisco Designated VIP,

    2017 IP Telephony

OK..add the command preference 1 under this dial-peer and preference 2 under the pots dial-peer


so you will have


dial-peer voice 9999 voip

incoming called-number.

preference 1


and dial-peer voice 4 pots

preference 2


then do a debug voip caapi inout and post the out put here..pls do this quickly...need to go home (waiting cos of you:)

Ayodeji Okanlawon Thu, 03/26/2009 - 11:32
User Badges:
  • Super Bronze, 10000 points or more
  • Cisco Designated VIP,

    2017 IP Telephony

Dont reboot the router..you have configured your incoming dial-peer 2300 voip wrongly. You should not have any destination-pattern on it. If you do all your calls from callmanager will be sent back to that destination pattern address...Which I believe is callmanager!

Ayodeji Okanlawon Thu, 03/26/2009 - 11:37
User Badges:
  • Super Bronze, 10000 points or more
  • Cisco Designated VIP,

    2017 IP Telephony

Afro,


do 2 things


1. Either remove the incoming called-number . from the dial-peer 2300 or remove the destination-pattern from it.


if you remove the incoming called-number . from it, create a new dial-peer as I told you before. No destination pattern on it

Afragoso2009 Thu, 03/26/2009 - 11:55
User Badges:

No its using always the dp 99999 but the call cannot complety


Afragoso2009 Thu, 03/26/2009 - 12:09
User Badges:

And Now I can make a call to 0001508....... (USA) but to 000351.........(PORTUGAL) its no possible

Ayodeji Okanlawon Thu, 03/26/2009 - 12:55
User Badges:
  • Super Bronze, 10000 points or more
  • Cisco Designated VIP,

    2017 IP Telephony

Ok.


send debug output

Afragoso2009 Thu, 03/26/2009 - 14:59
User Badges:

This may actual dial-peerdial-peer voice 2301 pots

incoming called-number .

direct-inward-dial

port 0/0/0:15

!

dial-peer voice 1 pots

destination-pattern 0T

port 0/0/0:15

!

dial-peer voice 8 pots

description ** BRI pots dial-peer **

translation-profile incoming 2300

incoming called-number .

direct-inward-dial

port 0/0/0:15

!

dial-peer voice 300 voip

preference 4

destination-pattern 3..

session target ipv4:172.19.0.253

dtmf-relay h245-alphanumeric

codec transparent

no vad

!

dial-peer voice 99999 voip

preference 1

voice-class codec 1

incoming called-number .

dtmf-relay h245-alphanumeric

fax rate disable

no vad

!

dial-peer voice 2300 voip

preference 2

destination-pattern .

session target ipv4:172.19.0.253

dtmf-relay h245-alphanumeric

codec transparent

!

dial-peer voice 2 pots

destination-pattern 000351T

port 0/0/0:15

prefix 00351



Now the situation is no so bad

Some time tha call are using the right dial-peer but other time it use the 2300 for outgoing. In the case the call are ring in an internal Phone withe the last 3 digit .I meas if I call 000351961245313 the call ring in the IP Phone 313


In attach the debug for boot situation



Attachment: 
Ayodeji Okanlawon Thu, 03/26/2009 - 15:06
User Badges:
  • Super Bronze, 10000 points or more
  • Cisco Designated VIP,

    2017 IP Telephony

You need to remove this dial-peer config. You dont need it and its causing you problems. This is why your calls are ringing on ip phone 313. Because all calls coming from callmanager is going back to callmanager


dial-peer voice 2300 voip

preference 2

destination-pattern .

session target ipv4:172.19.0.253

dtmf-relay h245-alphanumeric

codec transparent


Afragoso2009 Fri, 03/27/2009 - 04:53
User Badges:

Hi

This dial-peer is used to receive incoming DDI call

If I remove it the incoming DDI call from outsid stop to work

Ayodeji Okanlawon Fri, 03/27/2009 - 06:56
User Badges:
  • Super Bronze, 10000 points or more
  • Cisco Designated VIP,

    2017 IP Telephony

Nooooooooooooooooooooooooooo! The dial-peer used to receive incoming DDI is this


dial-peer voice 2301 pots

incoming called-number .

direct-inward-dial

port 0/0/0:15

!


You dont need that one! dial-peer 2300!


Afragoso2009 Fri, 03/27/2009 - 09:29
User Badges:

Sure but the call will stop at the Gateway , dont came to callmanager

Please clarify me if I am wrong



Ayodeji Okanlawon Fri, 03/27/2009 - 10:06
User Badges:
  • Super Bronze, 10000 points or more
  • Cisco Designated VIP,

    2017 IP Telephony

Ok I see that yoiu have changed the destination pattern. on dial-peer 2300. Ok you can leave it but remove the comand "incoming called number." on it.


This is the way it works. Calls coming from outside will first of all match dial-peer 2301, after that they will then match either


dial-peer voice 300 voip

destination-pattern 3..

session target ipv4:172.19.0.253

dtmf-relay h245-alphanumeric

codec transparent

no vad


or


dial-peer voice 500 voip

destination-pattern 5..

session target ipv4:172.19.0.253

dtmf-relay h245-alphanumeric

codec transparent

no vad


Depending on the number called.


Calls from callmanager will macth dial-peer 9999 voip.



Afragoso2009 Wed, 04/01/2009 - 05:25
User Badges:

Hi aokanlawon

Last two days i was having a problem with date an time , my Call Manager was not accepting the 31 March 2009.

Some one adive here in forum that is a CCM 6.0 bug

I still having a dial-peer problem

But I heady now to continue fixing this issue

Afragoso2009 Wed, 04/01/2009 - 09:36
User Badges:

Hi

For this moment the situation its not so bad

All the call to outid is using dial-peer 1 but concerning to the patern 000351.......... I stil continus having a problem , some time the call can be done and other not


dial-peer voice 1 pots

destination-pattern 0T

port 0/0/0:15



Concerning the dial peer to DID

dial-peer voice 300 voip

preference 4

destination-pattern 26023..

session target ipv4:172.19.0.253

dtmf-relay h245-alphanumeric

codec transparent



I try remove the "destination-pattern 26023.." bu the call stop on the Gateway , I means dont go to the dialed Ext




Actions

This Discussion