Remote phone connection on CME

francois.staiesse · ‎02-21-2008

Hello,

I would like to connect a remote IP phone (SEP001EF7C366EE) through the WAN on a CallManager Express 4.2 but I experience registration issues.

When I connect the IP phone in the remote location, it's always "registering" and, in the CLI of the CME, I always receive "registered/unregistered" messages (see here below).

Following the customer, there is no bandwith problem between the 2 sites, there are no blocked ports and the TFTP server is correctly configured in the DHCP scope.

Does someone know something else that I would need to configure/check?

Thanks in advance,

FranÃ§ois

Feb 19 12:43:31.387: ephone-27[-1]:SkinnyVideoParmsUpdate: phone: 26, action: 2, dn_index: -1

Feb 19 12:43:31.387: ephone-27[11][SEP001EF7C366EE]:phone SEP001EF7C366EE re-associate OK on socket[11]

Feb 19 12:43:31.387: %IPPHONE-6-REGISTER: ephone-27:SEP001EF7C366EE IP:10.32.45.40 Socket:11 DeviceType:Phone has registered.

Feb 19 12:43:31.387: Phone 26 socket 11

Feb 19 12:43:31.387: Skinny Local IP address = 10.33.160.35 on port 2000

Feb 19 12:43:31.387: Skinny Phone IP address = 10.32.45.40 51755

Feb 19 12:43:31.387: ephone-27[11]:SkinnyVideoParmsUpdate: phone: 26, action: 2, dn_index: -1

Feb 19 12:43:31.387: ephone-27[11][SEP001EF7C366EE]:Signal protocol ver 8 to phone with ver 9

Feb 19 12:43:31.387: ephone-27[11][SEP001EF7C366EE]:Date Format D/M/Y

Feb 19 12:43:31.387: ephone-27[11]:RegisterAck sent to sockettype ephone socket 11: keepalive period 30 use sccp-version 8

Feb 19 12:43:31.387: ephone-27[11]:CapabilitiesReq sent

Feb 19 12:43:51.975: ephone-27[11][SEP001EF7C366EE]:CallPrompt line 0 ref 0: Cisco Unified CME

Feb 19 12:43:51.975: ephone-27[11][SEP001EF7C366EE]:SkinnyCheckPendingCallBackPhone scan 0 lines

Feb 19 12:44:21.975: ephone-27[11][SEP001EF7C366EE]:CallPrompt line 0 ref 0: Cisco Unified CME

Feb 19 12:44:21.975: ephone-27[11][SEP001EF7C366EE]:SkinnyCheckPendingCallBackPhone scan 0 lines

Feb 19 12:44:31.359: New Skinny socket accepted [1] (11 active)

Feb 19 12:44:31.359: sin_family 2, sin_port 50223, in_addr 10.32.45.40

Feb 19 12:44:31.359: skinny_add_socket 1 10.32.45.40 50223

Feb 19 12:44:31.371: ephone-(27)[12] StationRegisterMessage (11/11/96) from 10.32.45.40

Feb 19 12:44:31.371: ephone-(27)[12] Register StationIdentifier DeviceName SEP001EF7C366EE

Feb 19 12:44:31.371: ephone-(27)[12] StationIdentifier Instance 0 deviceType 309

Feb 19 12:44:31.371: ephone-27[11]:stationIpAddr 10.32.45.40

Feb 19 12:44:31.371: ephone-27[11][SEP001EF7C366EE]:maxStreams 3

Feb 19 12:44:31.371: ephone-27[11][SEP001EF7C366EE]:From Phone raw protocol Ver 0x85700009

Feb 19 12:44:31.371: ephone-27[11][SEP001EF7C366EE]:protocol Ver 0x85700009

Feb 19 12:44:31.371: ephone-27[11][SEP001EF7C366EE]:phone-size 5432 dn-size 688

Feb 19 12:44:31.371: ephone-(27) Allow any Skinny Server IP address 10.33.160.35

Feb 19 12:44:31.371: ephone-27[11][SEP001EF7C366EE]:Found entry 26 for 001EF7C366EE

Feb 19 12:44:31.371: ephone-27[11][SEP001EF7C366EE]:socket change 11 to 12

Feb 19 12:44:31.371: ephone-27[11][SEP001EF7C366EE]:DisAssociate: Closed socket 11 while REGISTERED

Feb 19 12:44:31.371: ephone-27[11][SEP001EF7C366EE]:skinny_delete_socket [11]

Feb 19 12:44:31.371: %IPPHONE-6-UNREGISTER_ABNORMAL: ephone-27:SEP001EF7C366EE IP:10.32.45.40 Socket:11 DeviceType:Phone has unregistered abnormally.

Feb 19 12:44:31.371: ephone-27[-1][SEP001EF7C366EE]:FAILED: CLOSED old socket -1

Feb 19 12:44:31.371: ephone-27[-1][SEP001EF7C366EE]:bulk_speeddial_init_ephone: 26

Feb 19 12:44:31.371: ephone-27[-1]:SkinnyVideoParmsUpdate: phone: 26, action: 2, dn_index: -1

Feb 19 12:44:31.371: ephone-27[12][SEP001EF7C366EE]:phone SEP001EF7C366EE re-associate OK on socket[12]

Feb 19 12:44:31.371: %IPPHONE-6-REGISTER: ephone-27:SEP001EF7C366EE IP:10.32.45.40 Socket:12 DeviceType:Phone has registered

gmarogi · ‎02-27-2008

This issue normally occurs if there is too much of broadcast traffic reaching the Ip phone. Try to reduce the broadcasr traffic to resolve the issue.