<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.3157" name=GENERATOR></HEAD>
<BODY text=#000000 bgColor=#ffffff>
<DIV dir=ltr align=left><SPAN class=031364620-31012008><FONT face=Arial
color=#0000ff size=2>It's very reproduceable if we don't wait to
dial.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=031364620-31012008><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=031364620-31012008><FONT face=Arial
color=#0000ff size=2>If we attempt to dial within a minute of the device saying
it's registered, we can cause this error to occur. If we wait a longer
period of time, the dial succeeds.</FONT></SPAN></DIV><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> Wes Sisk [mailto:wsisk@cisco.com]
<BR><B>Sent:</B> Thursday, January 31, 2008 2:43 PM<BR><B>To:</B> Philip
Walenta<BR><B>Cc:</B> cisco-voip@puck.nether.net<BR><B>Subject:</B> Re:
[cisco-voip] Has anyone ever seen this message in a CCM trace
file<BR></FONT><BR></DIV>
<DIV></DIV>Phil,<BR><BR>In SDL traces looks like your device is not properly
registered. When device sent StationTemplateReq CM tried to do a database
lookup but the database PID appears invalid.<BR><BR>004186533| 2008/01/31
09:54:43.994| 001| SdlSig |
DbStationButtonTemplateReq
|
initialized
|
Db(1,100,186,1)
|
StationD(1,100,66,47)
| (1,100,65,1).17914-(SEP00e0db071acb:10.64.1.255)| [T:LP - HP: 0, NP: 0, LP: 0,
VLP: 0, LZP: 0 DBP: 0]<BR>004186534| 2008/01/31 09:54:43.994| 001| SdlExcept |
DbStationButtonTemplateErr
|
restart0
|
StationD(1,100,66,47)
|
|
| Error: FSM_NO_TRANSITION_DEFINED Description: A transition is not defined for
the input signal. Check state machine definition in
initStateMachine().<BR><BR><BR>Is this reproducible?<BR><BR>/Wes<BR><BR>Philip
Walenta wrote:
<BLOCKQUOTE cite=mid:000001c86442$848f92c0$0232a8c0@walentawk1 type="cite">
<META content="MSHTML 6.00.2900.3157" name=GENERATOR>
<DIV dir=ltr align=left><SPAN class=921554419-31012008><FONT face=Arial
color=#0000ff size=2>Case number is 607838861.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=921554419-31012008></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=921554419-31012008><FONT face=Arial
color=#0000ff size=2>In the scenario where we received this message we had no
active calls. Failover, then the ability to make a call was being
tested. So:</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=921554419-31012008></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=921554419-31012008><FONT face=Arial
color=#0000ff size=2>(device starts out on-hook with no active
calls)</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=921554419-31012008><FONT face=Arial
color=#0000ff size=2>1. Pulled network plug on primary CCM
server</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=921554419-31012008><FONT face=Arial
color=#0000ff size=2>2. Waited for device to report primary CCM was
down</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=921554419-31012008><FONT face=Arial
color=#0000ff size=2>3. Device completed re-home to secondary subscriber
and reported itself as being in-service (CCM also said device was
registered)</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=921554419-31012008><FONT face=Arial
color=#0000ff size=2>4. Attempted to make a call after the re-home and
got that error message the moment the dial string was
completed.</FONT></SPAN></DIV>
<DIV> </DIV>
<DIV><SPAN class=921554419-31012008></SPAN><FONT face=Arial><FONT
color=#0000ff><FONT size=2>C<SPAN class=921554419-31012008>UCM version is
6.0.1.1000-37 running on Cisco 7835 and 7845 servers (this is the platform
TekVizion uses for Cisco certification).</SPAN></FONT></FONT></FONT></DIV>
<DIV><FONT face=Arial><FONT color=#0000ff><FONT size=2><SPAN
class=921554419-31012008></SPAN></FONT></FONT></FONT> </DIV>
<DIV><FONT face=Arial><FONT color=#0000ff><FONT size=2><SPAN
class=921554419-31012008>After some futher testing and a subscriber reboot, we
found we could complete the call if we waited several minutes. If we try
right after re-registration we still get that
error.</SPAN></FONT></FONT></FONT></DIV>
<DIV><BR></DIV>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> Wes Sisk [<A class=moz-txt-link-freetext
href="mailto:wsisk@cisco.com">mailto:wsisk@cisco.com</A>] <BR><B>Sent:</B>
Thursday, January 31, 2008 1:40 PM<BR><B>To:</B> Philip Walenta<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] Has anyone ever seen this message in a CCM trace
file<BR></FONT><BR></DIV>Case number?<BR><BR>LineCdpc most likely believes 4
calls are already active on the line. If this is a shared line and 4
calls were active before failover then when the phone reregisters it will not
show the 4 active calls, it will simply refuse to go offhook and give you this
message. This goes way back to:<BR>CSCed43618 Line status out of sync
with shared line after reboot<BR><BR>/Wes<BR><BR>Philip Walenta wrote:
<BLOCKQUOTE cite=mid:002101c86439$75f58fc0$0232a8c0@walentawk1 type="cite">
<META content="MSHTML 6.00.2900.3157" name=GENERATOR>
<DIV dir=ltr align=left><SPAN class=984104418-31012008><FONT face=Arial
color=#0000ff size=2>Ok, I read the bug. It applies to CCM
4.0.1. I'm seeing this on a 6.0 system where the line settings are 4
max calls/1 busy trigger.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=984104418-31012008></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=984104418-31012008><FONT face=Arial
color=#0000ff size=2>The error occurs after the device fails from one server
to another in the cluser and attempt to dial after
re-homing.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=984104418-31012008></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=984104418-31012008><FONT face=Arial
color=#0000ff size=2>I do have a TAC case open on it
now.</FONT></SPAN></DIV><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> Wes Sisk [<A
class=moz-txt-link-freetext href="mailto:wsisk@cisco.com"
moz-do-not-send="true">mailto:wsisk@cisco.com</A>] <BR><B>Sent:</B>
Thursday, January 31, 2008 12:27 PM<BR><B>To:</B> Philip
Walenta<BR><B>Cc:</B> <A class=moz-txt-link-abbreviated
href="mailto:cisco-voip@puck.nether.net"
moz-do-not-send="true">cisco-voip@puck.nether.net</A><BR><B>Subject:</B> Re:
[cisco-voip] Has anyone ever seen this message in a CCM trace
file<BR></FONT><BR></DIV>Take a look at CSCee54687. Indicates someone
attempted to initiate a new call on a line that already had 'max calls'
active.<BR><BR>/Wes<BR><BR>Philip Walenta wrote:
<BLOCKQUOTE cite=mid:022401c8638e$b0d20980$0232a8c0@walentawk1
type="cite"><META content="MSHTML 6.00.2900.3157" name=GENERATOR>
<DIV><SPAN class=203372222-30012008><FONT face=Arial size=2>"Error:
Passed Max Device Limit"</FONT></SPAN></DIV>
<DIV><SPAN class=203372222-30012008></SPAN> </DIV>
<DIV><SPAN class=203372222-30012008><FONT face=Arial
size=2>?</FONT></SPAN></DIV><PRE wrap=""><HR width="90%" SIZE=4>
_______________________________________________
cisco-voip mailing list
<A class=moz-txt-link-abbreviated href="mailto:cisco-voip@puck.nether.net" moz-do-not-send="true">cisco-voip@puck.nether.net</A>
<A class=moz-txt-link-freetext href="https://puck.nether.net/mailman/listinfo/cisco-voip" moz-do-not-send="true">https://puck.nether.net/mailman/listinfo/cisco-voip</A>
</PRE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>