[jitsi-dev] Transition from BUSY to DISCONNECTED call state in SIP


#1

Hey,

In Jigasi there is this issue that it doesn't leave the conference
when remote SIP peer rejects the call. Peer state changes to BUSY, but
not to DISCONNECTED. Is it intended behaviour ? Should I manually
hangup the call when peer state changes to BUSY ?

Regards,
Pawel