Line Group ID Tips.

[holdmusic34]

Don't use line group ID 0 for your trunks under any circumstances.
Avaya recommend changing the line group ID from 0 in training.
Use line group ID 0 only for system features. E.g. voicemail collect/"?vmb"/0

My biggest, main trunk will generally be line group 10.
Incoming PSTN 20
2nd Choice BRI 30

On a server edition it becomes more important.
The numbering there may go:
SE: ID10
2nd choice ID 11
3rd Choice ID 12

Expansion 1: ID20
21
22

etc.

When you start doing it this way, don't forget to modify your ars table for outbound calling on trunk group ID 10!



Best. Commercial. Ever.

 

[IPGuru]

WTF
I have never seen any issues with leaving the linge group ID @ 0 for the main line

infact I recomend to oru engineers leave the incomming group ID at 0 for all DDI trunks & only change ift for trubnks without DDI working (analog lines)

Did Avaya give any justification for this statement? what issues does it cause? (I have only been working on this product range 16 years so may not have stumbled accross them yet).



Do things on the cheap & it will cost you dear

 

[amriddle01]

I also leave it at 0, ICR entries and shortcodes default to 0, so if you/someone forgets that shit doesn't work

 

[pkdev]

I personally never use 0 and tell all my engineers to modify it

 

[amriddle01]

Whatever works for you, makes no difference really if you know the risks/pitfalls. But the point we're making is what Avaya has said is bollocks, I have never seen an issue in the time I've done it either.
I have however seen issues when people have changed every line to unique groups so it makes maintaining the system very difficult as you are always cross referencing things etc

 

[Okkie26]

I leave on all the trunks the incomming ID to 0. Only outgoing ID is changed when this is needed (multi company, GSM gateway)

Never had any issues with it..

 

[Pepp77]

As above if just a single ISDN then 0 for incoming and outgoing IDs. If they have multiple PRIs, then they become 1, 2 etc. SIP I always start with 200 for incoming/outgoing IDs.

| ACSS SME |

 

[biv343]

I try to make the line group IDs match the line number if they are ISDN/PRI trunks. For analog, I leave them at zero. SIP I typically start at 200, and H323/SCN trunks I try to match the third octet of the IP address of the remote system if at all possible. Just a matter of preference.

 

[intrigrant]

I also leave the linegroup at 0, never had any problem with that and in the past Avaya never ever mentioned not to do so in any course.
And I can know as I've been a Avaya trainer for a few years.
Even in SCN systems each site have their default line group set to zero.

 

[holdmusic34]

Avaya AIPS SIP trunk module. Classroom based activity.

Also Intrigrant, with respect, I saw a post of yours yesterday where you wrote in 2014 that line group ID should only be used for system features.
I've looked for 40 minutes but can't find it. I have work to do.
That jogged my memory of this request from Avaya and I put the two together to make a tip.

Trunk IDs should always be unique across the network.

Best. Commercial. Ever.

 

[holdmusic34]

intrigrant (Programmer) 21 Jan 14 15:15

Line group should always kept on 0 for system features.
The name should be in brackets : "Snow"
And Snow must be a module in VM Pro with a call flow programmed otherwise you end up with the VM asking for mailbox and password.

[URL unfurl="true"]http://www.tek-tips.com/viewthread.cfm?qid=1725197[/url]

Best. Commercial. Ever.