VoIP Dial-peer load balancing

[guillermohurtado]

Hello,

What is the best approach to balance load between two VoIP dialpeers that point to two different session target?

Set the same preference option for both dialpeers?? A example:

dial-peer voice 11111 voip

destination-pattern 9999999

preference 1

progress_ind setup enable 3

session protocol sipv2

session target ipv4:74.125.45.103

dtmf-relay rtp-nte

fax protocol t38 ls-redundancy 0 hs-redundancy 0 fallback cisco

dial-peer voice 22222 voip

destination-pattern 9999999

preference 1

progress_ind setup enable 3

session protocol sipv2

session target ipv4:69.147.76.15

dtmf-relay rtp-nte

fax protocol t38 ls-redundancy 0 hs-redundancy 0 fallback cisco

Thanks in advance.

[paolo bevilacqua]

They seem to be the same ?!?

[fabien.damien]

Sorry for the confusion, i have used the below dial peers and the 3002 is always matched as the "show call hist voi br" is showing.

dial-peer voice 3002 voip

destination-pattern 3002

session protocol sipv2

session target ipv4:10.1.1.101

dtmf-relay rtp-nte h245-signal h245-alphanumeric

codec g711ulaw

no vad

!

dial-peer voice 3001 voip

destination-pattern 3002

session protocol sipv2

session target ipv4:10.1.1.105

dtmf-relay rtp-nte h245-signal h245-alphanumeric

codec g711ulaw

no vad

13DF : 185 341511720ms.134 +60 +5130 pid:3002 Originate 3002

dur 00:00:05 tx:250/40000 rx:0/0 10 (normal call clearing (16))

IP 10.1.1.103:17058 SRTP: off rtt:0ms pl:0/0ms lost:0/0/0 delay:0/0/0ms g711ulaw TextRelay: off

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

long duration call detected:n long dur callduration :n/a timestamp:n/a

13E6 : 186 341511760ms.135 +10 +5100 pid:85 Answer 571

dur 00:00:05 tx:0/0 rx:203/32480 10 (normal call clearing (16))

IP 10.1.1.103:18174 SRTP: off rtt:0ms pl:0/0ms lost:0/0/0 delay:0/0/0ms g711ulaw TextRelay: off

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

long duration call detected:n long dur callduration :n/a timestamp:n/a

13EB : 187 341548470ms.136 +80 +3950 pid:556 Answer 571

dur 00:00:03 tx:0/0 rx:192/30720 10 (normal call clearing (16))

IP 192.168.0.11:26840 SRTP: off rtt:0ms pl:0/0ms lost:0/0/0 delay:0/0/0ms g711ulaw TextRelay: off

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

long duration call detected:n long dur callduration :n/a timestamp:n/a

13EB : 188 341548490ms.137 +50 +3940 pid:3002 Originate 3002

dur 00:00:03 tx:192/30720 rx:0/0 10 (normal call clearing (16))

IP 10.1.1.103:18110 SRTP: off rtt:0ms pl:0/0ms lost:0/0/0 delay:0/0/0ms g711ulaw TextRelay: off

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

long duration call detected:n long dur callduration :n/a timestamp:n/a

13F2 : 189 341548520ms.138 +0 +3930 pid:85 Answer 571

dur 00:00:03 tx:0/0 rx:145/23200 10 (normal call clearing (16))

IP 10.1.1.103:19514 SRTP: off rtt:0ms pl:0/0ms lost:0/0/0 delay:0/0/0ms g711ulaw TextRelay: off

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

long duration call detected:n long dur callduration :n/a timestamp:n/a

13F7 : 190 341652040ms.139 +80 +7260 pid:556 Answer 571

dur 00:00:07 tx:0/0 rx:358/57280 10 (normal call clearing (16))

IP 192.168.0.11:26844 SRTP: off rtt:0ms pl:0/0ms lost:0/0/0 delay:0/0/0ms g711ulaw TextRelay: off

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

long duration call detected:n long dur callduration :n/a timestamp:n/a

13F7 : 191 341652060ms.140 +40 +7260 pid:3002 Originate 3002

dur 00:00:07 tx:358/57280 rx:0/0 10 (normal call clearing (16))

IP 10.1.1.103:16832 SRTP: off rtt:0ms pl:0/0ms lost:0/0/0 delay:0/0/0ms g711ulaw TextRelay: off

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

long duration call detected:n long dur callduration :n/a timestamp:n/a

13FE : 192 341652080ms.141 +20 +7250 pid:85 Answer 571

dur 00:00:07 tx:0/0 rx:311/49760 10 (normal call clearing (16))

IP 10.1.1.103:16810 SRTP: off rtt:0ms pl:0/0ms lost:0/0/0 delay:0/0/0ms g711ulaw TextRelay: off

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

long duration call detected:n long dur callduration :n/a timestamp:n/a

[paolo bevilacqua]

You must have something else causing that, In my experience load balancing works as described.

[fabien.damien]

hi,

I discovered the problem, i needed to add "preference 1" on both dialpeers as mentioned in the SRND.

[paolo bevilacqua]

Where exactly is mentioned ? I wasn't aware of this requirement.

[fabien.damien]

now you are :) page 61. cvp7srnd

[paolo bevilacqua]

sorry, I check page 61, PDF version of CUCM V7 SRND and can't find that, could you point me to a section and page in that book ?

[suaybaguio]

Both dial-peers have the same destination.