For SCCP phones you want to find the TCP handle so you can see messages back and forth.
00267710.001 |12:43:13.166 |AppInfo |StationD: (0001642) Device SEP0019AAAA3EB6, --INFO-- line_register_LineRegisterRes registering line=1 and maxline=1 00267710.002 |12:43:13.166 |AppInfo |StationD: (0001642) sendCapabilitiesReq Send StationOutputRegisterAck 00267710.003 |12:43:13.166 |AppInfo |StationD: (0001642) RegisterAck keepAliveInterval=30 dateTemplate='M/D/YA' secondaryKeepAliveInterval=60. 00267710.004 |12:43:13.166 |AppInfo |StationD: (0001642) Send StationOutputCapabilitiesReq in sendCapabilitiesReq 00267710.005 |12:43:13.166 |AppInfo |StationD: (0001642) CapabilitiesReq. ... 00267834.000 |12:44:13.175 |SdlSig |StationResponseTimerType |wait_capabilities |StationD(1,100,63,1642) |SdlTimerService(1,100,3,1) |1,100,62,1.1650^*^* |[R:H-H:0,N:0,L:0,V:0,Z:0,D:0] 00267834.001 |12:44:13.175 |AppInfo |StationD: (0001642) registrationError sent StationOutputRegisterReject 00267834.002 |12:44:13.175 |AppInfo |EndPointTransientConnection - An endpoint attempted to register but did not complete registration Connecting Port:2000 Device name:SEP0019AAAA3EB6 Device IP address:10.103.5.133 Device type:119 Reason Code:27 Protocol:SCCP Device MAC address:0019AAAA3EB6 IPAddressAttributes:3 LastSignalReceived:StationResponseTimerType StationState:wait_capabilities App ID:Cisco CallManager Cluster ID:StandAloneCluster Node ID:BE6K-CUCM The reason Brian points to MTU is because the CapabilitiesRes from the phone tends to be rather large and if the phone is sending it the server isn't getting it. You can compare with the same type of messages with the phone on 8.3.3 to see what's different. -Ryan On Jun 3, 2014, at 1:04 PM, Mike King <[email protected]<mailto:[email protected]>> wrote: Now I'm more confused. Did I pull the right Traces? <ServiceName name="Cisco CallManager"> <ServiceName name="Cisco Tftp"> This is from the Callmanager trace: (attached is the whole log, device MAC is 0019AAAA3EB6) 00268821.002 |12:51:14.196 |AppInfo |EndPointTransientConnection - An endpoint attempted to register but did not complete registration Connecting Port:2000 Device name:SEP0019AAAA3EB6 Device IP address:10.103.5.133 Device type:119 Reason Code:27 Protocol:SCCP Device MAC address:0019AAAA3EB6 IPAddressAttributes:3 LastSignalReceived:StationResponseTimerType StationState:wait_capabilities App ID:Cisco CallManager Cluster ID:StandAloneCluster Node ID:BE6K-CUCM 00268821.003 |12:51:14.197 |AlarmErr |AlarmClass: CallManager, AlarmName: EndPointTransientConnection, AlarmSeverity: Error, AlarmMessage: , AlarmDescription: An endpoint attempted to register but did not complete registration, AlarmParameters: ConnectingPort:2000, DeviceName:SEP0019AAAA3EB6, IPAddress:10.103.5.133, DeviceType:119, Reason:27, Protocol:SCCP, MACAddress:0019AAAA3EB6, IPAddrAttributes:3, LastSignalReceived:StationResponseTimerType, StationState:wait_capabilities, AppID:Cisco CallManager, ClusterID:StandAloneCluster, NodeID:BE6K-CUCM, 00268821.004 |12:51:14.197 |AppInfo |StationD: (0001646) RegisterReject text=''. 00268822.000 |12:51:14.198 |AppInfo |-->RISCMAccess::DeviceTransientConnection(...) 00268823.000 |12:51:14.198 |AppInfo |Device Transient deviceName : SEP0019AAAA3EB6, IPAddress : 10.103.5.133, IPv6Address : not shown, IPv4Attribute :3, IPv6Attribute :0, Protocol : 1 00268824.000 |12:51:14.198 |AppInfo |DebugMsg deviceName : SEP0019AAAA3EB6, DeviceType : 119, risClass: 1 00268825.000 |12:51:14.198 |AppInfo |<--RISCMAccess::DeviceTransientConnection(...) On Tue, Jun 3, 2014 at 11:57 AM, Ryan Ratliff (rratliff) <[email protected]<mailto:[email protected]>> wrote: > Any Idea's why the phones are being rejected? Not from that log that I can tell. Look at the CCM traces. Obvious reasons are wrong device model in the database, not in the database at all and auto-registration is disabled, phone configured with a secure profile requiring an LSC and none is present. -Ryan On Jun 3, 2014, at 11:08 AM, Mike King <[email protected]<mailto:[email protected]>> wrote: We just purchased a BE6K to setup a lab. I've run through the setup, and have that all sorted, or so I think. (So the environment may or may not be the issue) We have a couple of very phones we were going to recycle. Right now we have two, a 7970, and a 7971. The started life phone firmware at 6.0(2). Utilizing factory defaulting off my laptop, I got them to 8.3.3. (I couldn't get them to associated with 6.0(2)) Running 8.3.3, they were able to register, and function. I pushed the firmware up to 9.3(1SR3.1S) Now none of the phones are registering. I've read the release notes, and I should be able to goto 9.3.1 from 8.3.3 directly on these phones, with no further intermediate releases. Attached is one of the phone logs. Both phone's are showing the same behavior. The phone is just sitting there with the wrong date and time in the corner, and every once and awhile will print out "Registration Rejected: " Any Idea's why the phones are being rejected? <log199.log>_______________________________________________ cisco-voip mailing list [email protected]<mailto:[email protected]> https://puck.nether.net/mailman/listinfo/cisco-voip <SDL001_100_000010.txt.gz>
_______________________________________________ cisco-voip mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-voip
