signal groups

[MadAccess]

My T1 provider recommended that the new T1's I'm adding to an existing trunk group be added to their own signal group and their own D-channel. Is there anything I need to watch out for when mixing signal groups within one trunk group?

 

[wilsontec]

signal group is control t1 only ,so put all diffence t1 in same trunk group is ok.

 

[wilsontec]

but only beware of outgoing CLI. because different cli may not work normal in same trunk group.

 

[mikeydidit]

You could also use that as a secondary preference in the signaling group which basically gives you a backup .

See below.

display signaling-group 1                                       Page   1 of   5
                                SIGNALING GROUP

 Group Number: 1              Group Type: isdn-pri
                    Associated Signaling? n          Max number of NCA TSC: 0
                       Primary D-Channel: 01D2024     Max number of CA TSC: 0
                     Secondary D-Channel: 04D2024  Trunk Group for NCA TSC:

Then should you loose the primary your secondary picks up associated signaling.


"A people that values its privileges above its principles soon loses both."
- Dwight D. Eisenhower (1890-1969), Inaugural Address, January 20, 1953

For the best response to a question, read faq690-6594

 

[wmainc]

The PRI's need to be set up specifically to use nfas (non-facility associated signalling) to set up the primary and secondary d-channels. You can't just put the two channels in the signal group form and have one back up the other.

 

[Mitch672]

yes, you can. You will have to play with the "interface id", most likely they will be 0 and 1. See the example above that mikedidit posted, that is NFAS (Associated Signalling? is stroked "n")

mitch


AVAYA Certified Specialist

 

[AvayaTier3]

You are both correct. I think what "wmainc" is trying to say, is that you cannot arbitrarily program any T1 and signaling groups as NFAS unless the circuits were ordered that way from the provider. This is true.

Interface 0, 1, 2, ..... must match the provider and the primary and secondary, if used in one signaling-group, also have to match exactly what the provider is setup for.

A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

35 years Bell, AT&T, Lucent, Avaya
Tier 3 for 25 years and counting

 

[MadAccess]

Okay, how about this: After adding a few new T1's my trunk-group has reached it's limit of 255 members. I still have some more members to add. Can I go over this limit without having my T1 provider send these T1's to a new trunk-group?

 

[AvayaTier3]

You will have to put them in a new trunk-group in CM, but the provider can keep them in one group if they do not have the same limitations as CM

A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

35 years Bell, AT&T, Lucent, Avaya
Tier 3 for 25 years and counting

http://bshtele.com

 

[MadAccess]

Okay, good! Thanks for the quick reply.

 

[mikeydidit]

You can also set this up as a separate group and use it in the secondary preference in the trunks group. Of course your provider will have to set theirs up the same way. The nice thing about setting up this way is, let's say your 464 that the signaling is done on dies. The other members (unless you have a secondary d channel) also die. The switch and the CO see this and route calls in through the secondary preference (your new trunk group) giving you a backup trunk group. You can also bleed calls in an overflow condition. So this is just another option for you to think about.

This is also how ours are set up. But being this system is in a hospital, we try hard to come up with redundant solutions. Having some trunks in the event our main trunks go down sure beat having nothing.

"A people that values its privileges above its principles soon loses both."
- Dwight D. Eisenhower (1890-1969), Inaugural Address, January 20, 1953

For the best response to a question, read faq690-6594

 

[MadAccess]

Here's where I get stuck again. The signaling-group page has a field for "Trunk Group for Channel Selection" which to me implies that there can be only 1 signal-group per trunk group, but in my case SG1 is going to be spread across two TG's (because I ran out of slots in TG1). Can I spread a SG between multiple TG's?

If this helps this is what I have:

>TG1 has 255 members all in SG1.
>I'm adding TG2 which will have the remaining members from TG1/SG1 and several new circuits which will be SG2.



The information in the CM Admin manual isnt very helpful on this.

 

[mikeydidit]

change signaling-group 1                                        Page   1 of   5
                                SIGNALING GROUP

 Group Number: 1              Group Type: isdn-pri
                    Associated Signaling? n          Max number of NCA TSC: 0
                       Primary D-Channel: 01D2024     Max number of CA TSC: 0
                     Secondary D-Channel: 04D2024  Trunk Group for NCA TSC:
      [B] Trunk Group for Channel Selection: 5 [/B]
          Supplementary Service Protocol: a          Network Call Transfer? n

         Trunk Brd      Interface ID          Trunk Brd      Interface ID
          1: 02D15            2              11:
          2: 02D04            3              12:
          3: 02D05            4              13:
          4: 02D16            5              14:
          5: 04D17            7              15:
          6: 01C20            6              16:
          7: 01D20            0              17:
          8: 04D20            1              18:
          9: 03C09            8              19:
         10: 03D09            9              20:

F5 (help)
[B] Enter assigned group number between 1-2000, or blank [/B]

Looking at this it is going to have to be for only one trunk group. Mine above are set for 5 as this is trunk group 5. Not sure where or how BLANK would apply.


"A people that values its privileges above its principles soon loses both."
- Dwight D. Eisenhower (1890-1969), Inaugural Address, January 20, 1953

For the best response to a question, read faq690-6594