[cisco-voip] Huntgroup with CCM 4.1(2)

[Lelio Fulgenzi]

If you configure the forward calling search space such that the person cannot forward their phone to the pilot, you'll be set.  Some simple ways to do this would be to remove the partition which contains the pilot or to simply add a routepattern that blocks that pattern and put that as the first partition in the calling search space. We've had several instances where it was much easier to create a block pattern than it was to reorganize the partitions and calling search spaces.

As far as getting the system to recognize the call forwarding - I think you've got a lot of people behind you. There should be a spot which says 'skip member if forwarded' or something like that.


  ----- Original Message ----- 
  From: Ahmad Cheikh Moussa 
  To: cisco-voip at puck.nether.net 
  Sent: Friday, May 06, 2005 8:25 AM
  Subject: [cisco-voip] Huntgroup with CCM 4.1(2)


  Hi!

  I have a question regarding huntgroups/Pilotpoint.
  It is about the behaviour about the huntgroup.
  If a user in a huntgroup makes a callforward all
  to his own huntroup, he will produce an endless loopback.
  With callmanager 4.x there should be a way to avoid this.

  Is that true? If yes, how can I configure this ?
  Is there a way to configure the server to recognize
  that the callforward show backs to himselv and therefore
  ignore this callforwardall and goes on to the next user in
  the huntgroup ?

  Best regards,
    Ahmad

  -- 
  Ahmad Cheikh-Moussa
  NetUSE AG
  Dr.-Hell-Straße, 24107 Kiel, Germany
  Telefon: +49 431 2390 400 --  Telefax: +49 431 2390 499
  Service: Service at NetUSE.DE --  http://NetUSE.DE/
  _______________________________________________
  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/20050506/4583e557/attachment.html