Re: SX10 registering on VCS-C Gatekeeper

jluis_alves · ‎09-27-2017

Hi,

I want registering an SX10 on a VCS-C working as a gatekeeper.

Can someone help me with this? can someone provide me a guide how to configure this on VCS-C and SX10?

Thanks.

Patrick Sparkman · ‎09-27-2017

Steps on how to configure VCS is found in the VCS Configuration Guides, once the VCS is deployed and configured, you can register the SX10 to it. Configure the following options to register an SX10 to VCS using H323 and/or SIP. In order to register the SX10 using H323, it requires minimum CE8.2 software.

H323:

H323 Gatekeeper Address
H323 H323Alias E164 or H323Alias ID
H323 Authentication LoginName
H323 Authentication Password

SIP

SIP Proxy 1 Address
SIP URI
SIP Authentication UserName
SIP Authentication Password

You only need the H323/SIP Authentication fields if your VCS requires endpoints to authenticate with a username/password before it can regsiter, this is determined by the authentication poicy on the Defualt Subzone.

If your VCS has the device provsioning option key and you utlize TMS, you can also TMSPE to provision endpoints to the VCS, refer to the TMSPE Deployment Guides for information on this process.

jluis_alves · ‎09-28-2017

Thanks Patrick,

Now when i try to register the SX10 i see on the Expressway Logs this message:

"vcs: Event="Registration Rejected" Reason="License limit exceeded" Service="SIP" Src-ip="172.16.25.126" Src-port="5061" Protocol="TLS" AOR="ciscosx10@192.168.191.8" Contact="sip:ciscosx10@172.16.25.126:5061;transport\=tls" Duration="60" Level="1" UTCTime="2017-09-28 10:11:22,667""

Can you help me?

Thanks in advance

jluis_alves · ‎09-28-2017

Hi,

I'm waiting for a license to go further with this deployment.

I'll need to register a 3rd party equipment with this VCS-C. Can i do it with SIP?

Thanks in advance

Patrick Sparkman · ‎09-28-2017

Are you running VCS in demo mode? If so you can only register 3 endpoints max, with the full licensed version you can register up to 2500 endpoints.
You can register third-party standards-based endpoints using H323 and/or SIP to the VCS, ie: Polycom, Lifesize, etc.

jluis_alves · ‎10-03-2017

Hi Patrick.

Now we sucesseful registered our SX10, but when we try to make a call we got this log.

2017-10-03T18:08:32.529+01:00	tvcs: Event="Search Completed" Reason="Not found" Service="H323" Src-alias-type="H323" Src-alias="172.16.25.126" Dst-alias-type="H323" Dst-alias="401@orbcom.pt" Call-serial-number="a1079f41-91e7-411f-b9e6-41b916c4aa98" Tag="9a8a8311-8ddf-487a-b6a7-640d5f6d2727" Detail="found:false, searchtype:LRQ" Level="1" UTCTime="2017-10-03 17:08:32,529"
2017-10-03T18:08:32.528+01:00	tvcs: Event="Search Attempted" Service="H323" Src-alias-type="H323" Src-alias="172.16.25.126" Dst-alias-type="H323" Dst-alias="401@orbcom.pt" Call-serial-number="a1079f41-91e7-411f-b9e6-41b916c4aa98" Tag="9a8a8311-8ddf-487a-b6a7-640d5f6d2727" Detail="searchtype:LRQ" Level="1" UTCTime="2017-10-03 17:08:32,528"
2017-10-03T18:08:32.523+01:00	tvcs: Event="Call Rejected" Service="SIP" Src-ip="192.168.191.8" Src-port="25004" Src-alias-type="SIP" Src-alias="sip:172.16.25.126" Dst-alias-type="SIP" Dst-alias="sip:401@orbcom.pt" Call-serial-number="2b97e221-709b-4aa8-9ca7-f0557996cbec" Tag="9a8a8311-8ddf-487a-b6a7-640d5f6d2727" Detail="Not found" Protocol="TLS" Response-code="404" Level="1" UTCTime="2017-10-03 17:08:32,522"
2017-10-03T18:08:32.523+01:00	tvcs: Event="Search Completed" Reason="Not found" Service="SIP" Src-alias-type="SIP" Src-alias="172.16.25.126" Dst-alias-type="SIP" Dst-alias="sip:401@orbcom.pt" Call-serial-number="2b97e221-709b-4aa8-9ca7-f0557996cbec" Tag="9a8a8311-8ddf-487a-b6a7-640d5f6d2727" Detail="found:false, searchtype:INVITE, Info:Policy Response" Level="1" UTCTime="2017-10-03 17:08:32,522"
2017-10-03T18:08:32.523+01:00	tvcs: Event="Search Attempted" Service="SIP" Src-alias-type="SIP" Src-alias="172.16.25.126" Dst-alias-type="SIP" Dst-alias="sip:401@orbcom.pt" Call-serial-number="2b97e221-709b-4aa8-9ca7-f0557996cbec" Tag="9a8a8311-8ddf-487a-b6a7-640d5f6d2727" Detail="searchtype:INVITE" Level="1" UTCTime="2017-10-03 17:08:32,520"

Patrick Sparkman · ‎10-03-2017

Do you have your VCS fully configured, you need to add search rules yet if you haven't done so already, take a look at the VCS Basic Deployment Guides.

jluis_alves · ‎10-04-2017

Hi,

We had already configured search roules. We see same error on both VCS-C/E . It looks VCS-E don´t have an answer.

a74fd9ca-7b13-4f2c-ba05-80063accc8c3 sip:ciscosx10 sip:401@orbcom.pt SIP <-> 404 Not found Expressway

jluis_alves · ‎10-04-2017

This is the log of same call on VCS-C

2017-10-04 15:45:48 2017-10-04 15:45:48 0 seconds sip:ciscosx10 sip:401@orbcom.pt Traversal SIP <-> H323 Standards-based 404 Not found This system View

Patrick Sparkman · ‎10-04-2017

Can you upload a screenshot of any transforms and search rules and a copy of the search history of a failed call.

jluis_alves · ‎10-04-2017

Thanks Patrick.

I just upload the info you ask.

Thanks in advance.

jluis_alves · ‎10-04-2017

VCS-E Captures.

Thanks in advance

Patrick Sparkman · ‎10-04-2017

Which VCS are the two endpoint's (ciscosx10 and 401@orbcom.pt) registered to, and the protocol used for both?
If 401@orbcom.pt is registered to either VCS, you need to enable your Any match LocalZone search rule, as the current search rule you have enabled will only match aliases with outsystems.com domain.
Not sure why the call didn't go out your DNS zone, your search rule is exactly as mine, but I have mine set to Any instead of All zones.

jluis_alves · ‎10-06-2017

Hi Patrick,

the 401@orbcom.pt is a device on a remote site registered on another infrastruture.