Revision as of 14:44, 20 June 2012 by hamishwillee (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Archived:SIP RTP/AVP connections result in a "415, unsupported media type" error on the remote end (Known Issue)

From Nokia Developer Wiki
Jump to: navigation, search

Archived.pngArchived: This article is archived because it is not considered relevant for third-party developers creating commercial solutions today. If you think this article is still relevant, let us know by adding the template {{ReviewForRemovalFromArchive|user=~~~~|write your reason here}}.

Registering an application to the SIP stack for RTP/AVP connections will result in an 415/Unsupported media type error on the remote end.

Article Metadata
Platform(s): S60 3rd Edition
S60 3rd Edition (initial release)
Created: User:Technical writer 1 (20 Aug 2007)
Last edited: hamishwillee (20 Jun 2012)


It is not possible to have two ECom plug-ins registered to handle the same media type. The first one installed will always handle or reject the incoming requests. As the native SIP phone application is registered to handle RTP/AVP it is not possible to re-register for this media type.


One can use a unique Accept-Contact header (but the same RTP/AVP media type) in the SIP message. Ideally, the Accept-Contact header is a better way of resolving the client as it can always be unique. This will route the messages to the correct applications. The problem that can arise from using this workaround solution is that a non-standard SIP message is being used.

This page was last modified on 20 June 2012, at 14:44.
30 page views in the last 30 days.

Was this page helpful?

Your feedback about this content is important. Let us know what you think.


Thank you!

We appreciate your feedback.