HP VCX Software manual Accept RTP/AVP With sdescriptions, Transmit RTP/AVP With sdescriptions

Chapter 10. SIP Services

Accept RTP/AVP With sdescriptions

When sdescriptions are used, they should be presented as "RTP/SAVP" in the SDP offer sent by the client. Some clients choose to code them as "RTP/AVP" instead, to make clients, unaware of sdescriptions, to accept the SDP as an offer. Select here if the Telecommuting Module should accept incoming offers where sdescriptions are presented as "RTP/AVP" offers.

Transmit RTP/AVP With sdescriptions

When sdescriptions are used, they should be presented as "RTP/SAVP" in the SDP offer sent by the client. Some clients can’t understand the "RTP/SAVP" notation. In these cases, you might want to offer them as "RTP/AVP" instead. This violates the standard, but makes the offer compatible with clients unaware of sdescriptions. Select here if the Telecommuting Module should present outgoing offers where sdescriptions are presented as "RTP/AVP" or as "RTP/SAVP".

Force Record-Route for Outbound Requests

Here, you select if the Telecommuting Module should add a Record-Route header to all requests received by the Telecommuting Module, but whose Request-URI does not contain one of its Local SIP Domains.

The Record-Route header makes all subsequent SIP signaling for this session to be routed via the Telecommuting Module even if it is not the shortest route.

Here, you select to add Record-Route headers for outbound requests or not.

Force Record-Route for All Requests

Here, you select if the Telecommuting Module should add a Record-Route header to all requests received by the Telecommuting Module, which should be passed on to another

169