Description
Different behaviour of rtpengine_manage depending on where it is called
- Response 180 is not sent to rtpengine :12221 using only reply_route
- Response 180 is sent to rtpengine :12221 using
onreply_route[MANAGE_REPLY]
Scenario 1 - reply_route only
- call rtpenginge_manage() in reply_route for responses
- works for 200 OK
- for 180 Ringing, the command does not appear on the wire to rtpengine :12221
Scenario 2 - reply_route is empty, use onreply_route[MANAGE_REPLY]
- call rtpenginge_manage() in
onreply_route[MANAGE_REPLY]
- works for 200 OK
- for 180 Ringing, the command appears on the wire to rtpengine :12221, and SDP is injected
Troubleshooting
Reproduction
- Confirmed that setup is working without
onreply_route[MANAGE_REPLY]
- Caller does not see any SDP inside 180 response; this means that rtpengine_manage decided not to end anything to rtpengine :12221
- Move call to
rtpengine_manage()
inside onreply_route[MANAGE_REPLAY]
- Now observe that SDP appears inside 180 response, indicating that rtpengine_manage decided that it should send the "offer" command to rtpengine :12221
Debugging Data
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.