Recording: Recordings from CUBE fail with SIP error 488 Not Acceptable Here

From DocWiki

(Difference between revisions)
Jump to: navigation, search
Jwolfeld (Talk | contribs)
(Created page with "== Recordings from CUBE fail with SIP error 488 Not Acceptable Here == {| border="1" |- ! '''Problem Summary''' | Calls forked from CUBE cannot be recorded. |- ! '''Error Mess...")
Newer edit →

Revision as of 20:00, 25 September 2012

Recordings from CUBE fail with SIP error 488 Not Acceptable Here

Problem Summary Calls forked from CUBE cannot be recorded.
Error Message SIP traces show Cisco MediaSense receiving the Invite from CUBE, and then rejecting it with SIP/2.0 488 Not Acceptable Here.
Possible Cause CUBE by default sends multipart Content-Type header to the MediaSense, but MediaSense does not support it. Notice the SIP Invite contains "Content-Type: multipart/mixed;boundary=uniqueBoundary".
Recommended Action You can prevent CUBE from sending multipart Content-Type to MediaSense by specifying
signaling forward none

In the dial-peer to MediaSense.

Release All
Associated CDETS # None


Rating: 0.0/5 (0 votes cast)

Personal tools