SIP Trunk definition

Unanswered Question

I was reading in the SRND guide that if you have a SIP trunk defined in callmanager, the way you get CM redundency is thru dial-peers so you point the first dial peer to the primary callmanager and a second dial peer to the backup callmanager.( page 4-17 of the 01/08 CM6)

This is the first I seen this and this is not the way we have done our deployments.

The config we have is cm 5.1.3, IPCC enterprise 7.X and CVP ver 4.1. SIP is the preferred way for connections.

As anyone setup their dial-peers like I mentioned in the SRND guide.. page 4-17 of the 01/08 CM6

I asked some of our local guys and this is new to them ...

Any thiughts or ?

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Brandon Buffin Tue, 09/23/2008 - 04:48


Yes, this is a best practice. So, for incoming calls, you could have something like:

dial-peer voice 1 voip

destination-pattern 1112223333

session target ipv4:

dial-peer voice 2 voip

preference 1

destination-pattern 1112223333

session target ipv4:

If the CM at happened to be down, incoming calls would be handled by the CM at

Hope this helps.



This Discussion