[cisco-voip] dialpeers and trunk groups

Christopher M. Bomba cbomba at s4nets.com
Wed Feb 28 12:06:01 EST 2007


Do you know if you can combine the PRI and the FXO ports in one trunk-group instead of having separate dial-peers for each?


Chris


-----Original Message-----
From: Robert Kulagowski <bob at smalltime.com>
Sent: Wed, February 28, 2007 11:45 am
To: cbomba at s4nets.com
Cc: Lelio Fulgenzi <lelio at uoguelph.ca>, cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] dialpeers and trunk groups

It's working fine here:

trunk group  Local

interface Serial0/1/0:23
  no ip address
  encapsulation hdlc
  isdn switch-type primary-5ess
  isdn incoming-voice voice
  isdn map address . plan isdn type national
  trunk-group Local
  no cdp enable

dial-peer voice 871 pots
  trunkgroup Local
  description 7-digit local call to SBC
  preference 1
  destination-pattern 8[2-9]......
  progress_ind setup enable 3
  clid restrict

dial-peer voice 873 pots
  trunkgroup LongDistance
  description 7-digit local calls to ATT - stuff 203
  preference 3
  destination-pattern 8[2-9]......
  clid restrict
  prefix 203

# sh ver
Cisco IOS Software, 3800 Software (C3845-IPVOICE-M), Version 12.4(11)T1, 
RELEASE SOFTWARE (fc5)

Of course, we're not doing COR stuff, but fundamentally it does work.

Found an issue with FXO ports though; if you had a dead port, or had 
setup a range of ports but only had the first few connected, you'd get 
busy instead of rolling onto the next one in sequence (during a rollout 
we had 8 in the TG, but only two actually connected for testing.  Lots 
of headscratching and examination of dial-peers on what turned out to be 
not dial-peers at all.)  Here's what TAC gave me:

trunk group  FXO
  max-retry 5
  voice-class cause-code 1
  hunt-scheme round-robin
!
voice class cause-code 1
  no-circuit



More information about the cisco-voip mailing list