<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-7" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000066">
<font size="-1"><font face="Trebuchet MS">Hi Thorsten,<br>
we are running Cisco Unified Communications Manager Express 7.0(1) on a
2811<br>
Here are the logs of the CUCME side:<br>
<br>
Jun 19 10:41:33: %IPPHONE-6-REG_ALARM: 25: Name=SEP001FCAE9332E Load=
SCCP11.8-5-2S <b>Last=Initialized</b><br>
Jun 19 10:41:33: %IPPHONE-6-UNREGISTER_ABNORMAL:
ephone-20:SEP001FCAE9332E IP:10.43.3.250 Socket:20 DeviceType:Phone has
unregistered abnormally.<br>
Jun 19 10:41:33: %IPPHONE-6-REGISTER: ephone-20:SEP001FCAE9332E
IP:10.43.3.250 Socket:24 DeviceType:Phone has registered.<br>
Jun 19 11:35:10: %IPPHONE-6-REG_ALARM: 25: Name=SEP001FCAE9332E Load=
SCCP11.8-5-2S <b>Last=Initialized</b><br>
Jun 19 11:35:10: %IPPHONE-6-UNREGISTER_ABNORMAL:
ephone-20:SEP001FCAE9332E IP:10.43.3.250 Socket:24 DeviceType:Phone has
unregistered abnormally.<br>
Jun 19 11:35:10: %IPPHONE-6-REGISTER: ephone-20:SEP001FCAE9332E
IP:10.43.3.250 Socket:13 DeviceType:Phone has registered.<br>
JJun 19 12:28:56: %IPPHONE-6-REG_ALARM: 25: Name=SEP001FCAE9332E Load=
SCCP11.8-5-2S <b>Last=Initialized</b><br>
Jun 19 12:28:56: %IPPHONE-6-UNREGISTER_ABNORMAL:
ephone-20:SEP001FCAE9332E IP:10.43.3.250 Socket:13 DeviceType:Phone has
unregistered abnormally.<br>
Jun 19 12:28:56: %IPPHONE-6-REGISTER: ephone-20:SEP001FCAE9332E
IP:10.43.3.250 Socket:24 DeviceType:Phone has registered.<br>
<br>
These 3 lines occur every 54 minutes (for days now!)<br>
<br>
here is what i see for the 2 remote phones <br>
<br>
2811voicegw#sh ephone remote <br>
ephone-20[19] Mac:001F.CAE9.332E TCP socket:[8] activeLine:0 REGISTERED
in SCCP ver 17/9<br>
mediaActive:0 offhook:0 ringing:0 reset:0 reset_sent:0 paging 0 debug:0
caps:9 <br>
IP:10.43.3.250 20737 7911 keepalive <b>31</b> max_line 1<br>
button 1: dn 22 number 14333 CH1 IDLE CH2 IDLE <br>
Preferred Codec: g711ulaw <br>
<br>
ephone-23[22] Mac:0017.0ED3.F3D9 TCP socket:[6] activeLine:0 REGISTERED
in SCCP ver 11/9<br>
mediaActive:0 offhook:0 ringing:0 reset:0 reset_sent:0 paging 0 debug:0
caps:8 <br>
IP:10.43.3.17 52354 Telecaster 7940 keepalive <b>4903</b> max_line 2<br>
button 1: dn 20 number 14332 CH1 IDLE CH2 IDLE <br>
Preferred Codec: g711ulaw <br>
<br>
As you can see, 7940 has no problem getting unregistered.<br>
<br>
2811voicegw#sh ephone phone-load <br>
DeviceName CurrentPhoneload PreviousPhoneload
LastReset <br>
=====================================================================<br>
SEP00170ED3F3D9 8.0(5.0) 8.0(5.0)
CM-ICMP-Unreach<br>
SEP001FCAE9332E SCCP11.8-5-2S SCCP11.8-5-2S
Initialized <br>
2811voicegw#<br>
<br>
I will try and get the device logs but i don't know what the can tell
me.<br>
TAC is searching it for a month (case opened on 18th of May 2009)<br>
<br>
</font></font>Thanks<br>
Anthony<br>
<br>
<a class="moz-txt-link-abbreviated" href="mailto:Thorsten.Mayr@barclayscapital.com">Thorsten.Mayr@barclayscapital.com</a> wrote:
<blockquote
cite="mid:568BC086983B9544993FA5104CF68E1A08C6559E@LDNPCMEU304VEUA.INTRANET.BARCAPINT.COM"
type="cite">
<meta http-equiv="Content-Type" content="text/html; ">
<meta name="Generator" content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"Trebuchet MS";
panose-1:2 11 6 3 2 2 2 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";
color:#000066;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page Section1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="Section1">
<p class="MsoNormal"><span
style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);">The
first thing I would look at is the reason code of the
reset? (to be found in the syslog of the subscriber the phone is
registered to)<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);">I
assume TAC has been through the syslog as well as SDI/SDL of
ccm traces already?<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);">To
name a few reason codes:<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);">6=
connectivity error<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);">9=
callmanager reset<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);">8=
device initiated reset<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);">(unless
they changed in 7.x)<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);">Also
grab the phone logs of the phone. The phone logs are rather
“interesting” to read and interpret sometimes to say the least …<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);"><o:p> </o:p></span></p>
<div>
<div
style="border-style: solid none none; border-color: rgb(181, 196, 223) -moz-use-text-color -moz-use-text-color; border-width: 1pt medium medium; padding: 3pt 0cm 0cm;">
<p class="MsoNormal"><b><span
style="font-size: 10pt; font-family: "Tahoma","sans-serif"; color: windowtext;"
lang="EN-US">From:</span></b><span
style="font-size: 10pt; font-family: "Tahoma","sans-serif"; color: windowtext;"
lang="EN-US">
<a class="moz-txt-link-abbreviated" href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a>
[<a class="moz-txt-link-freetext" href="mailto:cisco-voip-bounces@puck.nether.net">mailto:cisco-voip-bounces@puck.nether.net</a>] <b>On
Behalf Of </b>Anthony Kouloglou<br>
<b>Sent:</b> Friday, June 19, 2009 8:54 AM<br>
<b>To:</b> Ryan Ratliff<br>
<b>Cc:</b> <a class="moz-txt-link-abbreviated" href="mailto:cisco-voip@puck-nether.net">cisco-voip@puck-nether.net</a><br>
<b>Subject:</b> Re: [cisco-voip] remote 7911 resets every 46 minutes
in CUCME
7.0(1)<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span
style="font-size: 10pt; font-family: "Trebuchet MS","sans-serif";">Hi
All,<br>
i am getting back on this because i think i 'll go crazy!<br>
I have this case running over a TAC and they can't find anything!.<br>
I have upgraded these two phones 3 times; last time was to the latest
firmware.<br>
1. with the first firmware they were resetting every 46 minutes<br>
2. with the second firmware they were resetting every 42 minutes<br>
3. with the latest firmware they were resetting every 54 minutes!<br>
<br>
<br>
And it is so precise!!<br>
In the same LAN, 7940 do not get resetted (i can see them registered
for a day
or more!)<br>
The 2 7911, tested on any other site, DO NOT get unregistered!<br>
TAC has asked for captures from the switches but there seem to be no
problem
(captured traffic from the CUCME interface and the ipphone interface).<br>
<br>
Anyone has faced something like this before?<br>
What device logs would be good to gather over the phone<br>
<br>
Thanks<br>
Anthony<br>
</span><br>
Ryan Ratliff wrote: <o:p></o:p></p>
<p class="MsoNormal">I don't know what that error means I'm afraid. <br>
<br>
-Ryan <br>
<br>
On May 18, 2009, at 11:24 AM, Anthony Kouloglou wrote: <br>
<br>
Hi Ryan, <br>
what is the possibility that both phones have the same problem? <br>
I just bought only 2 of these for the remote site so i can't really
tell if
another one has the same problems? <br>
What is this error that i have enboldened and mark with red? <br>
<br>
Thanks <br>
Akoul <br>
<br>
Ryan Ratliff wrote: <br>
<br>
<o:p></o:p></p>
<p class="MsoNormal"><br>
May 18 17:17:41: %IPPHONE-6-REG_ALARM: 25: Name=SEP001FCAE9332E Load=
SCCP11.8-3-3S Last=Initialized <br>
<br>
This means the phone either crashed or lost power. You may need to
get some eyes on these phones or try and get logs from the phone itself
to get
more details. <br>
<br>
-Ryan <br>
<br>
On May 18, 2009, at 11:00 AM, Anthony Kouloglou wrote: <br>
<br>
Hi Ryan, <br>
i have also opened a TAC for this but from my experience, cisco-voip
list is
much more quicker!! <br>
Here is a debugging that they have told me to do. <br>
<br>
May 18 17:17:38: socket 10 fatal error 254! can't read msg header with
size -1,
fd 10 phone tag 20 device name SEP001FCAE9332E state 1 keepalive 74 <br>
May 18 17:17:41: New Skinny socket accepted [1] from 0, sub 1 (23
active) <br>
May 18 17:17:41: sin_family 2, sin_port 50219, in_addr 10.43.3.17 <br>
May 18 17:17:41: skinny_add_socket 1 10.43.3.17 50219 <br>
May 18 17:17:41: %IPPHONE-6-REG_ALARM: 25: Name=SEP001FCAE9332E Load=
SCCP11.8-3-3S Last=Initialized <br>
May 18 17:17:41: <br>
Skinny StationAlarmMessage on socket [20] 10.43.3.17 SEP001FCAE9332E <br>
May 18 17:17:41: severityInformational p1=0 [0x0] p2=0 [0x0] <br>
May 18 17:17:41: 25: Name=SEP001FCAE9332E Load= SCCP11.8-3-3S
Last=Initialized <br>
May 18 17:17:41: ephone-(20)[20] StationRegisterMessage (19/21/37) from
10.43.3.17 <br>
May 18 17:17:41: ephone-(20)[20] Register StationIdentifier DeviceName
SEP001FCAE9332E <br>
May 18 17:17:41: ephone-(20)[20] StationIdentifier Instance 0
deviceType 307 <br>
May 18 17:17:41: ephone-20[19/10]:stationIpAddr 10.43.3.17 <br>
May 18 17:17:41: ephone-20[19/10][SEP001FCAE9332E]:maxStreams 5 <br>
May 18 17:17:41: ephone-20[19/10][SEP001FCAE9332E]:From Phone raw
protocol Ver
0x8570000C <br>
May 18 17:17:41: ephone-20[19/10][SEP001FCAE9332E]:protocol Ver
0x8570000C <br>
May 18 17:17:41: ephone-20[19/10][SEP001FCAE9332E]:phone-size 13216
dn-size 784
<br>
May 18 17:17:41: ephone-(20) Allow any Skinny Server IP address
192.168.101.1 <br>
May 18 17:17:41: ephone-20[19/10][SEP001FCAE9332E]:Found entry 19 for
001FCAE9332E <br>
May 18 17:17:41: ephone-20[19/10][SEP001FCAE9332E]:socket change 10 to
20 <br>
May 18 17:17:41: ephone-20[19/10][SEP001FCAE9332E]:DisAssociate: Closed
socket
10 while REGISTERED <br>
May 18 17:17:41: ephone-20[19/10][SEP001FCAE9332E]: DN out-of-service
for DN 20
chan 1 <br>
May 18 17:17:41: ephone-20[19/10][SEP001FCAE9332E]: DN out-of-service
for DN 20
chan 2 <br>
May 18 17:17:41: Bring down DN 20 chan 1 (14332) with the following
traceback
-Traceback= 0x40CB2104 0x40CB26FC 0x40CB51CC 0x40CE63A0 0x40CE6DA0
0x40CE9074
0x40CA0FCC <br>
May 18 17:17:41: Skinny DN 20 chan 1 state change to DOWN <br>
May 18 17:17:41: Bring down DN 20 chan 2 (14332) with the following
traceback
-Traceback= 0x40CB2104 0x40CB26FC 0x40CB51CC 0x40CE63A0 0x40CE6DA0
0x40CE9074
0x40CA0FCC <br>
May 18 17:17:41: Skinny DN 20 chan 2 state change to DOWN <br>
May 18 17:17:41: %IPPHONE-6-UNREGISTER_ABNORMAL:
ephone-20:SEP001FCAE9332E
IP:10.43.3.17 Socket:10 DeviceType:Phone has unregistered abnormally. <br>
May 18 17:17:41: ephone-20[19/-1][SEP001FCAE9332E]:FAILED: CLOSED old
socket -1
<br>
May 18 17:17:41: ephone-20[19/20][SEP001FCAE9332E]:phone
SEP001FCAE9332E
re-associate OK on socket [20] <br>
May 18 17:17:41: %IPPHONE-6-REGISTER: ephone-20:SEP001FCAE9332E
IP:10.43.3.17
Socket:20 DeviceType:Phone has registered. <br>
May 18 17:17:41: Phone 19 socket 20 <br>
May 18 17:17:41: Skinny Local IP address = 192.168.101.1 on port 2000 <br>
<br>
May 18 17:17:41: Skinny Phone IP address = 10.43.3.17 50219 <br>
May 18 17:17:41: ephone-20 If FastEthernet0/0 ETHERNET 10.43.3.17 via
192.168.101.254 <br>
May 18 17:17:41: ephone-20[19/20][SEP001FCAE9332E]:Signal protocol ver
9 to
phone with ver 12 <br>
May 18 17:17:41: ephone-20[19/20][SEP001FCAE9332E]:Date Format D/M/Y <br>
May 18 17:17:41: ephone-20[19/20]:RegisterAck sent to sockettype ephone
socket
20: keepalive period 60 use sccp-version 9 <br>
May 18 17:17:41: ephone-20[19/20]:CapabilitiesReq sent <br>
May 18 17:17:41: ephone-20[19/20][SEP001FCAE9332E]:Skinny IP port 3500
set for
socket [20] <br>
May 18 17:17:41: ephone-20[19/20]:ButtonTemplateReqMessage <br>
May 18 17:17:41: ephone-20[19/20]:ButtonTemplateReqMessage waiting for
Caps <br>
May 18 17:17:41: ephone-20[19/20]:StationSoftKeyTemplateReqMessage <br>
May 18 17:17:41: ephone-20[19/20]:StationSoftKeyTemplateResMessage <br>
May 18 17:17:41: ephone-20[19/20]:StationSoftKeySetReqMessage <br>
May 18 17:17:41: ephone-20[19/20]:StationSoftKeySetResMessage <br>
May 18 17:17:41: ephone-20[19/20]:StationConfigStatReqMessage <br>
May 18 17:17:41:
ephone-20[19/20][SEP001FCAE9332E]:StationConfigStatMessage
sent for device SEP001FCAE9332E (40/280) <br>
May 18 17:17:41: ephone-20[19/20]:CapabilitiesRes received <br>
May 18 17:17:41: ephone-20[19/20][SEP001FCAE9332E]:Caps list 9 <br>
WideBand_256K 40 ms, is_mtp 0 <br>
G711Ulaw64k 40 ms, is_mtp 0 <br>
G711Alaw64k 40 ms, is_mtp 0 <br>
ILBC 60 ms, is_mtp 0 <br>
G729AnnexB 60 ms, is_mtp 0 <br>
G729AnnexAwAnnexB 60 ms, is_mtp 0 <br>
G729 60 ms, is_mtp 0 <br>
G729AnnexA 60 ms, is_mtp 0 <br>
Unrecognized Media Type 257 1 ms, is_mtp 0 <br>
<br>
May 18 17:17:41: ephone-20[19/20]:Process pending button template <br>
May 18 17:17:41: ephone-20[19/20]:ButtonTemplateReqMessage <br>
May 18 17:17:41:
ephone-20[19/20][SEP001FCAE9332E]:StationButtonTemplateReqMessage
set max presentation to 2 <br>
May 18 17:17:41: ephone-20[19/20]:CheckAutoReg <br>
May 18 17:17:41: ephone-20[19/20]:AutoReg is disabled <br>
May 18 17:17:41: ephone-20[19/20][SEP001FCAE9332E]:Setting 1 lines 4
speed-dials
on phone (max_line 1) <br>
May 18 17:17:41: ephone-20[19/20][SEP001FCAE9332E]:First Speed Dial
Button
location is 3 (0) <br>
May 18 17:17:41: ephone-20[19/20]:ButtonTemplate lines=1 speed=4
buttons=6
offset=0 <br>
May 18 17:17:41: ephone-20[19/20][SEP001FCAE9332E]:ButtonTemplate
buttonCount=6
totalButtonCount=6 buttonOffset=0 <br>
May 18 17:17:41: ephone-20[19/20][SEP001FCAE9332E]:Configured 4 speed
dial
buttons <br>
May 18 17:17:41: ephone-20[19/20]:MediaPathEventMessage <br>
May 18 17:17:41: ephone-20[19/20]:MediaPathEventMessage <br>
May 18 17:17:41:
ephone-20[19/20][SEP001FCAE9332E]:StationLineStatReqMessage
from ephone line 1 <br>
May 18 17:17:41: ephone-20[19/20]:StationLineStatReqMessage ephone line
1 DN 20
= 14332 desc = 14332 label = <br>
May 18 17:17:41:
ephone-20[19/20][SEP001FCAE9332E]:StationLineStatResMessage
sent to ephone (1 of 1) <br>
May 18 17:17:41: ephone-20[19/20]:SkinnyCompleteRegistration <br>
May 18 17:17:41: ephone-20[19/20][SEP001FCAE9332E]: DN in-service for
DN 20
chan 1 <br>
May 18 17:17:41: ephone-20[19/20][SEP001FCAE9332E]: DN in-service for
DN 20
chan 2 <br>
May 18 17:17:41: Skinny DN 20 chan 1 state change to UP <br>
May 18 17:17:41: Skinny DN 20 chan 2 state change to UP <br>
May 18 17:17:41:
ephone-20[19/20][SEP001FCAE9332E]:StationForwardStatReqMessage
line 1 from ephone <br>
May 18 17:17:41: Skinny StationForwardStatMessage line 1 sent on ephone
socket
[20] for ephone-20 <br>
May 18 17:17:41: activeForward 0 AllActive 0 BusyActive 0
NoAnswerActive 0 <br>
May 18 17:17:41:
ephone-20[19/20][SEP001FCAE9332E]:StationSpeedDialStatReqMessage speed
1 <br>
May 18 17:17:41: ephone-20[19/20][SEP001FCAE9332E]:No speed-dial set 1 <br>
May 18 17:17:41: ephone-20[19/20]:StationSpeedDialStatMessage sent <br>
May 18 17:17:41:
ephone-20[19/20][SEP001FCAE9332E]:StationSpeedDialStatReqMessage speed
2 <br>
May 18 17:17:41: ephone-20[19/20][SEP001FCAE9332E]:No speed-dial set 2 <br>
May 18 17:17:41: ephone-20[19/20]:StationSpeedDialStatMessage sent <br>
May 18 17:17:41:
ephone-20[19/20][SEP001FCAE9332E]:StationSpeedDialStatReqMessage speed
3 <br>
May 18 17:17:41: ephone-20[19/20][SEP001FCAE9332E]:No speed-dial set 3 <br>
May 18 17:17:41: ephone-20[19/20]:StationSpeedDialStatMessage sent <br>
May 18 17:17:41:
ephone-20[19/20][SEP001FCAE9332E]:StationSpeedDialStatReqMessage speed
4 <br>
May 18 17:17:41: ephone-20[19/20][SEP001FCAE9332E]:No speed-dial set 4 <br>
May 18 17:17:41: ephone-20[19/20]:StationSpeedDialStatMessage sent <br>
May 18 17:17:41: ephone-20[19/20][SEP001FCAE9332E]:Skinny Available
Lines 1 set
for socket [20] <br>
May 18 17:17:41: ephone-20[19/20]:Already done
SkinnyCompleteRegistration <br>
May 18 17:17:41: STANDBY Keepalive socket 26 nonregistered ephone {3}
192.168.101.28 1026 <br>
<br>
Ryan Ratliff wrote: <br>
<br>
<o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom: 12pt;"><br>
When the phone re-registers to CCME I believe the alarm messages gets
printed
to the log/console. It should have a string like "last=" in
it. This is the reason the phone last unregistered and will be very
useful. <br>
<br>
-Ryan <br>
<br>
On May 18, 2009, at 7:01 AM, Anthony Kouloglou wrote: <br>
<br>
Hi, in a CUCME 7.0(1) running on 2811 with 12.4.22.T1, in the local
site all
phones have no problem. <br>
But, in a remote site, i registered 2 7911 and i noticed that they
unregister
and reregister every 46 minutes!! <br>
Not 45 not 47! <br>
I upgraded them to SCCP11.8-3-3S and they are doing the same thing. <br>
There is no connectivity problem with the remote site. I registered a
7940 at
the remote site and it never reseted!!. <br>
Also, the phone 7911 reseted even in an active call (it was at th 46th
minute) <br>
<br>
Has anyone faced that before? <br>
<br>
Thanks <br>
Anthony <br>
_______________________________________________ <br>
cisco-voip mailing list <br>
<a moz-do-not-send="true" href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>
<br>
<a moz-do-not-send="true"
href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a>
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<font face="Arial" size="2">
</font>
<p class="MsoNormal" style="margin: 0in 0in 0pt;"><span
style="font-size: 11pt;"><font face="Arial" size="2"><font
face="Times New Roman">_______________________________________________<o:p></o:p></font></font></span></p>
<p class="MsoNormal" style="margin: 0in 0in 0pt;"><span
style="font-size: 11pt;"><o:p><font face="Arial" size="2"><font
face="Times New Roman"> </font></font></o:p></span></p>
<p class="MsoNormal" style="margin: 0in 0in 0pt;"><span
style="font-size: 11pt;"><font face="Arial" size="2"><font
face="Times New Roman">This e-mail may contain information that is
confidential, privileged or otherwise protected from disclosure. If you
are not an intended recipient of this e-mail, do not duplicate or
redistribute it by any means. Please delete it and any attachments and
notify the sender that you have received it in error. Unless
specifically indicated, this e-mail is not an offer to buy or sell or a
solicitation to buy or sell any securities, investment products or
other financial product or service, an official confirmation of any
transaction, or an official statement of Barclays. Any views or
opinions presented are solely those of the author and do not
necessarily represent those of Barclays. This e-mail is subject to
terms available at the following link: </font></font></span><span
style="font-size: 10pt; color: navy; font-family: Arial;" lang="EN-GB"><font
face="Arial" size="2"><a moz-do-not-send="true"
href="http://www.barcap.com/emaildisclaimer">www.barcap.com/emaildisclaimer</a>.
</font></span><span style="font-size: 11pt;"><font face="Arial"
size="2"><font face="Times New Roman">By messaging with Barclays you
consent to the foregoing.<span style=""> </span>Barclays Capital is
the investment banking division of Barclays Bank PLC, a company
registered in <st1:place w:st="on"><st1:country-region w:st="on">England</st1:country-region></st1:place>
(number 1026167) with its registered office at <st1:address w:st="on"><st1:Street
w:st="on">1 Churchill Place</st1:Street>, <st1:City w:st="on">London</st1:City>,
<st1:PostalCode w:st="on">E14 5HP</st1:PostalCode></st1:address>.<span
style=""> </span>This email may relate to or be sent from other
members of the Barclays Group.<i style=""><o:p></o:p></i></font></font></span></p>
<p class="MsoNormal" style="margin: 0in 0in 0pt;"><span
style="font-size: 11pt;"><font face="Arial" size="2"><font
face="Times New Roman">_______________________________________________</font></font></span></p>
</blockquote>
</body>
</html>