Forum Discussion

Techdemonsuk's avatar
Techdemonsuk
Copper Contributor
Aug 11, 2019

Skype for business CU 10 install breaks call transfer on polycom VVX

We have on premise SFB 2 FE 2Edge 2 MediationServer 2 web app 2 SQL always on We use pureip for the gateway and sit web services behind a load balancer All other services use Microsoft recomm...
Installation
PSTN Calling
Voice
Techdemonsuk's avatar
Techdemonsuk
Copper Contributor
Aug 13, 2019
Any help on this?
  • ED9227's avatar
    ED9227
    Copper Contributor
    Aug 13, 2019

    Techdemonsuk 

     

    About the same problem here since CU 10.

    Internal transfer coming from internal working on Polycom VVX.

    Internal transfer coming from external failed on Polycom VVX.

    Internal transfer coming from external on SfB Client (When VVX Unpaired) is working.

     

    Updated Software version on VVX 501 to last.

    Updated btoe connector to last.

    No change.

     

    • Techdemonsuk's avatar
      Techdemonsuk
      Copper Contributor
      Aug 13, 2019
      Think we have figured this out the candidate list that’s sent out to remote party has an ipv4 address range in it that is used by the caller
      Our mediation server and edge server all have 3 nics
      1x fe
      1xbe
      1x management
      We have local persistent routes to correctly route the traffic out of the nic with default gateway
      Problem is Skype ignores this and because the management nic also is route able it adds this address range to the candidate list.
      Problem occurs as the management range is 192.168.30.0
      When you try and transfer the local Skype client sees the candidate list and this I have a local route and tears down the transfer.

      We now need to figure how to get the management range out of the advertised candidate list.
      • ED9227's avatar
        ED9227
        Copper Contributor
        Aug 22, 2019

        Techdemonsuk 

         

        It is now under investigation by Microsoft at least:

        https://support.microsoft.com/en-us/help/4518475/polycom-vvx-series-call-features-fail-after-july-2019-skype-update

         

        I have the same kind of message from SfB:

        (SIPStack,CCryptoServiceCng::GenerateAndCompareHash:CryptoService.cpp(2637)) ( 0000001AB9AFB5D0 ) Exit - hash doesn't match. Returned 0xC3E93C14(SIPPROXY_E_SIGNATURE_INVALID)

        (SIPStack,CCryptoServiceCng::HashAndCompare:CryptoService.cpp(2566)) ( 0000001AB9AFB5D0 ) Exit. Returned 0xC3E93C14(SIPPROXY_E_SIGNATURE_INVALID)

        (SIPStack,CCryptoModule::RouteCryptoHashAndCompare:CryptoModule.cpp(914)) ( 0000001AB8154770 ) Exit - verify failed. Returned 0xC3E93C14(SIPPROXY_E_SIGNATURE_INVALID)

        (SIPStack,CSIPRequest::ValidateRouteHeaders:SIPRequest.cpp(7093)) ( 0000001AB902E250 ) Exit - route set signature is invalid. Returned 0xC3E93C14(SIPPROXY_E_SIGNATURE_INVALID)

        (SIPStack,CSIPRequest::VerifyIncomingRouteHeaders:SIPRequest.cpp(2302)) ( 0000001AB902E250 ) Failed validating route headers

         

        So something is dodgy between SfB and Polycom VVX since CU10...

         

         

         

Resources