[cisco-voip] Has anyone ever seen this message in a CCM trace file

[Philip Walenta]

It's very reproduceable if we don't wait to dial.
 
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.

  _____  

From: Wes Sisk [mailto:wsisk at cisco.com] 
Sent: Thursday, January 31, 2008 2:43 PM
To: Philip Walenta
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Has anyone ever seen this message in a CCM trace
file


Phil,

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.

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]
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().


Is this reproducible?

/Wes

Philip Walenta wrote: 

Case number is 607838861.
 
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:
 
(device starts out on-hook with no active calls)
1.  Pulled network plug on primary CCM server
2.  Waited for device to report primary CCM was down
3.  Device completed re-home to secondary subscriber and reported itself as
being in-service (CCM also said device was registered)
4.  Attempted to make a call after the re-home and got that error message
the moment the dial string was completed.
 
CUCM version is 6.0.1.1000-37 running on Cisco 7835 and 7845 servers (this
is the platform TekVizion uses for Cisco certification).
 
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.

  _____  

From: Wes Sisk [mailto:wsisk at cisco.com] 
Sent: Thursday, January 31, 2008 1:40 PM
To: Philip Walenta
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Has anyone ever seen this message in a CCM trace
file


Case number?

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:
CSCed43618 Line status out of sync with shared line after reboot

/Wes

Philip Walenta wrote: 

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.
 
The error occurs after the device fails from one server to another in the
cluser and attempt to dial after re-homing.
 
I do have a TAC case open on it now.

  _____  

From: Wes Sisk [mailto:wsisk at cisco.com] 
Sent: Thursday, January 31, 2008 12:27 PM
To: Philip Walenta
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Has anyone ever seen this message in a CCM trace
file


Take a look at CSCee54687.  Indicates someone attempted to initiate a new
call on a line that already had 'max calls' active.

/Wes

Philip Walenta wrote: 

"Error:  Passed Max Device Limit"
 
?


  _____  


_______________________________________________

cisco-voip mailing list

cisco-voip at puck.nether.net

https://puck.nether.net/mailman/listinfo/cisco-voip

  

-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20080131/cbb1d97d/attachment-0001.html