Changing Trunk Group Name

[glenng3]

We have Communication Manager 3.1.5. I'd like to change the names of a couple of trunk groups, because the current names are confusing. We have a trunk group called Local Plus 103, for example but it's connected to a circuit labeled 104. Would anything bad happen if I renamed the trunk group Local Plus 104? Thanks.

 

[rdoranjr]

You should be fine changing the names. I've changed mine to reflect the circuit id's, so in case one goes down its an accurate trouble ticket.

 

[glenng3]

Thanks, I'll give it a try.

 

[montyzummer]

10000000000000000and 10% no issue in changing names , good house keeping practice , always try and reference things that ,make sense so the associated sig group change its name to match or reference the trunk, if viable due to routing same with the route pattern , always , always do this i try and set my systems up so if a total newbee looked at it they could work out what is associated to what by list commands via the name , I cant stress how important this type of activity is it may seem minor as it has no effect on the actual behavior of the system but when it comes to trouble shooting it can make all the difference

APSS (SME)
ACSS (SME)
ACIS (UC)

 

[wpetilli]

You may want to flag the outgoing display to 'n'. If you make the name a circuit number it can make the users think something is wrong and complain.