[Spce-user] MR14 bye not reaching subscriber

[Jeremie Chism]

Hello I have a couple MR14 ce deployments and both seem to be
exhibiting the same behavior.  Inbound or outbound call connects properly.
If the subscriber hangs up the call ends properly.  if the external caller
hangs up we receive the bye, bye goes to the internal leg but is never
transmitted to the subscriber so the call isnt hung up.  487 comes later
and sipwise tears the call down,  Has this been seen before and is there a
fix for it?

Sipwise MR14 Call Flow Issue Example

Call-ID: f5a39f61-9ff3-123f-97b1-22005af5e8c7_b2b-1

=== Call Setup ===
1. FusionPBX (131.99) -> Sipwise (11.241)
   INVITE sip:13182359651 at 76.8.29.198

2. Sipwise -> Carrier (29.198)
   INVITE forwarded

3. Carrier -> Sipwise
   100 Trying

4. Carrier -> Sipwise
   180 Ringing

5. Carrier -> Sipwise
   200 OK

6. Sipwise -> FusionPBX
   200 OK

7. FusionPBX -> Sipwise
   ACK

=== Call Active ===
- RTP established between endpoints
- Call remains active normally

=== Call Teardown (Problem Area) ===

8. Carrier -> Sipwise
   BYE (User hung up)
   CSeq: 102672 BYE

9. Carrier retransmits BYE multiple times (no response from Sipwise)
   - Same BYE repeated 4+ times

10. Sipwise -> Carrier
    SIP/2.0 408 Request Timeout
    (Sipwise never responded with 200 OK to BYE)

11. Sipwise -> FusionPBX (late)
    BYE sent AFTER timeout
    CSeq: 11 BYE

12. FusionPBX -> Sipwise
    SIP/2.0 481 Unknown Dialog

=== Result ===
- FusionPBX never receives the original BYE in time
- Call remains active on PBX side
- Sipwise sends delayed BYE which results in 481
- Call eventually clears incorrectly (NORMAL_CLEARING / 500)

=== Key Issue ===
Sipwise does NOT properly acknowledge or forward the initial BYE from the
carrier:
- No 200 OK sent to carrier BYE
- No immediate BYE sent to FusionPBX
- Causes stuck calls and dialog mismatch

=== Expected Behavior ===
Carrier BYE -> Sipwise:
- Sipwise should respond: 200 OK
- Sipwise should immediately forward BYE to FusionPBX
- FusionPBX should respond: 200 OK

=== Observed Behavior ===
Carrier BYE -> Sipwise:
- No 200 OK
- BYE retransmits
- Eventually 408 timeout
- Late BYE causes 481

-- 
Jeremie Chism
Triton Communications
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20260323/f303c52a/attachment.htm>