Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

Some IP Phones keeps registering to SRST

                 Hi guys, i need your help regarding our issue with our IP phones and SRST. Some phones (not all) keeps going to SRST mode even if the gateway router is not loosing connectivity to the CCM. We already changed the phone

ccm-manager fallback-mgcp
ccm-manager redundant-host 10.224.16.6
ccm-manager mgcp
no ccm-manager fax protocol cisco
ccm-manager music-on-hold
ccm-manager config server 10.224.16.3 10.224.16.8
ccm-manager config
!
mgcp
mgcp call-agent 10.224.16.7 2427 service-type mgcp version 0.1
mgcp dtmf-relay voip codec all mode out-of-band
mgcp rtp unreachable timeout 1000 action notify
mgcp modem passthrough voip mode nse
mgcp package-capability rtp-package
mgcp package-capability sst-package
mgcp package-capability pre-package
no mgcp package-capability res-package
no mgcp package-capability fxr-package
no mgcp timer receive-rtcp
mgcp sdp simple
no mgcp fax t38 ecm
mgcp fax t38 inhibit
mgcp rtp payload-type g726r16 static
mgcp bind control source-interface GigabitEthernet0/0
mgcp bind media source-interface GigabitEthernet0/0
!
mgcp profile default


call-manager-fallback
secondary-dialtone 9
max-conferences 12 gain -6
transfer-system full-consult
limit-dn 7935 1
limit-dn 7940 2
limit-dn 7960 2
limit-dn 7970 8
timeouts interdigit 3
ip source-address 172.20.180.65 port 2000
max-ephones 300
max-dn 336 dual-line preference 2
transfer-pattern .T
keepalive 10

Here is the sample logs

Log Buffer (4096 bytes):

6 DeviceType:Phone has registered.

354014: Jul  5 09:33:59 GMT: %IPPHONE-6-UNREGISTER_NORMAL: ephone-79:SEP001B5452DAC4 IP:66.202.132.242 Socket:6 DeviceType:Phone has unregistered normally.

354015: Jul  5 10:29:05 GMT: %IPPHONE-6-REG_ALARM: 10: Name=SEP001818856C01 Load= SCCP70.8-5-2S Last=TCP-timeout

354016: Jul  5 10:29:05 GMT: %IPPHONE-6-REGISTER_NEW: ephone-43:SEP001818856C01 IP:10.118.76.253 Socket:3 DeviceType:Phone has registered.

354017: Jul  5 10:32:06 GMT: %IPPHONE-6-UNREGISTER_NORMAL: ephone-43:SEP001818856C01 IP:66.202.132.242 Socket:3 DeviceType:Phone has unregistered normally.

354018: Jul  5 10:34:14 GMT: %SEC_LOGIN-5-LOGIN_SUCCESS: Login Success [user: v.vidallon] [Source: 90.152.3.38] [localport: 23] at 10:34:14 GMT Thu Jul 5 2012

354019: Jul  5 11:19:42 GMT: %SEC_LOGIN-5-LOGIN_SUCCESS: Login Success [user: l.arca] [Source: 90.152.3.38] [localport: 23] at 11:19:42 GMT Thu Jul 5 2012

354020: Jul  5 12:24:24 GMT: %IPPHONE-6-REG_ALARM: 10: Name=SEP001EF7282855 Load= SCCP70.8-5-2S Last=TCP-timeout

354021: Jul  5 12:24:24 GMT: %IPPHONE-6-REGISTER_NEW: ephone-198:SEP001EF7282855 IP:10.118.76.215 Socket:3 DeviceType:Phone has registered.

354022: Jul  5 12:27:05 GMT: %IPPHONE-6-UNREGISTER_NORMAL: ephone-198:SEP001EF7282855 IP:66.202.132.242 Socket:3 DeviceType:Phone has unregistered normally.

354023: Jul  5 14:14:53 GMT: %SEC_LOGIN-5-LOGIN_SUCCESS: Login Success [user: d.estalilla] [Source: 90.152.3.38] [localport: 23] at 14:14:53 GMT Thu Jul 5 2012

354024: Jul  5 15:00:19 GMT: %IPPHONE-6-REGISTER_NEW: ephone-40:SEP00181844C13F IP:10.118.76.167 Socket:35 DeviceType:Phone has registered.

354025: Jul  5 15:00:19 GMT: %IPPHONE-6-REG_ALARM: 10: Name=SEP00181844C13F Load= SCCP70.8-5-2S Last=TCP-timeout

