### Description Different behaviour of rtpengine_manage depending on where it is called 1. Response 180 **is not** sent to rtpengine :12221 using only reply_route 1. 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 1. Confirmed that setup is working without `onreply_route[MANAGE_REPLY]` 2. Caller does not see any SDP inside 180 response; this means that rtpengine_manage decided not to end anything to rtpengine :12221 3. Move call to `rtpengine_manage()` inside `onreply_route[MANAGE_REPLAY]` 4. 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