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 gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
DID Configuration at hiPath 4000 V6
- Thread starter RICHTz
- Start date
- Thread starter
- #21
- Thread starter
- #24
- Thread starter
- #25
Hi EngModo,
Great. Well Spotted.
Yes DSSKEY - DSS Functions via DSS Keys
Obviously not for Analogue Extensions.
Have not come across that problem because all the systems I work on have predefined classes of service for each type of phone.
However as I am sure you will agree, the explanations of any/all of these functions are less than desired.
Great. Well Spotted.
Yes DSSKEY - DSS Functions via DSS Keys
Obviously not for Analogue Extensions.
Have not come across that problem because all the systems I work on have predefined classes of service for each type of phone.
However as I am sure you will agree, the explanations of any/all of these functions are less than desired.
- Thread starter
- #27
the great is the discussion with you, thanks alot
why are you predefined classes of service for each type of phone?
also i have another issue need to know how it will be the trick, if i need to make a timer of trunk (i need the call ended after 5 minute as example)
why are you predefined classes of service for each type of phone?
also i have another issue need to know how it will be the trick, if i need to make a timer of trunk (i need the call ended after 5 minute as example)
Hi EngModo,
Yes the discussions are great, thank you too.
When Hicom 300 came out (many moons ago) it was a follow on from the Hicom 110, 120, EMS601 etc. systems.
It was found to be 'best practice' to pre define as much as possible in every system that was to be programmed.
So for example if you went to a site or logged on to a customer site that you had never been at before you would know that a Fax Machine had a COS of 10 for example, and a digital phone with no external forwarding was COS 12 or whatever, so you had a good idea that it would work to the way you wanted it to work.
Originally COS also included the ability to dial out but that part of the COS was replaced by LCOSV and LCOSD
So you made up your tables for COS and LCOSV/LCOSD beforehand and it helped even more when text labels were introduced so you could label them up.
Originally on the older systems they used the AMO's EWADA and EWAKO but that was replaced by the COS/LCOSV/LCOSD
So if you are adding a phone then to a system you would know what default COS to add it to as it was pre defined and known to work, that then avoids problems like you came across with the DSSKEY thing.
The timer issue would be one that was popular in times past when phone calls were more expensive, nowadays most customers have installed cheaper carriers. With regard to a call lasting 5 minutes or more you could move to a Call Charging model whereby you put the bill back to the end user that made the call?
Yes the discussions are great, thank you too.
When Hicom 300 came out (many moons ago) it was a follow on from the Hicom 110, 120, EMS601 etc. systems.
It was found to be 'best practice' to pre define as much as possible in every system that was to be programmed.
So for example if you went to a site or logged on to a customer site that you had never been at before you would know that a Fax Machine had a COS of 10 for example, and a digital phone with no external forwarding was COS 12 or whatever, so you had a good idea that it would work to the way you wanted it to work.
Originally COS also included the ability to dial out but that part of the COS was replaced by LCOSV and LCOSD
So you made up your tables for COS and LCOSV/LCOSD beforehand and it helped even more when text labels were introduced so you could label them up.
Originally on the older systems they used the AMO's EWADA and EWAKO but that was replaced by the COS/LCOSV/LCOSD
So if you are adding a phone then to a system you would know what default COS to add it to as it was pre defined and known to work, that then avoids problems like you came across with the DSSKEY thing.
The timer issue would be one that was popular in times past when phone calls were more expensive, nowadays most customers have installed cheaper carriers. With regard to a call lasting 5 minutes or more you could move to a Call Charging model whereby you put the bill back to the end user that made the call?
- Thread starter
- #29
as told you before your discussion is great for me,
but really i still not understand how i will get the default value of COS for each type ?
also still i need to disconnect the analog trunk after some minutes (5 minutes for example) i did it before by luck by Ptime but really i don't know the concept of configuration.
Thanks Alot
but really i still not understand how i will get the default value of COS for each type ?
also still i need to disconnect the analog trunk after some minutes (5 minutes for example) i did it before by luck by Ptime but really i don't know the concept of configuration.
Thanks Alot
- Status