Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

COS hipath 4K

Status
Not open for further replies.

tecnouser

IS-IT--Management
Feb 13, 2011
20
DZ
Hello experts,

Sometimes you get strange requests which will set you clueless, here one of them that I will be happy to find out how you are managing it:
My customer want to give some extension the right to make external CO calls by without being able to transfer them to internal party,
By the way this is a Hipath4K V6

Thank you for your help

Tecnouser
 
If you look at the COS that is assigned to that phone (not the LCR COS) you will see lots of boxes and some of them have checks in them. The parameter that enables the ability to forward your phone outside the organization is "CFWCO" (call forward to central office). Putting a checkmark in that box of the COS will enable that.

However, I would suggest you make a new COS which is a copy of the one you are currently using, and check that parameter in the new COS. Then assign that COS to both the day/night spots on the phone in question. The caution here is not to add the feature to a COS that has a bunch of phones in it unless you want all of them to have it.

In the Assistant, COS is under Configuration management and then Tables. In expert mode the AMO is COSSU, but it's easier to do it through the assistant. :eek:)
 
Thank you dond01 for your reply , but the needed restriction is to be able to place an outgoing CO call but to not be able to transfert it the internal party, as you said I will have a look in the COSSU:COS and will let you know.

Thank you
Tecnouser
 
Sorry, I misread that.
I know how to restrict all calls for internal users, but not specific calls. I am a hospital among other things, and we have set things up in the past so the staff, patient rooms, and common areas were all in different groups - putting a phone in an ITR group, and normally they can all talk to each other, but in the event of an emergency we chan change it so the patient rooms can't call the staff phones or the common area phones, and the common area phones can't call anywhere else in the hospital. If we had a mass casualty and the family were being gathered in a meeting room we could keep them from being able to barrage ER with phone calls, etc. I believe you use VBZ to say which groups can talk to each other. Problem here is that is all for internal phone - phone traffic, and I'm not sure there is a way for the system to know and act on if a call is external and is being transferred. I don't think if you have a phone restricted to something like internal calls only if that would make any difference because the call has already been placed and is merely being transferred. I will be interested to see if someone actually comes up with a solution for this!
 
Quickest way would be to give them an analogue phone, and remove the 'R'/Recall button so as they cannot transfer.
 
Yes this can be a solution as I didnt find class of service to deny the transfert.

Thank you
Tecnouser
 
Or on some phones you can change the recall type to 'Earth Recall' which will not work on HiPath and therefore when they press the R button no transfer will happen.
Some user might cop on to the Timed Break Recall by quickly pressing the hang up switch and then get dial tone back.
To avoid that you could change the timers applicable only to that phone.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top