[cisco-voip] Call Waiting on 4

[Lelio Fulgenzi]

The problem with making direct changes to the SQL database is that the phone does not know the change happened. That's why it is recommended to use SOAP/AXL because that process initiates an update process to CallManager and/or the phones.

If you try changing the callforwardall of a line, you will notice nothing happens on the phone.

--------------------------------------------------------------------------------
Lelio Fulgenzi, B.A.
Network Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 
Sanity First : Number of days with fewer than
50 messages in my inbox at the end of the day:   buffer overrun
  ----- Original Message ----- 
  From: Robert Singleton 
  To: cisco-voip at puck.nether.net 
  Sent: Wednesday, May 10, 2006 10:32 AM
  Subject: Re: [cisco-voip] Call Waiting on 4



  On Wed, 2006-05-10 at 16:10 +1000, Xris Brunton wrote:
  > Hi I was wondering if anyone knows where to set a cluster wide “Busy
  > Trigger” setting in 4.1. The “How Multiple Calls Per Line Work in
  > Cisco CallManager 4.x” document hints this can be done. But I am
  > unable to find where in the CallManager to set it; can’t find any
  > instructions on the Cisco site, forums, callmanager help or the
  > callmanager its self.

  I also could not find an existing method to fix this systemwide. I could
  not even find a place to change the default, which doesn't work for our
  shared line model, either.

  > Also this may be me miss interpreting the text that states “This busy
  > trigger is database configurable, per line appearance, per cluster”;
  > though I can’t see how it could mean anything else with the per
  > cluster comment since having a line appearance that is not per cluster
  > isn’t possible.

  In our particular situation, my helpers were hardly ever changing the
  default MaxNumRings/BusyTrigger settings, so I had a fairly random
  distribution of incorrect settings. I used a database query, which one
  can do from SQL Server Enterprise Manager, to identify which lines
  needed correction. I had a 2-3 page list of specific lines that needed
  correction and started doing the changes manually. It was a tedious job,
  but not a particularly hard one.

  Since then, I've gained the SQL confidence to write such changes via SQL
  query. Beware, however, for it is trivially easy to accidentally change
  and/or delete *every* line in the database, so this may not be
  appropriate or worth the risk.

  While I use isql on my Linux workstation to do most SQL work, I
  formulated a query to use from Enterprise Manager to report what the
  MaxNumCalls and BusyTrigger settings are on most of my telephones. Now,
  since I have corrected everything to not be 4/2 as default, I had to use
  a query that would produce output. The query is included below. :)

  Robert

  ----------------------

  SELECT Device.Name, NumPlan.DNOrPattern, DeviceNumPlanMap.Display,
  DeviceNumPlanMap.MaxNumCalls, DeviceNumPlanMap.BusyTrigger,
  TypeModel.Name AS Expr1, DeviceNumPlanMap.NumPlanIndex

  FROM DeviceNumPlanMap INNER JOIN
  NumPlan ON DeviceNumPlanMap.fkNumPlan = NumPlan.pkid INNER JOIN
  Device ON DeviceNumPlanMap.fkDevice = Device.pkid INNER JOIN
  TypeModel ON Device.tkModel = TypeModel.Enum

  WHERE (DeviceNumPlanMap.MaxNumCalls = '2') AND (Device.tkModel BETWEEN
  '7' AND '8')



  _______________________________________________
  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/20060510/2f674cfe/attachment.html