Extention mobility over expressway

[schwabcm]

We have upgraded to CUCM 11.5, UCCX 11.6 and our Expressway is v8.9.

We understood that this would allow the ability to log into Extension Mobility while a telephone (8851) is remote.  However when we do this we receive a 404 page not found error.

Is this a situation where a port needs to be opened on our network firewall or is there something within our system that needs to be fixed? 

We are trying to identify a remote call center agent solution and the ability to bring the phone home was one of our ideas.

[Ratheesh Kumar]

Hi there

Try upgrading to X8.10.4.

CSCvd68778 - EM shown 404 error in MRA

Description

Symptom:
Actual Behavior:
Getting 404 error for EM login and also while entering setPIN in 78xx and 88xx when phones are registered via MRA

Conditions:
Environment Matrix:
Unified CM : 12.0.0.99832-1
VCS-C / VCS-E : 8.9.1

Known Affected Releases:

(1)

 X8.9.1

Known Fixed Releases:

(1)

 X8.10.4

https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvd68778/?rfs=iqvred

Hope this Helps

Cheers
Rath!
***Please rate helpful posts***

[schwabcm]

Thank you very much Ratheesh, greatly appreciate the information.  Is the upgrade to Expressway relatively easy, does it entail rebooting CM and/or UCCX as well as Expressway?

[Jonathan Schulenberg]

Fairly easy but you need to keep up with Expressway updates as you would any other directly internet-facing system. For example, they patched seven CVEs between X12.5.1 and x12.5.2 alone.

You should be able to make it to X8.11 as-is. The jump to X12.5 will require an option key to validate you still have active support.

As always, keep an eye on the release notes. The main gotcha is the requirement for A and PTR records - including the public IP address. Unless you have your own prefix delegation this typically requires the cooperation of your ISP to get the public PTR created.

[jonathan.salter]

Have you allowed the Extension Mobility webpage though the Core?

Configuration=> Unified Communications=> HTTP Allow List=> Editable inbound rules

[Roger Kallberg]

Hi,

I'm looking for information on what is needed to add in the allow list to enable use of extension mobility via MRA? What would the URL be that is needed to be added in the allow HTTP page? The deployment guide doesn't provide any useful information, that I've been able to find anyway, it just states that it would be required to for EM to work via MRA.

• You can add your own inbound rules, if clients from outside need to access other web services inside the enterprise. For example, these services may require you to configure the allow list.

  • Jabber Update Server

  • Cisco Extension Mobility

  • Directory Photo Host

  • Advanced File Transfer (AFT)

  • Problem Report Tool server

We run CM 12.5.1SU1 and X12.5.6.

Any help on this would be appreciated.

[jonathan.salter]

On the Core....

Configuration>Unified Communications>HTTP Allow List>Editable Inbound Rules

Add a rule, name it

URL -http://<publisher address>:8080/emapp/EMAppServlet

Allow Methods- Use Default

Match Type- Prefix Match

Should be good to go after that.

[Roger Kallberg]

---

@jonathan.salter wrote:

On the Core....

Configuration>Unified Communications>HTTP Allow List>Editable Inbound Rules

Add a rule, name it

URL -http://<publisher address>:8080/emapp/EMAppServlet

Allow Methods- Use Default

Match Type- Prefix Match

Should be good to go after that.

---

Thank you, will test this.

[Roger Kallberg]

Update on this, I also needed to add these rules to get it rid of 404 errors for change PIN function and also at the time of successfull login/logout to EM.

Stop 404 error at login/logout

https://<IP of EM CM node>:8443/ccmcip/getservicesmenu.jsp

Stop 404 error at PIN change

http://<IP of EM CM node>:80/changecredential/ChangeCredentialServlet

For these I used the same settings as for the other rule.

Allow Methods- Use Default

Match Type- Prefix Match

In all there was 3 rules needed per CM node that run the EM service.

As per Jonathan reply, with slight modify as we don't have port 8080 used for services on CM.
http://<IP of EM CM node>:80/emapp/EMAppServlet