Specifications

PA-001011-03-04 Aastra July 2014

183

Example 2:

This example orders the phone to send a multicast RTP stream to 239.0.1.20 from UDP port 21000

with audio mixing.

</AastraIPPhoneExecute>

Example 3:

This example orders the phone to send a multicast RTP stream to 239.0.1.20 from UDP port 21000

with audio mixing and “mix” icon disabled.

</AastraIPPhoneExecute>

4.4.5 Interaction with action uris

action uri incoming

The action uri incoming is not triggered when the phone starts streaming RTP. This is a known

issue which will be fixed in a future firmware release.

action uri connected

The action uri connected is not triggered when the phone starts streaming RTP. This is a known

issue which will be fixed in a future firmware release.

action uri onhook

The action uri onhook is triggered at the end of the RTP streaming but the URL variables are not

bound. This is a known issue which will be fixed in a future firmware release.

action uri disconnected

The action uri disconnected is not triggered at the end of theRTP streaming. This is a known issue

which will be fixed in a future firmware release.

4.5 Keypress emulation

The Aastra SIP Phones support a “Key” URI to allow the XML application to send an event that a

key has been pressed on the phone. The system initiates the event as if the button was physically

pressed.

The phone maps key events to the phone physical keys and not to their mapped logical

keys.

The exceptions to this rule are

 Xfer,

 Icom,

 Conf

as they can be dynamically mapped on the phone.

Notes:

 If the key is a valid key, the phone executes the key regardless of the current phone

status.