User Community Feedback

Submitted ideas will be evaluated by our product teams for upcoming releases and will be responded to so you know where things stand. For product support, please use the community forums or contact TAC.

NOTE: All Cisco employees & Channel Partners must enter Ideas through this Ideas Portal.

Call completed elsewhere

Webex is missing a SIP feature described in RFC3326 section 3.1


When a forked call is picked up by a device, other devices receive a CANCEL Request with The Sip header "Reason:SIP;text="Call completed elsewhere";cause=200" in the content. UC-One but also Hardphones cancels the session while ringing and don't register the call as being missed. Webex however cancel the session and registers the call as a missed call inspite of the Reason Header.


This affects The Webex app in a Huntgroup, CallCenter, Broadworks Anywhere, Shared Call Appearance, Simultanious ring and other forked call scenario's.


I suggest that Webex does process the Sip Header and when it occurs in a CANCEL request the call is not registered as a missed call.


Code Sample SIP CANCEL Request:


CANCEL sip:102@10.16.145.5 SIP/2.0

Via:SIP/2.0/UDP 10.16.145.3;branch=z9hG4bKBroadWorks.16smkct-

10.16.145.5V5060-0-146434168-1571676787-1374682403054-

From:"John Q.

Public"<sip:2145550000@initech.test;user=phone>;tag=1571676787-

1374682403054-

To:"Dom Portwood"<sip:102@initech.test>

Call-ID:BW111323054240713-1896647299@10.16.145.3

CSeq:146434168 CANCEL

Reason:SIP;text="Call completed elsewhere";cause=200

Max-Forwards:10


Thanks and kind regards,

Misja Hoen


  • Misja Hoen
  • Jan 19 2022
  • Mike Jackson commented
    November 19, 2023 21:43

    Yes, would be good if VTCs (our Yealinks do not) provided choice of how forked/SCA appearance answers are shown to others INVITEd.


    If you like, you may also like If you like, you may also like WXCUST-I-10199