GRP2600 Administration Guide
Version 1.0.5.15
Account register status. The value can be
“registered” or “unregistered”
The dynamic
attributes in this row
are common
attributes that can
be applied to all
events
Software version of the phone
Hardware version of the phone
Product name of the phone
Display language on the phone
All above dynamic attributes’ value is generated by phone system and can be used as dynamic attributes
with a pair of curved braces around them. For example, if the message body is specified as following:
Your call from {remoteName}:{remoteNumber} to {localName}:{localNumber} was forwarded to {fwdNumber}
by reason {fwdReason}.
Then the message received in the outbound notification will look like this:
Your call from Daniel:2070 to Jasmine:2071 was forwarded to 777777 by reason unconditional.
Only attributes in curved braces will be replaced by the run time value. Other content will remain the same
as static text.
For each event, at most 3 notifications can be configured. In total, up to 75 notifications can be configured.
The P value for each notification is listed in below table.
Table 22: Action URL Notification P-values
String. Each P value consists of all the options configured for this
notification.
Example 1 – Notification 1 for event “Call_Missed” to destination 1, with 2
extra Attributes configured:
P9920=eventName=Call_Missed&destName=destination1&subject=&msg=
You have a missed call from {remoteName}:{remoteNumber} on Line {line},
account {account} at
{time}.&extraAttrName1=extraAttrValue1&extraAttrName2=extraValue2
Example 2 – Notification 2 for event “Incoming_Call” to destination 2, with 2
extra Attributes configured:
P9921=
eventName=Incoming_Call&destName=destination2&subject=Incoming
Call Alert&msg=You have an {callType} call from
To Next Page
Loading...
Need help?
General
