Server to server SIP trunks are very useful and easy to configure.
DNIS is used to send and receive calls between servers
Usage Cases Implementing DNIS:
ISDN Gateways are very practical for adding ISDN interfaces to the ScopTEL server when SIP trunks are not used but additional features can be added to Legacy PBX’s using ISDN Gateways and leveraging ScopTEL to:
Hot Desk extensions are essentially guest extension numbers which are able to login to physical Phone Extensions (SIP).
-Logged Hot Desk extensions can make and receive calls while sending their Hot Desk CallerID.
-Admin assigned Class of Service objects can restrict the usage of Hot Desk users and Phones from Long Distance Dial Plans, Feature Codes, and Applications.
-A single SIP Phone or SoftPhone can be a ‘landing spot’ or ‘hotelling station’ for any Hot Desk user
First you need to create at least one Class of Service object with custom privileges selected in Services, Applications, Local Extensions, and Outgoing Lines. This Class of Service will be ‘nested’ in the Phone’s Class of Service after you assign the ‘hotdesk’ Class of Service object. Advanced ‘Nesting’ is achieved by creating multiple Class of Service ‘nested’ objects and checking ‘Include other permission(s)‘ check-boxes in the ‘primary’ Class of Service object and assigning the primary Class of Service to the Hot Desk User extension. This type of ‘nesting’ can be used to set privileges defining behavior based on various schedules since a schedule can be applied to any Class of Service object.
After you have customized your desired Class of Services objects you must create a ‘hotdesk’ Class of Service object in the GUI in Telephony>Manager>Class of Service.
This Class of Service object will later be applied to the physical SIP Phone or SoftPhone.
Then you must select the Services tab and only give this Class of Service access to the feature code for Hot Desk
Then on the Miscellaneous tab you must enable ‘Enable Hotdesk Restriction ?’ and assign an existing Class of Services drop list selection for the Phone’s ‘Class of Service if not Logged:’ assignment.
NOTE: When the Hot Desk User is logged to the device, the Hot Desk extension’s Class of Service is active and when the Hot Desk User is not logged to the device the ‘Class of Service if not Logged‘ configuration is active. Therefore you must create these Class of Service objects before building the ‘hotdesk’ Class of Service.
The next step is to assign the ‘hotdesk’ Class of Service to a Phone extension.
Now create a Hot Desk extension in Extensions>Type>Hot Desk
-Whatever Class of Service you assign to the Hot Desk extension will take precedence over the phone’s assigned Class of Service when the Hot Desk user is logged to the extension. This allows great security and flexibility when logging in and out with a Hot Desk extension to a phone.
-Enable Voicemail on the Voicemail tab if needed
-Edit the Caller ID to send custom Caller ID if needed.
-Edit other tabs if needed
Commit when all configurations are saved.
From the SIP Phone or SoftPhone with Class of Service = hotdesk
-Dial the Hot Desk feature code (default *22)
-Enter the Hot Desk extension number as in example 222
-Enter the password as in example 1234
The Hot Desk extension 222 is now logged to the SIP extension and can make and receive calls. These calls will be restricted/allowed by the extensions>Hot Desk>Class of Service configuration
Automatic schedules are great when you want to set up Incoming Lines to predetermined destinations during closed hours, weekends, and Holidays.
But what if you want to override your schedules and set up predetermined destinations for unforeseen emergencies or early closures, or just can’t be bothered to set up automatic scheduling? ScopServ refers to this feature as Ringing Services. Also known as Night Service…
Not only does this document explain how to set up Incoming Lines on your ScopTEL PBX but it clearly explains how to set up manual schedules that can be toggled on and off with a feature code or programmed to a DSS Key WITH BLF STATUS so you know when the Service Mode is ACTIVE.Module 7 - ScopTEL - Incoming Lines Management
We will see in this article how to configure a Scopserv system so it can communicate with Montreal based SIP trunk provider, B2B2C.
Two steps are required in order to use an external link, and two other steps are optional:
Creation of a VoIP Account
Creation of an incoming line (optional)
Creation of an outgoing line (optional)
Update of the appropriate Class of Service (CoS)
In the Telephony -> Interface menu , in the VoIP Account TAB, click on ‘Add New VoIP Account ‘
General Tab: Create a SIP trunk type Ami. name the instance B2B2C.
Server Tab: Specify the server address in the box B2B2C Host / IP, the host mode is set to specific. If you have a username and password, specify it. Register as a user agent is optional.
Network Tab: Check boxes: Trunk behind a Nat, Unsecure Port and Invites (required for incoming calls), and Qualifier
Options Tab: Automatic Mode DTMF (RFC2833/Inband)
In the menu Telephony –> Lines, incoming line Tab, click ‘Add a new line’
General tab: Type Post (DNIS), Indicate in the box Post the phone number assigned to you.
Destination tab: Select the desired destination, such a position.
Options tab: Select the trunk created in the previous step, in this case B2B2C.
In the menu Telephony –> Lines, outgoing line Tab, click ‘Add a new line ‘
General tab: Name your line, for example B2B2C B2B2C and enter the trunk.
Dial String tab: Simply put in first, choose a custom dial string and enter ‘X’. This configuration is not adequate but to validate the operation.
Caller ID tab: Click Force the outgoing caller ID, and specify your main phone number and the name of the company. This is mandatory.
In the menu Telephony –> Manager, Class of Service Tab, choose the Class of Service where you have defined your internal extensions.
Outgoing Lines tab: Either you check the ‘Allow all outgoing lines’ or you include the B2B2C line in the list authorized lines.
NOTE: You need to register every 3600 seconds with this supplier. This parameter can be changed in the menu Configuration –> Channels –> SIP Channel Tab, under the SIP Option section.
|Max length of incoming registration||:||3600|
|Default length of incoming/outgoing registration||:||120|
There you go… The only thing left is to validate the configuration and make tests.
Thank you and have a great day !!!
A Class of Service (CoS) is where you configure permissions for extensions, incoming lines, applications, features codes, outgoing lines, etc. It very important to properly configure each Class of Service, because this is where all validation for routing is done (examples: if an incoming line, extension, or if an outgoing line route exists)
To add, modify or delete a Class of Service, login to the ScopServ GUI, and click on Telephony -> Manager- > Class of Services
In each Class of Service, you have different sections where you can set different permissions.
On the Services tab, you can specify which feature code(s) (Voicemail, Agent Login, Call Forward, DND, etc.) are available. It is not recommended to use the ‘All Features’ option when the Class of Service is used by an “untrusted” source. So if the users that will use this Class of Service do not need full access then do not check the ‘All Features’ option and instead select individual features codes that will be available.
On the Applications tab, you can specify which applications (created on Applications -> Application) are available. It is not recommended to use the ‘All Applications’ option when the Class of Service is used by an “untrusted” source. If you check ‘All Applications ‘ and have a custom application that executes a “sensitive” task (example: turn off the alarm system) then this is a major security risk, this is why you must select individual permissions.
On the Local Extensions tab, you can specify which extensions are reachable. If you want all extensions to be available for users that use this Class of Service, then simply check the ‘ All Extension ‘ option. If you want to restrict the ability to reach some local extensions then select a list of allowed local extensions.
On the Outgoing Lines tab, you specify which outgoing lines you want to be reachable. You can set the line priority (examples: 011X must be defined before X. else 011X will never be reachable). If some users need access only to local/national calls but must not be able to make international calls, or be restricted to use specific trunks, then the Outgoing Lines tab is used to select individual outgoing lines.
On the Miscellaneous tab, you can set miscellaneous options like Agent or Hotdesk restrictions. It is also possible to include others permissions (Class of Services) by selecting one or more contexts. The option ‘Include other permissions’ allows to include others permissions in order to create group like Class of Service objects. This is useful to create a Class of Service that will include a hierarchy of other Class of Service objects.
Class of Services can be used in different places like Interfaces (VoIP Account, Digital, Analog) to lookup destinations. They can also be used on Extensions to specify which permissions the extension will have (examples: can the extension reach Voicemail or disable DND). They can also be used on an Auto Attendant (IVR) menu to lookup a key pressed by a user so it is very important to ensure that everything is properly configured.
For example: if you configure an Auto Attendant (IVR) to use a Class of Service that has access to all services, then any person that reaches the IVR will be able to execute any inherited service such as *888 to spy on extensions, or dial *78 to set a CallForward, or reach DISA, or dial any included feature, and etc. So ensure that an IVR does not have access to Class of Services with excessive permissions else major security holes can exist in the configuration.
In summary it is very important to properly configure Class of Services to restrict access permissions to a user.