DX70 registration over MRA.

[Sushant Sharma]

Hi All,

Please suggest me about DX70 registration over MRA.

I have upgraded dx 70 with latest firmware

sipdx70.10-2-4-99

I am geeting below option in DX70 after rebooting with new Firmware

Expressway login details

• Service Name:
• Username:
• Password:

Please suggest me what i need to add in these fields because i tried below options

1)

service name : cisco.com

username : sushants

passs abc@123

2) service name : collab1.cisco.com ( expressswaye FQDN)

username : sushants

passs abc@123

Both cases its not reaching expressway e .

i checked event logs .

[Acevirgil de Ocampo · Accepted solution]

These would be the same credentials you use for Jabber MRA login. Do you have working Jabber client that was already provisioned successfully and can be able to login?  Log in to Jabber via MRA to ensure and verify MRA functions are working. Use same credentials to login on your DX70 endpoint via Expressway-E. 

Service Name: <Expressway-E FQDN>

Username: <same user login as Jabber>

Password: <same user password as Jabber>

What is the firmware version of your VCS (Expressway-E)? You should be running X8.5 or later to support DX endpoints using VCS via MRA.

You would need to verify also if the public (external) DNS configured with _collab-edge._tls.<domain> SRV records so that endpoints can discover the VCS Expressways to use for MRA.

In your case for example:

Expressway-E FQDN = collab1.cisco.com

Domain = cisco.com

Verify from a Windows computer located on the Internet network, open a command line and do nslookup:

To check the A record, type:

nslookup collab1.cisco.com

The response should include the corresponding Expressway-E
public IP address

To check the SRV record, type:

nslookup -type=srv _collab_edge.tls.cisco.com

The response should include the FQDN of the Expressway-E

regards,

Acevirgil

[Sushant Sharma]

Hi Dear,

yes we have Cisco jabber is working fine over expressway

i tried same but geeting error service not fund please verify your service domain and your internet connectivity and then try again

[Acevirgil de Ocampo]

Make sure the device have acquired IP address with working DNS to reach the Collaboration Edge services on the internet.

Have you tried this procedure:

regards,

Acevirgil

[Sushant Sharma]

Hi Guys,

now its working fine , issue was in expressway certificate .

[Acevirgil de Ocampo]

Great that you found the issue and its been resolved. Please share also what are the modifications you performed regarding the certificate so others with same problem would have insights in same issues encountered.

regards,

Acevirgil

[Sushant Sharma]

I took logs from Dx using cisco collaboration problem reporting tool ,In  Dx logs i found first certificate mismatch

ERR edge_gateway: Verify Cert[2]: Certificate doesn't match

then i worked on certificate  in my certificate Chane secure server  certificate was missing . i asked to CA please provide me this secure certificate after uploading certificate  its immediately registered

For registration i have  used :

service domain : Domain name ( not Expressway FQDN, its was  not working with FQDN)

username : same like Jabber

Password : same like jabber

regards,

sushant

[Acevirgil de Ocampo]

Thanks for the update.

regards,

Acevirgil

[s.sitthichai]

Dear Sushant

Sorry, You mean certificate issue.

Where are uploading certificate ? Thanks.