Teams user hang up the call but call at the VitalPBX still show connected.

Hi,

I have setup a trial between VitalPBX 3.1.1-2 with MS Teams using the Teams Connector Add-On module. I am able to dial from VitalPBX extension x9839 (using microsip) to Teams x3000. Call was able to establish. But when x3000 hang up the call, x9839 showed Connected (in Orange colour).

Based on the log, looks like the trunk have detected hang up but wondering why the call still in Connected state.

[2021-09-13 15:50:48] VERBOSE[30340][C-00000024] pbx.c: Executing [h@trk-10-dial:1] Gosub("PJSIP/9839-00000048", "dynamic-routing-out,s,1(9839,+3000,ANSWER,10)") in new stack
[2021-09-13 15:50:48] VERBOSE[30340][C-00000024] pbx.c: Executing [s@dynamic-routing-out:1] NoOp("PJSIP/9839-00000048", "Test if save on dynamic routing list") in new stack
[2021-09-13 15:50:48] VERBOSE[30340][C-00000024] pbx.c: Executing [s@dynamic-routing-out:2] Set("PJSIP/9839-00000048", "CALLER=9839") in new stack
[2021-09-13 15:50:48] VERBOSE[30340][C-00000024] pbx.c: Executing [s@dynamic-routing-out:3] Set("PJSIP/9839-00000048", "CALLED=+3000") in new stack
[2021-09-13 15:50:48] VERBOSE[30340][C-00000024] pbx.c: Executing [s@dynamic-routing-out:4] Set("PJSIP/9839-00000048", "STATUS=ANSWER") in new stack
[2021-09-13 15:50:48] VERBOSE[30340][C-00000024] pbx.c: Executing [s@dynamic-routing-out:5] Set("PJSIP/9839-00000048", "TRKID=10") in new stack
[2021-09-13 15:50:48] VERBOSE[30340][C-00000024] pbx.c: Executing [s@dynamic-routing-out:6] Set("PJSIP/9839-00000048", "ALLOW_DR=no") in new stack
[2021-09-13 15:50:48] VERBOSE[30340][C-00000024] pbx.c: Executing [s@dynamic-routing-out:7] Set("PJSIP/9839-00000048", "DYNROUTING_OMC=yes") in new stack
[2021-09-13 15:50:48] VERBOSE[30340][C-00000024] pbx.c: Executing [s@dynamic-routing-out:8] GotoIf("PJSIP/9839-00000048", "0?:comeback") in new stack
[2021-09-13 15:50:48] VERBOSE[30340][C-00000024] pbx_builtins.c: Goto (dynamic-routing-out,s,10)
[2021-09-13 15:50:48] VERBOSE[30340][C-00000024] pbx.c: Executing [s@dynamic-routing-out:10] Return("PJSIP/9839-00000048", "") in new stack
[2021-09-13 15:50:48] VERBOSE[30340][C-00000024] pbx.c: Executing [h@trk-10-dial:2] Gosub("PJSIP/9839-00000048", "notify-trunk-hangup,s,1") in new stack
[2021-09-13 15:50:48] VERBOSE[30340][C-00000024] pbx.c: Executing [s@notify-trunk-hangup:1] Verbose("PJSIP/9839-00000048", "0, Trunk Hangup") in new stack
[2021-09-13 15:50:48] VERBOSE[30340][C-00000024] app_verbose.c:  Trunk Hangup
[2021-09-13 15:50:48] VERBOSE[30340][C-00000024] pbx.c: Executing [s@notify-trunk-hangup:2] UserEvent("PJSIP/9839-00000048", ""EXTENSIONS_SUMMARY","Data: OUTBOUND,PJSIP/9839,3000,OUT"") in new stack
[2021-09-13 15:50:48] VERBOSE[30340][C-00000024] pbx.c: Executing [s@notify-trunk-hangup:3] Return("PJSIP/9839-00000048", "") in new stack
[2021-09-13 15:50:48] VERBOSE[30340][C-00000024] pbx.c: Executing [h@trk-10-dial:3] Hangup("PJSIP/9839-00000048", "") in new stack
[2021-09-13 15:50:48] VERBOSE[30340][C-00000024] pbx.c: Spawn extension (trk-10-dial, h, 3) exited non-zero on 'PJSIP/9839-00000048'

Please advise.

Thanks.

Best Regards,

Welcome to the community :grinning:
Thanks for sharing, the development team will reproduce the issue
Regards,

Hi ddavila,

I tried again today after rearrange the dial plan between the VitalPBX and Teams as well as some routing rules fine tuning, the mentioned problem not happening again. It could be due to some missed configuration earlier on.

I will proceed to close this post. Thanks for your time.

Regards,

Could you share the solution please? :slight_smile:

1 Like

My bad. After a series of detailed testing, the problem still exist.

If the call is initiated by VitalPBX extension or external party to a Teams user, call is able to hang up by either party.

If the call is initiated by Teams user, both call legs will released if hang up by Teams. If released by VitalPBX extension or external party, the Teams call leg remained active.

Thanks.

Regards,