Table 23: Action URL – Events and Dynamic Attributes
All above dynamic attributes’ value is generated by the 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 follows:
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 the below table.
account
Account number associated with the call
remoteNumber
The remote party number
remoteName
The remote party name
localNumber
The local party number
localName
The local party name
sipServer
The SIP server address of the account
call-id
The SIP dialog call ID
Time
The time stamp when the call is transferred
transferName
Transferred party name
transferNumber
Transferred party number
Register_Status
registerStatus
Account register status. The value can be “registered” or
“unregistered”
Bootup_Complete
N/A
N/A
The dynamic
attributes in this row
are common
attributes that can be
applied to all events
mac
MAC address of the phone
phone_ip
IP address of the phone
program_version
Software version of the phone
hardware_version
Hardware version of the phone
product
Product name of the phone
language
Display language on the phone
P Value
Notification
Value Format
