[cisco-voip] 4.2 vs. 5.1

[Lelio Fulgenzi]

I think that was the general consensus a while back, that was our understanding as well. I think we have to accept that 4.2 is only going to be included in 6.0 which is now what they are saying. 

Could be that it even gets delayed to 7.0 which is rumored to be asterisk based running on QNX.

Just joking.

--------------------------------------------------------------------------------
Lelio Fulgenzi, B.A.
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 
"I can eat fifty eggs." "Nobody can eat fifty eggs."
  ----- Original Message ----- 
  From: Jonathan Charles 
  To: Ryan Ratliff 
  Cc: cisco-voip at puck.nether.net 
  Sent: Tuesday, October 24, 2006 1:05 PM
  Subject: Re: [cisco-voip] 4.2 vs. 5.1


  According to the tech brief from Cisco, the plan was that 5.0 and 4.1 would be feature equivelent and 5.1 and 4.2 would be feature equivelent...

  Did they change it again?




  Jonathan


  On 10/24/06, Ryan Ratliff <rratliff at cisco.com> wrote:
    The features from 4.2 and 5.x will not synch up until 6.0.

    -Ryan

    On Oct 24, 2006, at 9:07 AM, Andre Beck wrote:

    Hi,

    evaluating 5.0 I found it finally has one of the two features we were
    calling for at least for three years: busy lamps coupled to speed dials. 
    The other thing we desperately long for is Login/Out to Hunt (Line)
    Groups,
    which is supposedly in 4.2. The newest kid on the block is 5.1, which
    does
    have BFL-SDs from 5.0, but doesn't seem to have Hunt Login. 

    Please tell me the latter isn't true, as our local hack to simulate
    login
    to line groups (Ext Mob with a second line) is crappy WRT busy
    feedback to
    callers who happen to call the primary line while we already talk on the 
    secondary one. I've tried to solve the problem with partitions and
    CSS but
    the way CCM does static digit analysis since 4.0 breaks this, either
    (having
    the same number in two different partitions allows for the line group 
    to only
    route to one of them, but you cannot define a CSS that always reaches
    the DN,
    as either sequence of partitions will busy out on those DNs that
    happen to
    be inactive in the first one).

    Argh. 

    --
                       The _S_anta _C_laus _O_peration
       or "how to turn a complete illusion into a neverending money source"

    -> Andre Beck    +++ ABP-RIPE +++    IBH Prof. Dr. Horn GmbH, Dresden <- 
    _______________________________________________
    cisco-voip mailing list
    cisco-voip at puck.nether.net
    https://puck.nether.net/mailman/listinfo/cisco-voip
    _______________________________________________
    cisco-voip mailing list
    cisco-voip at puck.nether.net
    https://puck.nether.net/mailman/listinfo/cisco-voip





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


  _______________________________________________
  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/20061024/7b72b50f/attachment-0001.html