3.9.5.1.4 Routing Element Lists
The server MUST use only the lists specified in the following table. These lists can be empty if there is no relevant data provided by the user. All other list elements published by client endpoints are ignored.
|
List name |
Usage |
|---|---|
|
forwardto |
This list contains the URI that SHOULD be used when the user has selected call forwarding, which means that the enablecf is set under clientflags. Even though the list element syntax allows more than one item, the list SHOULD contain only one entry. If more than one entry is present, the server SHOULD only use the first destination. |
|
simultaneous_ring |
This list contains the URI that defines a device that SHOULD ring at the same time as the user's registered devices. Even though the list element syntax allows more than one item, the list SHOULD contain only one entry. If more than one entry is present, the server SHOULD only use the first destination. |
|
team<44> |
This list contains the URIs corresponding to the team members of the user. This list is applicable only if the routing version is 2. |
|
delegates<45> |
This list contains the URIs corresponding to the delegates of the user. This list is applicable only if the routing version is 2. |
|
first_delegate<46> |
Reserved for future use. SHOULD be ignored. |
|
breakthrough<47> |
List of identities that can ring the user directly even when the skip_primary flag is set. This is applicable only if routing version is 2. |
|
add_voice<48> |
Reserved for future use. SHOULD be ignored. |