<div dir="ltr">Florian,<div><br></div><div>That's good information but I don't believe it applies here. This would be after the phone has its config file and is in the process of registering via SCCP. I think the Station Capabilities Response is what is getting lost here. I had the same issue trying to register my 7861s on my lab cluster. I had to lower the MTU in CUCM in order for the TCP MSS to get updated to a lower value.</div>
<div><br></div><div>Brian</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Jun 3, 2014 at 2:02 PM, Florian Kroessbacher <span dir="ltr"><<a href="mailto:florian.kroessbacher@gmail.com" target="_blank">florian.kroessbacher@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class=""><div dir="ltr"><div class="gmail_default" style="font-family:verdana,sans-serif"><div class="gmail_default" style="font-size:13px">
Hy</div><div class="gmail_default" style="font-size:13px"><br></div><div class="gmail_default" style="font-size:13px">
8.3.3 does everything through udp tftp</div><div class="gmail_default" style="font-size:13px">9.3. does the new method over http 6970 (so the size is greater than the udp 576 Bytes)</div><div class="gmail_default" style="font-size:13px">
<br></div><div class="gmail_default" style="font-size:13px">look here</div><div class="gmail_default" style="font-family:arial,sans-serif;font-size:13px"><font face="verdana, sans-serif"><a href="http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cuipph/7900_series/firmware/9_3_1/release_notes/P790_BK_RF1DAED3_00_rn-9_3_1-7900-series/P790_BK_RF1DAED3_00_rn-9_3_1-7900-series_chapter_00.html#P790_RF_H0DA5A91_00" target="_blank">http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cuipph/7900_series/firmware/9_3_1/release_notes/P790_BK_RF1DAED3_00_rn-9_3_1-7900-series/P790_BK_RF1DAED3_00_rn-9_3_1-7900-series_chapter_00.html#P790_RF_H0DA5A91_00</a></font></div>
</div></div></div><div class="gmail_extra"><br clear="all"><div>Florian Kroessbacher<br><br>gmail: <a href="mailto:florian.kroessbacher@gmail.com" target="_blank">florian.kroessbacher@gmail.com</a><br></div>
<br><br><div class="gmail_quote"><div class="">2014-06-03 19:38 GMT+02:00 Brian Meade <span dir="ltr"><<a href="mailto:bmeade90@vt.edu" target="_blank">bmeade90@vt.edu</a>></span>:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">You can do the capture on the CUCM side via CLI but that doesn't help you prove you lost a packet since you'll also need from the phone side via Span To PC:<div><div class="h5"><div><br></div><div>
utils network capture eth0 size all count 100000 file 7970testreg</div>
<div>Press Ctr+c to end the capture after the reject.</div><div><br></div><div>You can get the capture from RTMT via Trace&Log Central->Collect Files->Packet Capture Logs (on 2nd page).</div><div>You can also use SFTP:</div>
<div>file get activelog platform/cli/7970testreg.cap</div></div></div></div><div><div class="h5"><div><div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Jun 3, 2014 at 1:29 PM, Mike King <span dir="ltr"><<a href="mailto:me@mpking.com" target="_blank">me@mpking.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hmm..<div><br></div><div>Before I bust out my span sessions, is there a way to packet capture from the CUCM / Phone?</div>
</div><div><div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Jun 3, 2014 at 1:22 PM, Brian Meade <span dir="ltr"><<a href="mailto:bmeade90@vt.edu" target="_blank">bmeade90@vt.edu</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Sounds like an MTU issue to me based on those logs. Get captures from the phone side and CUCM.</div><div>
<div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Jun 3, 2014 at 1:04 PM, Mike King <span dir="ltr"><<a href="mailto:me@mpking.com" target="_blank">me@mpking.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Now I'm more confused.<div>Did I pull the right Traces? </div><div><br></div><div><div><ServiceName name="Cisco CallManager"></div>
<div><ServiceName name="Cisco Tftp"><br>
</div><div><br></div></div><div>This is from the Callmanager trace: (attached is the whole log, device MAC is 0019AAAA3EB6)</div><div><br></div><div><div>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</div>
<div>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,</div>
<div>00268821.004 |12:51:14.197 |AppInfo |StationD: (0001646) RegisterReject text=''.</div><div>00268822.000 |12:51:14.198 |AppInfo |-->RISCMAccess::DeviceTransientConnection(...)</div><div>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</div>
<div>00268824.000 |12:51:14.198 |AppInfo |DebugMsg deviceName : SEP0019AAAA3EB6, DeviceType : 119, risClass: 1</div><div>00268825.000 |12:51:14.198 |AppInfo |<--RISCMAccess::DeviceTransientConnection(...)</div></div>
</div><div><div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Jun 3, 2014 at 11:57 AM, Ryan Ratliff (rratliff) <span dir="ltr"><<a href="mailto:rratliff@cisco.com" target="_blank">rratliff@cisco.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>> Any Idea's why the phones are being rejected?<br>
<br>
</div>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.<br>
<br>
-Ryan<br>
<div><div><br>
On Jun 3, 2014, at 11:08 AM, Mike King <<a href="mailto:me@mpking.com" target="_blank">me@mpking.com</a>> wrote:<br>
<br>
We just purchased a BE6K to setup a lab.<br>
<br>
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)<br>
<br>
We have a couple of very phones we were going to recycle.<br>
<br>
Right now we have two, a 7970, and a 7971.<br>
<br>
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))<br>
<br>
Running 8.3.3, they were able to register, and function.<br>
<br>
I pushed the firmware up to 9.3(1SR3.1S)<br>
<br>
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.<br>
<br>
Attached is one of the phone logs. Both phone's are showing the same behavior.<br>
<br>
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: "<br>
<br>
Any Idea's why the phones are being rejected?<br>
</div></div><log199.log>_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
<br>
</blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
<br></blockquote></div><br></div>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
<br></div></div></blockquote></div><br></div>
</blockquote></div><br></div>