[cisco-voip] CUCME : Same Dead End . Any workarounds?
Anthony Kouloglou
akoul at dataways.gr
Fri Feb 3 06:17:54 EST 2012
Hi Bernhald,
that's nice and clever.
Assuming you always have at least 2 buttons on a console device, that
will work.
I 'll give it a try.
Thanks
Anthony
On 03-Feb-12 13:01, Bernhard Albler wrote:
> When I was young (we still used steam powered routers for CMEs back
> then) I used to do the following for such a requirement:
> 1.)Don't actually forward the main number to the Huntgroup (e.g.
> number 90) but rather to a normal DN (e.g. number 91)
> 2.)Put the normal DN(91) on a button without overlay. Label as "Main
> Number" or similar. This way CFA should work from the phone
> 3.)Put a speed dial on the phone labeled "Office Open" on the phone,
> target for the speed dial is the huntgroup (90)
> 4.)Tell people to do the following:
> a.)When the office is supposed to be open, hit the 91 DN, press the
> CFA Softkey andf then the "Offen Open" button
> b.)When forward somewhere else, press the 91 DN , press CFA and then
> forward wherever you want
> c.)When reversing to normal operation, do as in a.)
>
> This always worked on 79XX phones, not sure about the SPAs. Do they
> allow secondary line call forwards when using non-overlayed DNs?
>
> if you only need a fixed target, the above combined with the CME
> night-service might also do the trick.
>
> cheerio
> bernhard
>
>
>
> On Fri, Feb 3, 2012 at 11:34 AM, Anthony Kouloglou <akoul at dataways.gr
> <mailto:akoul at dataways.gr>> wrote:
>
> Hi all,
> i was wondering:
> Is this feature so advanced and rarely used so nobody has ever
> asked or requested from cisco to give a solution?
> Many time in SoHos, the call are answered by 2-3 persons and there
> are times that they want to use cfwall for incoming calls.
>
> I would you to share it with me. :-)
>
> BR
> Anthony
>
>
>
> On 01-Feb-12 15:19, Anthony Kouloglou wrote:
>> Thanks for the tip Wes but that seems kind of complicated for
>> average user.
>> Besides, i simplified my scenario but there are actually 4
>> devices answering calls.
>> And also, do all devices support this feature? (ie SPA508)
>>
>> Cheers
>> Anthony
>>
>> On 01-Feb-12 15:00, Wes Sisk wrote:
>>> maybe configure phone1 with mobility and configured phone2's DN
>>> as a remote destination?
>>>
>>> This will create 2 separate call legs that CUCM will
>>> independently manage.
>>>
>>> /wes
>>>
>>> On Feb 1, 2012, at 7:21 AM, Anthony Kouloglou wrote:
>>>
>>> Hi all,
>>> i am facing the problem where all incoming calls in a CUCME are
>>> ringing at the same time two devices but at some point, the
>>> company wants to have a call-forward all function enabled by one
>>> ( or both devices).
>>>
>>> 1. When i use parallel voice hunt group, call forward-all on any
>>> device does nothing (known issue)
>>> 2. When i use a third dn, overlay it to both devices in order to
>>> ring at the same time, call-forward all works only on the first dn
>>> 3. When i use the same secondary number on both dns, they have
>>> the same preference so they ring randomly.
>>>
>>> Has anyone solved this puzzle?
>>>
>>> Best Regards
>>> Anthony
>>> _______________________________________________
>>> cisco-voip mailing list
>>> cisco-voip at puck.nether.net <mailto:cisco-voip at puck.nether.net>
>>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>>
>>
>>
>> _______________________________________________
>> cisco-voip mailing list
>> cisco-voip at puck.nether.net <mailto:cisco-voip at puck.nether.net>
>> https://puck.nether.net/mailman/listinfo/cisco-voip
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net <mailto:cisco-voip at puck.nether.net>
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
>
>
> --
> Bernhard Albler, +4369917207384
> --
> "Was Nachwelt! Wie komm' ich dazu was für die Nachwelt zu tun? Was hat
> denn die Nachwelt für mich getan?"
> --Carl Friedrich Zelter
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20120203/1f1004a5/attachment.html>
More information about the cisco-voip
mailing list