Multiple inbound call problem 1

[kyleamars]

I have a CME running with a 24 channel ISDN PRI. Everything is working fantastic except one problem. Main number I have a translation rule built that sends the 4 digit DNIS to ext 2000. Ext 2000 I have assigned to about 10 phones. I call this incoming. The only other button programmed on these phones is the extension number. For example. ext 1000 has button 1 - 1000 and button 2 - 2000... Now, my problem is this. Once a call is answered on that incoming ext(2000) and someone else calls the same number, the other phones don't ring. I see the second call displayed on the extension that answered the first call but not on the other phones. In other phone systems I've worked on generally what I do is when that call is answered on 2000 it drops to the users extension freeing up the original extension. Does this make sense and can anyone please help?

Thanks in advance!

 

[trvlr1]

Not sure if this will help, just a thought .... At the bottom of the page for Directory Number Config on the phone, you have options for Multiple calls/call waiting settings. These affect how many calls come to a phone. Maybe if you set it to 1 / 10 that might help.
In a Nortel system, you would set this scenario up with MCR keys (multiple call ringing) which does exactly what you are asking to do, however, I am not sure if there is an equivvalent in the Cisco .... anyone know??

 

[pndscm]

Put a dummy number on button 1 of all the phones and then make a Broadcast Hunt Group containing all the dummy numbers with 2000 as the pilot number. You can even put a label on button one saying that it is "2000". Then all the phones should ring every time.

 

[MitelInMyBlood]

We're doing this exact same thing, except used some multi-line 6-button sets (7965) then built a multiline hunt list in reverse order, so that incoming calls start at the bottom of the keystrip instead of at the top. We use a total of 6 phones, with each phone a clone (supercopy) of each other. Reversing the calls to sort from the bottom-up has the benefit of displaying the caller-id info of subsequent calls in a clear area of the screen rather than cluttering the screen as it does when top-down hunting is used. The design is basically that of a square key system, which those of you familiar with WECO 1A2 Key systems are intimately familiar with.


Original MUG/NAMU Charter Member

 

[MitelInMyBlood]

Taking this a step further, we have approx 14 published numbers that users call and it is very helpful to know what number they called. To accomplish we simply built 14 separate hunt groups (1 for each of the DID or tollfree numbers) and then put a label on each one stating what it was. Each hunt group uses the same hunt list and line group. When the call rings-in you see the callerID of the caller along with the business name of the line that they actually called-in on.

Original MUG/NAMU Charter Member