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

Comments

(no comments yet)

Log in or Join to leave comments.

Archived: 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

---

Compatibility

Platform(s): S60 3rd Edition

---

Article

Created: User:Technical writer 1 (20 Aug 2007)

Last edited: hamishwillee (20 Jun 2012)

Solution

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.

Workaround

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.