You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In Verboice 3.3.3, with a SIP Client channel that has no call flow assigned but its direction is (mistakenly) Both directions, getting an incoming call raises an exception in the broker and doesn't log the call in the app.
We would expect a CallLog to be created with the call's failure information - but the incoming call isn't logged at all (except for the message logs in the broker's std{out/err}).
The text was updated successfully, but these errors were encountered:
In Verboice 3.3.3, with a SIP Client channel that has no call flow assigned but its direction is (mistakenly)
Both directions
, getting an incoming call raises an exception in the broker and doesn't log the call in the app.We would expect a CallLog to be created with the call's failure information - but the incoming call isn't logged at all (except for the message logs in the broker's std{out/err}).
The text was updated successfully, but these errors were encountered: