Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Trunk Group

Status
Not open for further replies.

tommylux

Technical User
Apr 16, 2008
67
GB
Our 3300 was set up for us, but I have had technical training how to maintain the 3300.

Im worried I might have learnt too much because Im starting to look at things perhapse too closely.

We have two 3300s, and if we focus on the first switch, there is 1 T1 card which has 1 ISDN link to BT and one incoming link from the second switch (attached to an T1/E1 Failover port)

In the First switch's Digital link assignment, there is two records; one for the ISDN, the second for the failover from the second switch.

In the Trunk Assignment, you can see 60 trunks over the two digital links.

In the Trunk Group assignment, there is only 1 group which contains Trunks for the ISDN link. The failover trunks are not defined.

Does this mean that calls will never go out on the failover line?

Tom
 
Your analysis seems a little off but the programming does seem to support some of your assumptions.

I would venture that the programming is wrong but I can't be sure without more data.

First the failover port is not incoming but is actually outgoing to the second system. You do not indicate so I must assume that it is connected to a PRI failover card on the second system (Primary port) and the link shows that it is currently out of service.

With this configuration, in the event of a failure of the first system, the PRI will failover to the second system and be available for any phones that are resilient/running off the second system.

There should be 30 channels running on sys1 and 30 channels running on sys2 and route lists pointing the ARS to overflow both directions.

I'm making a lot of assumptions above. Hopefully you can provide more detail to clear things up.


*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.
 
Does this help?


Should I program 30 more trunks, for the failover link, would the system know that its not failed over, and not attempt to send the calls across?

I was thinking of changing the hunt mode to Terminal, and put all the failover trunks at the end of the group.
 
Picture helps a lot but I have bad news. It is not configured correctly.

Your picture seems to indicate that you have two(2) 30 channel PRI's. One connected to each system. The failover port of one card is connected to the failover port of the other. This will not work!

The failover port MUST be connected to the PRIMARY port of the failover card.

The configuration you have would require a total of 4 Resilient T1/E1 PRI cards (2 in each system) with 4 digital links (2 on each system).

I have this exact scenario setup on one of my systems and it works like a charm. There are some finicky setup values but pretty simple overall

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.
 
Sorry for the confusion.. One is a T1 E1 Failover card, the other one is a standard 2 port E1 card. (not failover) So Switch 2 will failover the link into the second port on the E1 card.

Link fails over OK, and green lights are on.. Calls will come in just fine on the failed over link, But I don’t think that calls will go out on the second link as there is only 30 trunks defined in the Trunk Group.

What im kind of asking is, Can I program another 30 trunks in the group assignment (to make it 60) or is there any other setup somewhere for alternative routing bearing in mind there is only 1 trunk group.
 
Tommylux

correct me if i'm wrong but the reason the failover card is there is in case the controller dies. In which case the phones (if on the same controller) will re-home to their secondary (guessing the controller with the failover PRI). In which case the secondary controller needs to have a trunk group programmed not a second group on the primary. So what i'm saying is, you need one trunk group PER controller not 2 trunk groups in one..... make sense?

 
We're getting there.

The first system only has 1 PRI connected and should therefore have only 30 trunks in the trunk group.

The second system has 1 Active PRI and 1 Resilient PRI connected and should have 60 Channels in its huntgroup.

The first system should have a trunk list allowing overflow to a trunk group that will dial out on the second system.

The Second system should have a trunk list allowing overflow to a trunk group that will call out of the first system.

With the above setup, under normal conditions the first 30 calls will initiate on the local system and the next 30 will dial out of the remote system. (yes I know they're both physically local but logically they are remote from each other)

In Failover mode all calls will initiate from the secondary system on all 60 channels.

Clearer now?

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top