cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
734
Views
5
Helpful
2
Replies

Unable to get MPP Phone Remote SDK Sample working

Stephen Welsh
Level 4
Level 4

Hi,

I'm trying out the Cisco IP Multiplatform Phones Remote SDK but unable to get the phone to open a WebSocket connection.

I've downloaded and setup the sample as per here:

https://github.com/CiscoDevNet/multiplatform-phones

 

Here are some log entries relating to the connection error:

 

6833 NOT Dec 13 23:58:32.796927 (1351:1351) apigateway-API_GATEWAY.main lws_service disconnect requested.
6834 NOT Dec 13 23:58:32.800824 (1351:1351) apigateway-API_GATEWAY.main lws_service disconnect requested.
6835 NOT Dec 13 23:58:32.803252 (1317:1413) voice-pal_commit_update EH_FOR_EACH_HDLR_END 0x231e5b4
6836 NOT Dec 13 23:58:32.805020 (1317:1413) voice-Firewall state: Enabled
6837 NOT Dec 13 23:58:32.805158 (1317:1413) voice-Firewall Option:[]
6838 NOT Dec 13 23:58:34.721089 [2021/12/13 23:58:34:7207] NOTICE: Connect failed errno=110
6839 ERR Dec 13 23:58:34.720797 (1351:1351) apigateway-API_GATEWAY.callback_lws_method Websocket Client Connection Error connect failed
6840 NOT Dec 13 23:58:34.723419 (1351:1351) apigateway-API_GATEWAY.main lws_service disconnect requested.
6841 NOT Dec 13 23:58:34.723466 (1351:1351) apigateway-API_GATEWAY.main lws_service Connection Error or Connection Closed

 

The phone logs it says connection failed, I know there are no network issues as I can connect to the python WebSocket from another PC on the network.

 

I suspect this is a firmware issue (or the firmware version I'm on sip88xx.11-3-3MPP0001-377.loads)

 

Any suggestions appreciated.

 

Stephen

1 Accepted Solution

Accepted Solutions

rmorehea
Cisco Employee
Cisco Employee

The 110 connect error is usually from the initial outgoing connection failing at the TCP socket/low-level networking level. There could be multiple reasons for the phone being unable to successfully complete this connection:

  • VLAN - The phone could be on a dedicated VLAN that doesn't have routing to the network the PC running the sample is on.
  • Firewall on phone - MPP phone has a built-in firewall that could be interfering with the phone's ability to open an outgoing socket connection.
  • Firewall on PC - The phone may not be trusted by the firewall on the PC in the same way as the PC that was able to successfully connect.
  • DNS - If you are using a name rather than an IP to specify the WebSocket connection, it could be getting resolved to the wrong IP on the phone, but the correct IP on the other PC.

View solution in original post

2 Replies 2

rmorehea
Cisco Employee
Cisco Employee

The 110 connect error is usually from the initial outgoing connection failing at the TCP socket/low-level networking level. There could be multiple reasons for the phone being unable to successfully complete this connection:

  • VLAN - The phone could be on a dedicated VLAN that doesn't have routing to the network the PC running the sample is on.
  • Firewall on phone - MPP phone has a built-in firewall that could be interfering with the phone's ability to open an outgoing socket connection.
  • Firewall on PC - The phone may not be trusted by the firewall on the PC in the same way as the PC that was able to successfully connect.
  • DNS - If you are using a name rather than an IP to specify the WebSocket connection, it could be getting resolved to the wrong IP on the phone, but the correct IP on the other PC.

Perfect, didn't realise I had a NAT boundary on the phone network, my bad

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: