You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Trunk Groups for EV Lite – this is complex as differs between analog and IP devices and would need to have detail of which device (EVG or handset) each ext is to be assigned to – however once this is known and documented may be able to made more efficient in OS.
We may be best to break this down into 2 separate scripts as Trunk Groups for analog devices is different to Trunk Groups for IP devices using EV Lite.
There could then be a further evolution for SIP Trunks in general (might need some input from Omar to make sure I don’t miss anything when we do General SIP Trunks however there’s not much difference from the Trunk Groups for Analog devices scenario below)
Trunk Groups for Analog devices using EV Lite
• The attached ‘EV Lite – prebuild notes’ doc has steps on the process, however note the devices are no longer Vega and are either EVG-24S-Lite or EVG-96S-Lite so we will need an option to choose device model
• I’ve also attached a few uploads I’ve done recently for a prebuild (HPNGR) which might help
• The Pilot user ext numbers can be anything unique in the Group – typically we often use 7001 upwards, however in this instance we used 701 upwards
• Some screenshots of a completed Trunk Group for analog device
(See email from Adam for screenshots and attached files)
Trunk Groups for IP device using EV Lite
Attached are Magic uploads for YYZMR which is an example of Trunk Groups for IP device using EV Lite
This is slightly different as there is no ‘Enable Authentication’ or ‘Pilot User’ required
Differences to Trunk Groups for analog devices are:
Enable Authentication = no
No Pilot User required
Type = Vtech_SIP_Bedroom_TG
Device Name = (GROUPID)GWL( is the location letter A,B,C etc)
Trunk Name = (GROUPID)GWL( is the location letter A,B,C etc).
Call Capacity = 1 active call per user (this could be a variable to be added for each Group or can be set manually once Trunk Group is created with a minimum of 1)
Access Device = Device created in step 2 = (GROUPID)GWL( is the location letter A,B,C etc)
Allow Unscreened Calls = Enabled
Allow Unscreened Emergency Calls =Enabled
Cl Asserted ID Policy = Unscreened originating Calls
The text was updated successfully, but these errors were encountered:
Trunk Groups for EV Lite – this is complex as differs between analog and IP devices and would need to have detail of which device (EVG or handset) each ext is to be assigned to – however once this is known and documented may be able to made more efficient in OS.
We may be best to break this down into 2 separate scripts as Trunk Groups for analog devices is different to Trunk Groups for IP devices using EV Lite.
There could then be a further evolution for SIP Trunks in general (might need some input from Omar to make sure I don’t miss anything when we do General SIP Trunks however there’s not much difference from the Trunk Groups for Analog devices scenario below)
Trunk Groups for Analog devices using EV Lite
Trunk Groups for IP device using EV Lite
Trunk Groups for Analog devices using EV Lite
• The attached ‘EV Lite – prebuild notes’ doc has steps on the process, however note the devices are no longer Vega and are either EVG-24S-Lite or EVG-96S-Lite so we will need an option to choose device model
• I’ve also attached a few uploads I’ve done recently for a prebuild (HPNGR) which might help
• The Pilot user ext numbers can be anything unique in the Group – typically we often use 7001 upwards, however in this instance we used 701 upwards
• Some screenshots of a completed Trunk Group for analog device
(See email from Adam for screenshots and attached files)
Trunk Groups for IP device using EV Lite
Attached are Magic uploads for YYZMR which is an example of Trunk Groups for IP device using EV Lite
This is slightly different as there is no ‘Enable Authentication’ or ‘Pilot User’ required
Differences to Trunk Groups for analog devices are:
Enable Authentication = no
No Pilot User required
Type = Vtech_SIP_Bedroom_TG
Device Name = (GROUPID)GWL( is the location letter A,B,C etc)
Trunk Name = (GROUPID)GWL( is the location letter A,B,C etc).
Call Capacity = 1 active call per user (this could be a variable to be added for each Group or can be set manually once Trunk Group is created with a minimum of 1)
Access Device = Device created in step 2 = (GROUPID)GWL( is the location letter A,B,C etc)
Allow Unscreened Calls = Enabled
Allow Unscreened Emergency Calls =Enabled
Cl Asserted ID Policy = Unscreened originating Calls
The text was updated successfully, but these errors were encountered: