Forum Discussion

msabat's avatar
msabat
Brass Contributor
Feb 20, 2020

Polycom VVX400 with Teams

Hello.   My account was on SfB on Prem. I was moved to Teams Only mode (Hybrid).   Is there any way I can still use my old Polycom VVX400?
  • Anson2400's avatar
    Anson2400
    Aug 07, 2020

    I got my problem figured out.  My problem was there was some old proxy config in my VVX .  After I cleared that out my VVX400 registered with no problems. Anson2400 

LinusCansby's avatar
LinusCansby
MVP
Aug 14, 2020

msabat What is not working? Does 911 work from a Teams client when signed in with the same account as you use for your VVX?

 

Btw. your VVX will support Teams beyond 31/7 2023.

msabat's avatar
msabat
Brass Contributor
Aug 14, 2020

LinusCansby So in Teams emergency routing policy I have setup 9911 for emergency:

 

Emergency dial mask - 9911

Emergency dial string - 1414566911

Dynamic emergency calling - On

 

I have network with subnets including my Polycom and Windows app IPs.

 

When I call 9911 from my Windows app - all works fine - call is marked as emergency and routed correctly throu my SBC.

 

When I call 911 from my Polycom I get nothing.

  • msabat's avatar
    msabat
    Brass Contributor
    Aug 24, 2020

    I finally removed number recognition from Polycom but Teams doesn't still work correctly with 911

  • msabat's avatar
    msabat
    Brass Contributor
    Aug 19, 2020

    LinusCansby 

    Jeff_Schertz 

     

    So when I dial 9911 from Polycon that call is translated in standard 4digit normalization rule instead of emergency routing policy.  And that happens when on Polycom is signed in standard Teams user. For that user on Windows app all works fine.

     

    Line 4094: 0818133046|so   |3|00|[CSoRegexDigitMapElement]: Checking 9911 against ^(\d{4})$

    Line 4095: 0818133046|so   |3|00|[CSoRegexDigitMapElement]: RegexMap ^(\d{4})$ Declared match 9911 -> +14145669911

     

    Basing on my emergency routing policy 9911 should be translated to 1414566911 and routed to SBC.

     

     

  • msabat's avatar
    msabat
    Brass Contributor
    Aug 14, 2020

    LinusCansby Looks like Teams doesn't setup my Polycom location correctly.

     

    On Polycom I have:

     

    o=Eyeball 3366812679 945242496 IN IP4 10.204.5.194
    s=Eyeball AnyFirewall Engine Sep 10 2019
    c=IN IP4 10.204.5.194
    t=0 0
    m=audio 50012 RTP/AVP 0
    a=ice-pwd:QU8lhnlnk/pUz+RCIVp5VKFd
    a=ice-ufrag:yl6r
    a=candidate:1 1 UDP 2130706431 10.204.5.194 50012 typ host
    a=candidate:1 2 UDP 2130706430 10.204.5.194 50013 typ host
    a=candidate:2 1 TCP-PASS 6619135 52.112.12.217 53336 typ relay raddr 52.112.12.251 rport 51739
    a=candidate:2 2 TCP-PASS 6619134 52

    Local IP addresses used for SDP are 10.204.5.194 and
    0814130522|sip |0|00|Calling CreateLocalSdp bIsLyncCall : 1 Line :6709
    0814130522|sip |3|00|Should parse SDP v=0
    o=Eyeball 3366812679 945242496 IN IP4 10.204.5.194

     

    a=candidate:1 1 UDP 2130706431 10.204.5.194 50012 typ host
    a=candidate:1 2 UDP 2130706430 10.204.5.194 50013 typ host
    a=candidate:2 1 TCP-PASS 6619135 52.112.12.217 53336 typ relay raddr 52.112.12.251 rport 51739
    a=candidate:2 2 TCP-PASS 6619134 52.112.12.217 53336 typ relay raddr 5
    0814130522|sip |3|00|IsMediaAddressZero local sdp connection IP is 10.204.5.194

     

     

     

    And my Polycom IP is correct.

     

    But on Teams log for my test call I see:

    Connectivity_LocalSite 10.0.137.0:51576
    Connectivity_LocalAddress 10.0.137.0:51576

Resources