07-13-2015 12:14 AM - edited 03-12-2019 10:17 AM
Introduction
Some time it requires creating multiple outbound dial-peers for the same destination-pattern such as in a multi-cluster (various Subscribers) environment.
CUBE 10.0.0 [IOS 15.4(2)T / IOS-XE 3.12] introduces the concept of Destination Server Group, which supports multiple session targets (up to 5) to be defined in a group and applied to a single outbound dial-peer. This reduces the need to configure multiple dial-peers with the same capabilities and destination-patterns but different destination target IP Addresses.
Multiple outbound dial-peers are defined when an incoming call is required to hunt through different destinations. Each destination requires a separate outbound dial-peer setup even if the same call capability setup is used.
Destination server group supports multiple destinations that can be defined in a new “voice class server-group <tag>” setup.
A sip dial-peer can reference the server-group by a new “session server-group <tag>” command line.
The destinations of a server-group will then be used for outgoing call setup when a SIP dial-peer with server-group is selected as an outbound dial-peer.
Destination Server Group
Supports multiple destinations (session targets) be defined in a group and applied to a single outbound dial-peer
Once an outbound dial-peer is selected to route an outgoing call, multiple destinations within a server group will be sorted in either round robin or preference [default] order
This reduces the need to configure multiple dial-peers with the same capabilities but different destinations. E.g. Multiple subscribers in a cluster
Once an outbound dial-peer is selected to route an outgoing call, multiple destinations within a server group will be sorted in either round robin or preference [default] order.
Configuration Example
voice class server-group 1
hunt-scheme {preference | round-robin}
ipv4 1.1.1.1 preference 5
ipv4 2.2.2.2
ipv4 3.3.3.3 port 3333 preference 3
ipv6 2010:AB8:0:2::1 port 2323 preference 3
ipv6 2010:AB8:0:2::2 port 2222
dial-peer voice 100 voip
description Outbound DP
destination-pattern 1234
session protocol sipv2
codec g711ulaw
dtmf-relay rtp-nte
session server-group 1
Verify
show voice class server-group 1
Good one +5
-Terry
Thank you Terry. All your comments are really encouraging.
Regards
Lavanya
Nice doc. What is the minimum IOS train supports this feature?
Thanks
Hi Rahul
Thanks for your comments. This feature is supported in, Cisco IOS XE Release 3.11S 15.4(1)T. Refer this link for more information,
http://www.cisco.com/c/en/us/td/docs/ios-xml/ios/voice/dialpeer/configuration/15-mt/vd-15-mt-book/multiple-server-groups.pdf
Regards
Lavanya
Technical community Manager
Hi
one question the voice class server groups work fine, but if the first ipv4 is busy-out the call wait 60seg to send digit to another ipv4.
it's long time to wait.
you have any way to reduce these time. the ping option only word when you put session target ipv4 directly on dial-peer.
Have you reduced the retry invite under slip-up.
voice service voip
sip
sip-ua
retry invite 2
timers trying 150
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: