Bug 139 - handling ACK with sip.rendering="no" and missing SDP
Summary: handling ACK with sip.rendering="no" and missing SDP
Status: NEW
Alias: None
Product: resiprocate
Classification: Unclassified
Component: recon (librecon) (show other bugs)
Version: unspecified
Hardware: All All
: P1 normal
Assignee: Owner of all unassigned bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-11-09 07:53 CST by Daniel Pocock
Modified: 2018-11-09 07:53 CST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Daniel Pocock 2018-11-09 07:53:42 CST
A user on a Polycom UA presses the Hold button.

The Polycom is configured with an MOH URI (RFC 7088).  It sends a re-INVITE to reCon without SDP and with sip.rendering="no" 

https://tools.ietf.org/html/rfc7088#page-5

reCon responds correctly, sending 200 OK with an SDP offer.

Polycom is unable to contact the MOH server and simply sends an ACK to reCon with sip.rendering="no" and no SDP answer.

In this case, reCon should treat it as a remote hold without music and notify the application's ConversationManager.

ACK sip:7003@.....
...
Contact: <sip:phone4@.....:55612;transport=tls>;+sip.rendering="no"
...
Content-Length: 0



InviteSession.cxx:1815 | Got Ack with no answer
InviteSession.cxx:2782 | Transition InviteSession::ReceivedReinviteSentOffer -> InviteSession::Connected
RemoteParticipant.cxx:2301 | onOfferRejected: handle=300, SipReq:  ACK 7003@10.0.0.10:5062 tid=cbf8a95