How to Upload Contacts Into Grandstream Gxp2160
Although SIP protocol (RFC3261) was non providing the semantics to back up the Busy Lamp Field (BLF) in that location's a way around to make the Busy Lamp Field function works on our telephone past using the proper instantiation and the appropriate extension of the SIP Specific Event Notification framework (RFC3265). RFC4235 – Dialog Outcome Package is the instantiation RFC3265 which defined the machinery of how the endpoint can subscribe for the status of any dialog including some other endpoint. The Busy Lamp Field feature is useful only can create a lot of overhead when trying to subscribe for the status of a large number of the resources. Event Listing BLF or BLF resource listing is the solution to solve the overhead trouble past reducing the number of requests. Instead of generating an individual SUBSCRIBE request for each resource status, the concept of the Event List is combining all of those requests into a single request that queries the status of the resources from the Event Listing. RFC4662 – Resources Listing defines an aggregating mechanism that allows for subscribing and notifying for a list of resource. This mechanism is useful when the device needs to subscribe to a large number of resources. The overhead of generating individual SUBSCRIBE requests and the overhead of processing private NOTIFY requests can be reduced by aggregating resources using a resource list concept.
This certificate serves as an stop-user guide on how to configure Grandstream GXP21xx/17xx/16xx Enterprise IP phones for the UCM Eventlist BLF feature. And How to configure the BLF list on Grandstream UCM and apply them on the GXP phones.
OVERVIEW
Grandstream GXP21xx/17xx/16xx Enterprise IP Phones support both Grandstream UCM Decorated Lamp Field and EventList BLF features and allow terminate-users, such as attendants, to monitor the call status of users in the list. GXP21xx/17xx/16xx supports this feature by sending out the subscription request to the UCM and changing the indicator status of the Line keys, MPKs, or virtual MPKs associated with the monitored users. Additionally, the telephone is also able to pick up the calls to the monitored extensions by using a pre-divers characteristic code called BLF- Phone call-pickup Prefix.
Available Programmable Keys on each Model
| Model/Cardinal | Line Keys | Onboard MPKs | Extension Board MPKs | VPKs |
|---|---|---|---|---|
| GXP2130 | X | X | X | |
| GXP2140 | X | X | X | |
| GXP2160 | Ten | Ten | X | |
| GXP2170 | 10 | 10 | X | |
| GXP1760 | X | Ten | ||
| GXP1780 | X | X | ||
| GXP1782 | X | X | ||
| GXP1610 | X | 10 | ||
| GXP1615 | X | X | ||
| GXP1620 | X | X | ||
| GXP1625 | X | X | ||
| GXP1628 | X | Ten | 10 | |
| GXP1630 | 10 | X | Ten |
HOW EVENTLIST BLF WORKS
Subscribe
Co-ordinate to the RFC4662 – Resource List, UCM must let no more than 20 endpoints to subscribe to the unmarried resource listing. However, in do, only a single endpoint will subscribe to a particular EventList.
In the first stride, the endpoint will send a SUBSCRIBE request to the configured EventList URI as per RFC3265. The main goal of this subscription is to obtain the state data of all endpoints that are associated with the Event List.
In society to subscribe for the Consequence List, it is necessary that the phone includes the "eventlist" tag in the supported header, and in most cases, the Authorization header is too required.
Via: SIP/2.0/UDP 192.168.forty.119:5060;co-operative=z9hG4bK341324999;rportFrom: <sip:5000@192.168.40.170>;tag=1620181217
To: <sip:170BLF@192.168.40.170>
Call-ID: 1469406960-5060-ii@BJC.BGI.EA.BBJ
CSeq: 20001 SUBSCRIBE
Contact: <sip:5000@192.168.twoscore.119:5060>
Dominance: Digest username="5000", realm="Grandstream", nonce="509e9f25", uri="sip:170BLF@192.168.40.170", response="47c40eb60804fff79e3478e327145432", algorithm=MD5
X-Grandstream-PBX: true
Max-Forwards: 70
User-Agent: Grandstream GXP2170 1.0.11.35
Expires: 3600
Supported: replaces, path, timer, eventlist
Upshot: dialog
Accept: application/dialog-info+xml,multipart/related,application/rlmi+xml
Allow: INVITE, ACK, OPTIONS, CANCEL, Adieu, SUBSCRIBE, NOTIFY, INFO, REFER, UPDATE, MESSAGE
Content-Length: 0
Notify
Upon the successful subscription, the UCM will reply to the Event List initial condition information in class of the NOTIFY bulletin that contains the state and other data of each endpoint on the Consequence List in the XML format. In normal cases, each NOTIFY will contains the data of iii endpoints. Therefore, it is normal to have a set of NOTIFYs from the UCM even if the user only subscribes for a single Event List.
Content-Transfer-Encoding: binaryContent-ID: <5000@192.168.40.170>
Content-Type: awarding/dialog-info+xml;charset="UTF-viii"
<?xml version="1.0" encoding="UTF-8"?>
<dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="2" land="full" entity="sip:5000@192.168.forty.170">
<dialog id="5000">
<state>terminated</state>
<local>
<identity display="John Smith">sip:5000@192.168.40.170</identity>
</local>
</dialog>
</dialog-info>
Content-Transfer-Encoding: binary
Content-ID: <5001@192.168.40.170>
Content-Type: application/dialog-info+xml;charset="UTF-8"
<?xml version="i.0" encoding="UTF-eight"?>
<dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="2" state="full" entity="sip:5001@192.168.40.170">
<dialog id="5001">
<state>offline</state>
<local>
<identity display="David Jackson">sip:5001@192.168.xl.170</identity>
</local>
</dialog>
</dialog-info>
Content-Transfer-Encoding: binary
Content-ID: <5002@192.168.forty.170>
Content-Type: application/dialog-info+xml;charset="UTF-8"
<?xml version="ane.0" encoding="UTF-8"?>
<dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="3" state="full" entity="sip:5002@192.168.forty.170">
<dialog id="5002">
<state>terminated</state>
<local>
<identity display="William Thompson">sip:5002@192.168.40.170</identity>
</local>
</dialog>
</dialog-info>
Endpoint States
- Terminated
When there is no active call for a specific endpoint or when a call to or from a subscribed endpoint is just beingness released, and so the endpoint is considered idle/terminated.
- If applicative, the LED for the associated endpoint should be solid light-green or background should be solid greenish for the related VMPKs.
- Early
When an incoming call arrives for a subscribed endpoint, the endpoint is considered ringing/in the early country.
- If applicable, the LED for the associated endpoint should be blinking ruby or background should exist solid red for the related VMPK.
- Confirmed
When a phone call is originated from a subscribed endpoint or a subscribed endpoint answered the call, then the resource is said to be in the "active" country.
- If applicable, the LED for the associated endpoint should exist solid cherry-red or background should be solid carmine for the related VMPK.
- Offline
The subscription for that endpoint is failed or unreachable.
- If applicable, the LED for the associated endpoint should be off or groundwork should exist solid grey for the related VPK.
CREATING A BLF EVENT Listing ON GRANDSTREAM UCM
Grandstream UCM supports and allows creating an Upshot List for Busy Lamp Field (BLF) monitoring purposes. To create a list, login into the UCM and follow the beneath steps:
- Get to Telephone call Features 🡪 Upshot List.
- Click "Add Event List" to start creating a new list.
Enter the unique URI of the Event List in the URI field followed by choosing either "dialog" or "presence" Issue List (subscribers must bear the same value in the Effect header).
- Select the accounts (endpoint) to be monitored from the both available local and remote extensions. then click on the correct arrow head to motility them to the "selected" column.
- You tin add together extensions which are non in the list under the "Special Extensions" field.
- Click "Save" to consummate the Event Listing BLF cosmos.
If the new Event List is successfully created, it should be showing on the Result List table:
- Utilise Changes
Notes:
PROVISION THE EVENT Listing BLF ON THE PHONE
Configuring the GXP21xx/GXP17xx/GXP16xx Enterprise IP Phones to work with Grandstream UCM Event List BLF feature is straightforward.
- First configure your SIP account settings.
- Cull the provisioning method under Settings 🡪 Call Features: "Auto Provision List Starting Indicate".
- Select "Extension Boards" or "VPK" to be used first when the phone is existence automatically provisioned with Issue Listing BLF. The default setting is "Extension Boards".
Annotation:
- GXP2130/GXP2160: Need to set "Automobile Provision List Starting Indicate" to "MPK" (Default setting is VPK) to make the provision work.
- Fill in the BLF URI under Account Ten 🡪 SIP Settings 🡪 Advanced Features.
- Enter the URI (name) of the Result List BLF that you just created on the Grandstream UCM.
- Enable Auto Provision Event List BLFs (Recommended) to automatically assign the BLF extensions into the available MPKs/VMPKs slots.
- In the case that Auto Provision Event List BLF was disabled:
- Users can manually configure the MPKs on the extension Boards (GXP2140/2170) to monitor the BLF extension. Nether Settings 🡪 Extension Boards 🡪 EXTx: For each MPK, user needs to select "Upshot List BLF" equally Mode, cull the specified Business relationship, and enter the Value of each extension in the list. After saving and rebooting, the UCM extensions will exist logged on the extension board, and the telephone will offset to monitor the extensions condition.
- If the phone doesn't back up the extension board. Event List BLF still can be configured on Line Keys: Become to Settings 🡪 Programmable Keys 🡪 Programmable Keys, then configure each line accordingly.
The Event List BLF tin can also exist configured on MPKs and VPKs:
- To configure the Event List BLF on MPKs: Become to Settings 🡪 Programmable Keys 🡪 Multi-Purpose Keys.
- To configure the Outcome Listing BLF on VPKs:
Go to Settings 🡪 Programmable Keys 🡪 Virtual Multi-Purpose Keys: Click "Add VPK" to Select the "Mode", the "Account" and enter the "Value". So "Relieve".
VISUAL INDICATORS
Grandstream GXP21xx/17xx/16xx Enterprise IP Phones are able to notify the end-user of the phone call condition of the monitored extension by turning on the LEDs or changing the groundwork colors.
For instance, if the monitored extension is ringing, the BLF indicator condition will exist changed from solid greenish to blinking red; and if the monitored extension answers the call, the BLF indicator status will be changed from blinking blood-red to solid red.
The following table shows the BLF indicator status in unlike scenarios:
| Monitored Extension Beliefs | VMPK (BLF Background Condition for GXP21xx) | LINE Keys/MPKs (LED Indicator Status) | Extension Board Central Status (Only for MPK Extension Supported Models) |
| Idle | Solid green | Solid dark-green | Solid greenish |
| Placing a call | Solid red | Blinking green | Blinking green |
| Ringing | Solid reddish | Blinking ruby-red | Blinking red |
| During a call | Solid cerise | Solid ruby-red | Solid red |
| Agree the call | Solid ruby-red | Solid red | Solid scarlet |
| Call Park | Solid red | Blinking red | Blinking red |
| Monitored extension non registered/BLF subscription failed | Solid grey | Off | Off |
DIRECTED CALL PICKUP
The directed call pickup feature allows the GXP/21xx/17xx/16xx telephone system to respond the calls to the monitored users. This feature is very useful for the attendant to be able to answer calls if the callees are non available.
For the Grandstream UCM organisation, it requires to dial the specified prefix ahead of the monitored extension to straight pick up the call. Thus, the end-user must configure the BLF Call-pickup Prefix for GXP21xx/17xx/16xx in order to use this characteristic.
The following screenshot shows that (**) is configured as the prefix under the Account Ten 🡪 SIP Settings 🡪 Advanced Features 🡪 BLF Telephone call-pickup Prefix.
Then, when the monitored user'southward indicator shows an incoming phone call betoken, the GXP21xx/17xx/16xx phones user can press the BLF button to answer/option up the call.
Source: https://documentation.grandstream.com/knowledge-base/how-to-configure-eventlist-blf/
0 Response to "How to Upload Contacts Into Grandstream Gxp2160"
Post a Comment