DTMF signal received
Description
One of the parties sent a DTMF signal (SIP-INFO or RFC2833).
Class |
|
Type |
|
Properties
| Specification | Description |
|---|---|
Name: |
Unique event identifier. |
Name: |
Event timestamp. |
Name: |
CallId of party A (from the received INVITE SIP packet). The same for all events within one switching. |
Name: |
Numeric hash of party A CallId. The same for all events within one switching. |
Name: |
Unique call identifier (starts with the arrival of the INVITE SIP packet). The same for all events within one switching. |
Name: |
Call timestamp (arrival of the INVITE SIP packet for processing). The same for all events within one switching. |
Name: |
Call date-time (arrival of the INVITE SIP packet for processing). The same for all events within one switching. |
Name: |
Unique call identifier (in product layer format 'cid.invitets'). The same for all events within one switching. |
Name: |
Switching dialog identifier. |
Name: |
Hash of the switching dialog identifier. |
Name: |
Party B URI. |
Name: |
service field. |
Name: |
Party A URI. |
Name: |
Party B callid. |
Name: |
Party A URI. |
Name: |
service field. |
Name: |
Party B URI. |
Name: |
callid of the party that set hold. |
Name: |
Party B URI for the device that set hold. |
Name: |
service field. |
Name: |
Party A URI for the device that set hold. |
Name: |
Subscriber id in 'number@domain' format, from which the command was received. |