[cisco-voip] One DID >> several phones ring
Aman Chugh
aman.chugh at gmail.com
Wed Dec 13 14:21:01 EST 2006
Forwarding options on HP are not available in 4.0.x ,they were introduced in
CM 4.1.X
Aman
On 12/14/06, Tim Reimers <tim.reimers at asheville.k12.nc.us> wrote:
>
> Nope---
>
> Just a "route this pattern" and a "block this pattern" option is all that
> I see that says anything about routing.
>
> I think this -may- be a Unity side issue--- in that the calls ARE going to
> Unity now after 'falling out' of the Hunt Group.
>
> Problem is, nothing is telling Unity that this call 'came from' 6196, such
> that Unity knows to send the call to the CH for 6196
> Unity has no idea what's going on, so it's just sending the call to the
> standard "enter your password, followed by pound" option.
>
> I'm not even certain -where- inside Unity the call is ending up... but it
> IS going there...
>
> Thanks, Tim
>
> ------------------------------
> *From:* Vince Loschiavo [mailto:VLoschiavo at data-corporation.com]
> *Sent:* Wednesday, December 13, 2006 1:28 PM
> *To:* Tim Reimers
> *Subject:* RE: [cisco-voip] One DID >> several phones ring
>
>
> Is there a "route of last resort" type option on the hunt group config?
>
> ------------------------------
> *From:* cisco-voip-bounces at puck.nether.net [mailto:
> cisco-voip-bounces at puck.nether.net] *On Behalf Of *Tim Reimers
> *Sent:* Wednesday, December 13, 2006 1:18 PM
> *To:* cisco-voip at puck.nether.net
> *Subject:* Re: [cisco-voip] One DID >> several phones ring
>
>
>
> Update on this issue for the group--
>
> Running CCM 4.01
> Unity 4.0
>
> I have done the steps mentioned by Scott --
> I now have a functioning 6196 >> ring several phones at once
>
>
> But-- the problem now is that if no one answered 6196, it went to 'busy'
>
> A suggestion was to add my VM pilot points to the HuntGroup
>
> Did that, and after I added that LG8000 to the Hunt List, it works--- I
> can call Maintenance on 6196, and all the phones ring.
>
>
>
>
>
>
>
> But, if no one answers, the call now goes correctly into Unity *BUT* does not go to the Call Handler for Maintenance--
>
>
>
>
> Instead, I get:
>
> "Enter your password, followed by pound"
>
>
>
> It sounds like it's going into someone's mailbox (possibly the last member
> of the MaintLG group?)
>
>
>
> FYI, here's the config:
>
>
>
> MaintHuntPilot (6196) >> MaintHuntList >> MaintLineGroup (contains
> 6197,6198,2991,2992,2993,2994, running in broadcast)
>
> * After* implementing Scott Voll's suggestion:
>
>
>
> MaintHuntPilot (6196) >> MaintHuntList >> MaintLineGroup (contains
> 6197,6198,2991,2992,2993,2994, running in broadcast)
>
> and HG8000
> (contains VMPilotPoint/8000,VMPilotPoint/8001...VMPilotPoint/8016)
>
> <these
> are the 16 lines pointing to Unity)
>
>
>
>
>
> Maint's CH does have 6196 on it as an extension..
>
>
>
> How can I get the HuntList to fall through and go to the Call Handler for
> Maintenance instead of a mailbox?
>
> (note- the MaintLG is running in 'broadcast' mode, so that all phones ring
> at the same time)
>
>
>
> Scott had suggested a 'forward no answer' option be set on the HuntPilot.
>
> I cannot find that on CCM 4.01
>
>
>
> Does this make sense, or have I confused people?
>
>
>
> thanks, Tim
>
>
> ------------------------------
>
> *From:* Voll, Scott [mailto:Scott.Voll at wesd.org]
> *Sent:* Tuesday, December 12, 2006 11:08 AM
> *To:* Tim Reimers
> *Subject:* RE: [cisco-voip] One DID >> several phones ring
>
> Under Route plan there is your route/Hunt.
>
>
>
> There are three things you need to configure
>
>
>
> First the Line Group – setup all the extension you want to ring and set
> the algorithm to Broadcast
>
>
>
> Then setup the Hunt list to include the LG you just setup
>
>
>
> Then setup the Hunt Pilot with the DID and the HL you just setup.
>
>
>
> Test
>
>
>
> Done
>
>
>
> Scott
>
>
> ------------------------------
>
> *From:* Tim Reimers [mailto:tim.reimers at asheville.k12.nc.us]
> *Sent:* Monday, December 11, 2006 7:10 PM
> *To:* Voll, Scott
> *Cc:* Tim Reimers
> *Subject:* RE: [cisco-voip] One DID >> several phones ring
>
>
>
> so ... Hunt List with 6196 >> Hunt Group >> route plan >> Line
> Group<extensions to call> ???
>
>
>
> I'll look at this in the AM and ensure that I see all the steps needed..
>
>
>
> thanks Scott!
>
>
>
> Tim
>
>
> ------------------------------
>
> *From:* Voll, Scott [mailto:Scott.Voll at wesd.org]
> *Sent:* Mon 12/11/2006 4:46 PM
> *To:* Tim Reimers; cisco-voip at puck.nether.net
> *Subject:* RE: [cisco-voip] One DID >> several phones ring
>
> Route plan à Line Group
>
>
>
> Make new one with the extensions and under distribution Algorithm àBroadcast
>
>
>
> Then place in Hunt Group and then Hunt list with your 6196.
>
>
>
> Hope that helps.
>
>
>
> Scott
>
>
> ------------------------------
>
> *From:* cisco-voip-bounces at puck.nether.net [mailto:
> cisco-voip-bounces at puck.nether.net] *On Behalf Of *Tim Reimers
> *Sent:* Monday, December 11, 2006 1:35 PM
> *To:* cisco-voip at puck.nether.net
> *Subject:* [cisco-voip] One DID >> several phones ring
>
>
>
>
>
> Hi --
>
> silly question..
>
> Can someone point me to Cisco's how-to on configuring one DID to ring
> several phones
>
> Once upon a time, I knew how to do this in 3.x, but it's been a long time.
>
> and…
>
> we now run 4.01 -- and I think things are different.
>
> I have tried reading whitepapers, etc -- and I think I have some
> understanding… but not a 'steps to follow'
>
> As an example--
>
> I want 6196 to ring simultaneously on
> 6197
> 6198
> 2990
> 2991
> 2992
> 2991
>
> whoever picks it up, gets the call.
>
> Next call rings the same phones again..
>
> Thanks, and sorry for asking for simple directions, instead of having the
> time to do all the reading and figuring myself…
>
> Tim
>
>
> _______________________________________________
> 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/20061214/a1879ca7/attachment-0001.html
More information about the cisco-voip
mailing list