354026: Jul  5 15:03:20 GMT: %IPPHONE-6-UNREGISTER_NORMAL: ephone-40:SEP00181844C13F IP:66.202.132.242 Socket:35 DeviceType:Phone has unregistered normally.

354027: Jul  5 15:11:06 GMT: %IPPHONE-6-REG_ALARM: 10: Name=SEP001EBE908B97 Load= SCCP70.8-5-2S Last=TCP-timeout

354028: Jul  5 15:11:06 GMT: %IPPHONE-6-REGISTER_NEW: ephone-34:SEP001EBE908B97 IP:10.118.77.13 Socket:9 DeviceType:Phone has registered.

354029: Jul  5 15:14:07 GMT: %IPPHONE-6-UNREGISTER_NORMAL: ephone-34:SEP001EBE908B97 IP:66.202.132.242 Socket:9 DeviceType:Phone has unregistered normally.

354030: Jul  5 15:28:01 GMT: %IPPHONE-6-REG_ALARM: 10: Name=SEP001EBE908A5B Load= SCCP70.8-5-2S Last=TCP-timeout

354031: Jul  5 15:28:01 GMT: %IPPHONE-6-REGISTER_NEW: ephone-126:SEP001EBE908A5B IP:10.118.76.249 Socket:12 DeviceType:Phone has registered.

354032: Jul  5 15:28:25 GMT: %IPPHONE-6-REG_ALARM: 10: Name=SEP000AB80D154B Load= SCCP70.8-5-2S Last=TCP-timeout

354033: Jul  5 15:28:25 GMT: %IPPHONE-6-REGISTER_NEW: ephone-44:SEP000AB80D154B IP:10.118.76.221 Socket:4 DeviceType:Phone has registered.

354034: Jul  5 15:30:43 GMT: %IPPHONE-6-UNREGISTER_NORMAL: ephone-126:SEP001EBE908A5B IP:66.202.132.242 Socket:12 DeviceType:Phone has unregistered normally.

354035: Jul  5 15:31:07 GMT: %IPPHONE-6-UNREGISTER_NORMAL: ephone-44:SEP000AB80D154B IP:66.202.132.242 Socket:4 DeviceType:Phone has unregistered normally.

354036: Jul  5 15:32:17 GMT: %IPPHONE-6-REG_ALARM: 10: Name=SEP001EF72826DC Load= SCCP70.8-5-2S Last=TCP-timeout

354037: Jul  5 15:32:17 GMT: %IPPHONE-6-REGISTER_NEW: ephone-87:SEP001EF72826DC IP:10.118.76.189 Socket:9 DeviceType:Phone has registered.

354038: Jul  5 15:35:18 GMT: %IPPHONE-6-UNREGISTER_NORMAL: ephone-87:SEP001EF72826DC IP:66.202.132.242 Socket:9 DeviceType:Phone has unregistered normally.

354039: Jul  5 16:25:01 GMT: %IPPHONE-6-REGISTER_NEW: ephone-150:SEP001EBE908B33 IP:10.118.77.21 Socket:5 DeviceType:Phone has registered.

354040: Jul  5 16:25:01 GMT: %IPPHONE-6-REG_ALARM: 10: Name=SEP001EBE908B33 Load= SCCP70.8-5-2S Last=TCP-timeout

354041: Jul  5 16:28:02 GMT: %IPPHONE-6-UNREGISTER_NORMAL: ephone-150:SEP001EBE908B33 IP:66.202.132.242 Socket:5 DeviceType:Phone has unregistered normally.

354042: Jul  5 18:33:03 GMT: %SEC_LOGIN-5-LOGIN_SUCCESS: Login Success [user: d.estalilla] [Source: 90.152.3.38] [localport: 23] at 18:33:03 GMT Thu Jul 5 2012

7672-23-1-RTR01#show clock

18:54:06.184 GMT Thu Jul 5 2012

7672-23-1-RTR01#

Hope you guys can help me on this issue. Thanks in advance!

1 REPLY
Cisco Employee

Some IP Phones keeps registering to SRST

If the phones are registering with SRST, then that means the phones are loosing connectivity to the CUCM.   This connection is TCP between the phone and CUCM.  You need to figure out what is happening to those TCP connections.   Make sure you have a correct QoS configuration in your network to ensure the phone signaling is prioritized correctly. 

4421
Views
0
Helpful
1
Replies
CreatePlease login to create content