FXO trunk-group

Unanswered Question
Apr 29th, 2007

I have configured 8 fxo ports as members of a singe trunk-group. How do I get the ports to roll over to selecting the next available port if the higher pref ports are not available. By not available I mean phone line not plugged in.

The trunk group will select the highest pref port first and make a call, but if I move the phone line to another FXO port it will not hunt to the new port where i moved the line to, unless I make the new port a higher pref.

This is with outgoing calls.

I'm sure I'm missing something....thanks.

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 3.5 (3 ratings)
Loading.
Paolo Bevilacqua Mon, 04/30/2007 - 01:44

Hi,

The FXO hardware cannot detect automatically if it is connected to a line or not. So, you must manually shutdown ports that are part of a trunk-group but not connected.

Hope this helps, please rate all useful posts using the scrollbox below!

m-ketchum Mon, 04/30/2007 - 07:09

The more I researched the more I became afraid of that. Thanks for the info.

On another note, I decided to config my 3 PRI's as 3 seperate trunk-groups and the 8-FXO's as a 4th trunkgroup. Then I tied the 4 trunk-groups with pref to each of my dial-peers. Do you forsee any issues with this type of config?

!

interface Serial0/0/0:23

description <== PRI 1 ==>

no ip address

encapsulation hdlc

isdn switch-type primary-ni

isdn incoming-voice voice

trunk-group pri_1

no cdp enable

!

interface Serial0/0/1:23

description <== PRI 2 ==>

no ip address

encapsulation hdlc

isdn switch-type primary-ni

isdn incoming-voice voice

trunk-group pri_2

no cdp enable

!

interface Serial0/1/0:23

description <== PRI 3 ==>

no ip address

encapsulation hdlc

isdn switch-type primary-ni

isdn incoming-voice voice

trunk-group pri_3

no cdp enable

!

!

voice-port 0/2/0

trunk-group backup_fxo 1

connection plar opx 3232

!

voice-port 0/2/1

trunk-group backup_fxo 2

connection plar opx 3232

!

voice-port 0/2/2

trunk-group backup_fxo 3

connection plar opx 3232

!

voice-port 0/2/3

trunk-group backup_fxo 4

connection plar opx 3232

!

voice-port 0/3/0

trunk-group backup_fxo 5

connection plar opx 3232

!

voice-port 0/3/1

trunk-group backup_fxo 6

connection plar opx 3232

!

voice-port 0/3/2

trunk-group backup_fxo 7

connection plar opx 3232

!

voice-port 0/3/3

trunk-group backup_fxo 8

connection plar opx 3232

!

!

dial-peer voice 1050 pots

trunkgroup pri_1 1

trunkgroup pri_2 2

trunkgroup pri_3 3

trunkgroup backup_fxo 4

description <== Local ==>

destination-pattern 9[2-9]......

forward-digits 7

!

dial-peer voice 1051 pots

trunkgroup pri_1 1

trunkgroup pri_2 2

trunkgroup pri_3 3

trunkgroup backup_fxo 4

description <== Long distance ==>

destination-pattern 91..........

forward-digits 11

!

dial-peer voice 1052 pots

trunkgroup pri_1 1

trunkgroup pri_2 2

trunkgroup pri_3 3

trunkgroup backup_fxo 4

description <== Special service ==>

destination-pattern 9[2-9]11

forward-digits 3

!

dial-peer voice 1053 pots

trunkgroup pri_1 1

trunkgroup pri_2 2

trunkgroup pri_3 3

trunkgroup backup_fxo 4

description <== International ==>

destination-pattern 9011T

!

dial-peer voice 1054 pots

trunkgroup pri_1 1

trunkgroup pri_2 2

trunkgroup pri_3 3

trunkgroup backup_fxo 4

description <== 911 Safeguard ==>

destination-pattern 911

!

Thanks

Paolo Bevilacqua Mon, 04/30/2007 - 07:18

Hi,

I think it would be no issue. Trunk groups lets you mix and match different type of voice ports as you like.

In fact, if you merge pri_1, 2, 3 and backup_fxo into a single one, it would have the same effect. You would then assign the preference at interface level (trunk-group XXX ), and use a single "trunkgroup" statement in the dial-peer.

As a courtesy to those providing answers, please rate all useful posts using the scrollbox below!

Actions

This Discussion