locked
is inviting you to a video call video call was not accepted btoe polycom vvx500 RRS feed

  • Question

  • I am not sure if this is a Lync Client or Polycom UC issues. I have posted on the Polycom community however no one ever answers so I am trying my luck here. (http://community.polycom.com/t5/VoIP/VVX-BTOE-Video-Call-to-Lync-Client-603-Decline/m-p/70307#M12058)

    I have Lync 2013 Client and VVX500 paired with BTOE. If I make an inbound video call, a toast pop up shows incoming call then changes to inviting to a video call, as soon as the video invitation toast appears, the call is immediately decline 603 and sent to voicemail.

    If I disabled BTOE, the call comes in fine, both the Lync client and the VVX will ring, the toast pop up says inviting to a video call and I can use the Lync client to answer the video call.

    I have found that it can get it to work with BTOE running if there is an existing IM window opened first, when I then select video call, its get added, not invited. In short, when BTOE is on, adding video to an existing conversation is ok, inviting to a new video conversation fails.

    Lync Client Trace

    02/17/2015|10:12:17.872 1028:1600 INFO  ::
    SIP/2.0 603 Decline
    Via: SIP/2.0/TLS 10.1.2.3:5061;branch=z9hG4bK09EB59D3.878067B2BD5BA​2F3;branched=FALSE;ms-internal-info="clTPvXadK7Igm​wymnUOPmAwURJgRK-31dcZyFOKfwj-luyZ4CHtVuuMAAA"
    Via: SIP/2.0/TLS 10.1.0.2:63193;branch=z9hG4bKF4F578A1.7CD7D5FBC595​12EC;branched=TRUE;ms-received-port=63193;ms-recei​ved-cid=1529000
    Via: SIP/2.0/TLS 10.1.0.3:62226;branch=z9hG4bK02B03964.8FB8BAF0BD59​A2F3;branched=FALSE;ms-received-port=62226;ms-rece​ived-cid=116A500
    Via: SIP/2.0/TLS 192.168.50.35:55338;branch=z9hG4bK692468C1.645DAB6​3422602EA;branched=FALSE;ms-internal-info="cqkBAMf​yk84SSTy0QFCKF3uTBlR3EPlBBjEs03HXe3MjJjq11kd6564QA​A";received=server.domain.com.au;ms-received-port=​55338;ms-received-cid=15ACE00
    Via: SIP/2.0/TLS 192.168.20.93:49665;branch=z9hG4bK5CD0F064.79815F1​838A0E2EC;branched=FALSE;ms-received-port=49665;ms​-received-cid=5C3100
    Via: SIP/2.0/TLS 192.168.20.91:56827;branch=z9hG4bK4d37782f;ms-rece​ived-port=56827;ms-received-cid=10D5E00
    From: <sip:user1@domain.com.au>;epid=212336682833;tag=c3​cc787854
    To: <sip:user2@domain.com.au;epid=02b20eda9a;tag=004da​b121b
    Call-ID: fdda2d3b-f866-4fc0-911d-52325c367468
    CSeq: 2761 INVITE
    Record-Route: <sip:server.domain.com.au:5061;transport=tls;opaqu​e=state:Ci.R15b4d00;lr;ms-route-sig=hq2GqYQH_bwrx8​1dIPmdpVxGJ1-6Efhii6WH0Y2xZ30LuyZ4CHd1QD1QAA>;ms-r​rsig=hq4nGI47yeltpJOyJdVQer6IRdzSfd_tMWMZ0DcO6s3gi​yZ4CHd1QD1QAA;tag=D98DD6387856815820B8A77612357DD3
    Record-Route: <sip:server.domain.com.au:5061;transport=tls;opaqu​e=state:F;lr>;tag=979939159978D94B1CC557683CC07627
    Record-Route: <sip:server.domain.com.au:5061;transport=tls;lr>;t​ag=D98DD6387856815820B8A77612357DD3
    Record-Route: <sip:server.domain.com.au:5061;transport=tls;epid=​212336682833;lr;ms-key-info=AAEAAd5fgB2zCJuKJUrQAZ​sNiN7Rdf2OP7P4CDdEYhzeJcOCii5YjmTeMtsz3EmjXIuNgi_5​b30JZRPun9XUxIVFpc6gs9uexzcgQ46wibGt1ysnGC2feNZAgG​DUP1-21V8CflzxuaSZh8A4-W37pwPQiYGmOO2tQd9gtZAHIUix​Q2G9oDAaDHpKn59JnbPCOUjW-3sOpwSOeMCr088E_cyaNKQGUs​05M_q_WZAKF8BQB9k3IoNofk9ANhmBel-3hAyF9HBzS3LPLn1-​97RsNQHT1izFiJh5is9U3XeATJ45xU_4gNBhpRuicYLK-yt48X​DQqHFznTUVPo0zJDQ-xEbnEV6OS7zcay_2jSUg3Sx6tc8mXgxi​kd8I02Rf_b_LdbG-sNrX8OVG_7PWrIquprKykEj0WeLlaEDFBd​QkQcsVKyHm3-T3FBAHFrcUHA4YOwbGtW6K2Ktd8udJ0kEyjHh3​4B2-Gc1czr1C7Q4IDl7X7w2mo4n74Z3EYhWS8s0qWABtRbIGsI​y_tdDuWe2srrFpYg_axBx316kmHvNTZhiFzNqmWpJaXo0UnyJ3​UzA8fYcXUj6WaMnVDsyxUu3qaztpwacrrZQcwx2LjgoU7SVKkx​eAZxODoCmNtdyuRydRcmUT_A8B-4Zq4TRf-tz9nGz5OEJQ68cR​BZg_aq95fmZGP1pYKDfF1Xy3ZITzLzc_;ms-route-sig=apVu​IPCCfyeKrZIly3WpAr9uyi4-qNp9uMnq52Y0QezkZjq11kMgZx​9QAA>;ms-rrsig=apDspj0GfvYaSUD2rk62B_EWptxL9jVzfKr​eNWj_dwFVtjq11kMgZx9QAA;tag=3C19ED7A255CD46B526D92​A75CFB434F
    Record-Route: <sip:server.domain.com.au:5061;transport=tls;opaqu​e=state:T;lr>;tag=96EF6F280233691217CC3ABE68DB5DC3
    User-Agent: UCCAPI/15.0.4675.1000 OC/15.0.4675.1000 (Microsoft Lync)
    Ms-client-diagnostics: 51004; reason="Action initiated by user"
    Proxy-Authorization: TLS-DSK qop="auth", realm="SIP Communications Service", opaque="0344086F", targetname="server.domain.com.au", crand="3c4d71dd", cnum="24", response="7bf1620d04b14007827aa19a79682fefb688078d​"
    Content-Length: 0

    VVX Trace

    0217101229|sip  |0|29941|<<< Data received TLS
    0217101229|sip  |0|29941|    CANCEL sip:user1@domain.com.au:56462;transport=tls;ms-rec​eived-cid=11D5E00 SIP/2.0
    0217101229|sip  |0|29941|    Via: SIP/2.0/TLS 10.1.0.2:5061;branch=z9hG4bKF4F578A1.2FB1C493C5951​2EC;branched=FALSE
    0217101229|sip  |0|29941|    Authentication-Info: TLS-DSK qop="auth", opaque="737D74E4", srand="ED605741", snum="36", rspauth="8edb3e544f1f8c8199cf949f03afa6ae39754f3b"​, targetname="server.domain.com.au", realm="SIP Communications Service", version=4
    0217101229|sip  |0|29941|    Max-Forwards: 70
    0217101229|sip  |0|29941|    CSeq: 2761 CANCEL
    0217101229|sip  |0|29941|    Call-ID: fdda2d3b-f866-4fc0-911d-52325c367468
    0217101229|sip  |0|29941|    To: <sip:user@2domain.com.au>;epid=0004f2840839
    0217101229|sip  |0|29941|    From: <sip:user1@domain.com.au;epid=212336682833;tag=c3c​c787854
    0217101229|sip  |0|29941|    Content-Length: 0
    0217101229|sip  |0|29941|    Server: http%3A%2F%2Fwww.microsoft.com%2FLCS%2FDefaultRout​ing
    0217101229|sip  |0|29941|    ms-edge-proxy-message-trust: ms-source-type=AutoFederation;ms-ep-fqdn=server.do​main.com.au;ms-source-verified-user=verified;ms-so​urce-network=federation
    0217101229|sip  |0|29941|    Reason: SIP;cause=603;text="Decline"
    0217101229|sip  |0|29941|    ms-diagnostics-public: 5025;reason="Cancel sent by application for INVITE client transaction.";AppUri="http%3A%2F%2Fwww.microsoft.c​om%2FLCS%2FDefaultRouting"
    0217101229|sip  |0|29941|   

    Let me know if you want to see more trace.

    Thanks in advance

    Wednesday, February 18, 2015 3:20 AM

Answers

  • Video between Lync Server 2013 and VVX is not supported for the moment


    Note: Video Calls on Paired Devices Not Compatible with Microsoft Lync 2013


    BToE-enabled Polycom phones running UC software 5.0.0 cannot receive incoming video calls sent from contacts using Microsoft Lync 2013. However, you can receive video calls from contacts using Lync 2010. If you receive an incoming video call from a contact using Lync 2013, the call drops.

    This is from official Polycom document

    http://support.polycom.com/global/documents/support/user/products/voice/Lync_QuickUserGuide_UCS_4_1.pdf


    http://thamaraw.com

    • Proposed as answer by Eric_YangK Thursday, February 19, 2015 2:23 AM
    • Marked as answer by Buzz Bombers Thursday, February 19, 2015 10:44 AM
    Wednesday, February 18, 2015 4:18 AM

All replies

  • Video between Lync Server 2013 and VVX is not supported for the moment


    Note: Video Calls on Paired Devices Not Compatible with Microsoft Lync 2013


    BToE-enabled Polycom phones running UC software 5.0.0 cannot receive incoming video calls sent from contacts using Microsoft Lync 2013. However, you can receive video calls from contacts using Lync 2010. If you receive an incoming video call from a contact using Lync 2013, the call drops.

    This is from official Polycom document

    http://support.polycom.com/global/documents/support/user/products/voice/Lync_QuickUserGuide_UCS_4_1.pdf


    http://thamaraw.com

    • Proposed as answer by Eric_YangK Thursday, February 19, 2015 2:23 AM
    • Marked as answer by Buzz Bombers Thursday, February 19, 2015 10:44 AM
    Wednesday, February 18, 2015 4:18 AM
  • Thanks Thamara,

    Do you mean Lync server or Lync client. We are using Lync Server 2013 and to test, I installed 2010 client and it worked fine.

    Wednesday, February 18, 2015 5:25 AM
  • In Lync Server 2013, it dropped the support for SIF codec which could be the reason that it failed to connect. And obviously Lync 2013 client will not have the codec within it's stack. Lync 2010 client might still have it and probably negotiating it with the VVX. But, try to get it in to a video conference scheduled by Lync server 2013. It should not work.


    http://thamaraw.com

    Wednesday, February 18, 2015 6:25 AM