Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements
Users might experience few discrepancies in Search results. We are working on this on our side. We apologize for the inconvenience it may have caused.
New Member

VoIP Dial-peer load balancing

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.

1 ACCEPTED SOLUTION

Accepted Solutions

Re: VoIP Dial-peer load balancing

Yes, the default in this case would be to send calls to the 2 dial peers in a random order which essentially works out to be load balancing. Also, the "preference 1" command is not necessary since the default is preference 0. Without this command, both dial peers would still have the same preference.

Hope this helps.

Brandon

22 REPLIES

Re: VoIP Dial-peer load balancing

Yes, the default in this case would be to send calls to the 2 dial peers in a random order which essentially works out to be load balancing. Also, the "preference 1" command is not necessary since the default is preference 0. Without this command, both dial peers would still have the same preference.

Hope this helps.

Brandon

New Member

Re: VoIP Dial-peer load balancing

Thanks for your answer.

I was wondering if there is something like Trunkgroup, but instead of working with channels work with IP Address?

Regards.

Re: VoIP Dial-peer load balancing

Not to my knowledge. Another way to accomplish this would be by using DNS, such as:

session target dns:device.domain.com

You could then use DNS to load balance.

I think multiple dial peers with IP addresses and the same preference would be a better solution because it does not depend on DNS.

Hope this helps.

Brandon

New Member

Re: VoIP Dial-peer load balancing

where i can find info on load balancing using dns?

thanks,

Re: VoIP Dial-peer load balancing

The exact implementation would depend on the DNS server that you are using. The following link gives a general description.

http://en.wikipedia.org/wiki/Round_robin_DNS

Essentially, load balancing using DNS uses a round-robin algorithm to distribute the load. This method is not perfect, but may do the job for you.

Hope this helps.

Brandon

New Member

Re: VoIP Dial-peer load balancing

Hi Brandon,

So it would load balance and not select the first dial peer configured?

Thanks,

Re: VoIP Dial-peer load balancing

With DNS load balancing, you would only have one dial peer. This dial peer would point to a FQDN such as gateways.domain.com. Your DNS server would then take care of the load balancing by distributing the calls among IP addresses that it has configured for gateways.domain.com.

Brandon

Re: VoIP Dial-peer load balancing

I would need to look into this more - but I believe IOS may cache the DNS reference it receives. I'm not 100% positive if it receives a reply with multiple IP addresses that it load balances. It should, just never seen or tested it myself. I would check this before depending on it.

-nick

New Member

Re: VoIP Dial-peer load balancing

Hi Brandon,

would you have a document that explains the configuration needed on the dns server and the gateyway? configuring the dns server seems challenging.

Another option would be to load balance using dial peers, is it done using hunt groups?

thanks for your feedback,

New Member

Re: VoIP Dial-peer load balancing

I've only seen POTS peers set up for hunt groups. I am curious how dial peers with IP addressing and not DNS will load balance. I thought the router would take the first configured dial peer in the configuration if two dial peers had the same match.

Hall of Fame Super Gold

Re: VoIP Dial-peer load balancing

Same preference DPs are used round-robin, no matter if pots or voip.

That pretty much summarizes the way it works.

New Member

Re: VoIP Dial-peer load balancing

Great, thanks.

Hall of Fame Super Gold

Re: VoIP Dial-peer load balancing

You're welcome, thank you for the nice rating and good luck.

New Member

Re: VoIP Dial-peer load balancing

Hi,

i have used these the below dial-peers and only the first one is matched:

dial-peer voice 3001 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 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

thanks for your feedback,

Hall of Fame Super Gold

Re: VoIP Dial-peer load balancing

They seem to be the same ?!?

New Member

Re: VoIP Dial-peer load balancing

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

Hall of Fame Super Gold

Re: VoIP Dial-peer load balancing

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

New Member

Re: VoIP Dial-peer load balancing

hi,

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

Hall of Fame Super Gold

Re: VoIP Dial-peer load balancing

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

New Member

Re: VoIP Dial-peer load balancing

now you are :) page 61. cvp7srnd

Hall of Fame Super Gold

Re: VoIP Dial-peer load balancing

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 ?

New Member

Re: VoIP Dial-peer load balancing

Both dial-peers have the same destination.

1659
Views
5
Helpful
22
Replies
CreatePlease to create content