Versions Compared

Old Version 12

changes.mady.by.user Ribbon Communications

Saved on

compared with

New Version Current

changes.mady.by.user Ribbon Communications

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Add_workflow_for_techpubs
AUTH1UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'}
JIRAIDAUTHSYM-2302227627
REV5UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'}
REV6UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'}
REV3UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26c85500c98a00a02355cd1c2f0155cd26cc5207f0, userName='null'}
REV1UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cc5207f0, userName='null'}

 

Panel

This section includes:

Table of Contents
maxLevel3

 

...

Confirm the public SBC Edge FQDN is properly mapped to the External IP used in Configure CCE (via SBC Edge WebUI).

Note

Any changes to the Configure CCE tab requires the CCE to be redeployed.

 

  1. From a PC with open internet access, run Nslookup on the public CCE FQDN. If the result is "Error: Requested name myccesite1.mydomain.com could not be resolved", the Public DNS server needs to be corrected.

    Code Block
    nslookup av.contoso.com

  2. Ensure the IP address returned is the Edge Server External Public IP. If the IP is not the correct one, you need to fix your Public DNS server.

    Caption
    0Figure
    1IP Address

     

  3. Ensure the Edge VM has proper DNS resolution.

...