Summary: | ASTERISK-23558: UPDATE causes chan_pjsip channel to be taken off hold | ||
Reporter: | John Bigelow (jbigelow) | Labels: | |
Date Opened: | 2014-03-29 00:08:28 | Date Closed: | 2014-05-01 07:49:24 |
Priority: | Major | Regression? | |
Status: | Closed/Complete | Components: | Resources/res_musiconhold Resources/res_pjsip Resources/res_pjsip_sdp_rtp |
Versions: | SVN | Frequency of Occurrence | |
Related Issues: | |||
Environment: | PJSIP trunk r4797 (after v2.2), pjsua.py library used for endpoints "alice" & "bob", Asterisk trunk r411312 | Attachments: | ( 0) full.txt |
Description: | With using PJSIP an UPDATE message sent to Asterisk from the caller who put the callee on hold causes the callee to be taken off of hold.
Break down of what happens after the call is up between "alice" and "bob: # Alice sends an UPDATE message (a=sendrecv) # Asterisk replies with a 200 OK (a=sendrecv) # Alice then sends an INVITE (a=sendonly) # Bob is put on hold and MOH is started on bob # Asterisk replies with a 200 OK (a=recvonly) # Alice sends another UPDATE message (a=sendonly) # Bob is taken off of hold and MOH is stopped on bob # Asterisk replies with a 200 OK (a=recvonly) See Alice's Call-ID 'f7e233b6-86c4-4d32-8906-84e632b02c96' in the attached full log for more details. | ||
Comments: |