Thanks to visit codestin.com
Credit goes to www.scribd.com

100% found this document useful (1 vote)
281 views3 pages

Entity

Entities are used to separate users and trunks into groups with specific features. By default, two entities are created for trunks and users. The document then describes how to review and modify entity settings such as name, routing numbers, call distribution settings, voice guides, and incoming state hours which define the operating mode (e.g. attendant, day, night) throughout the day.

Uploaded by

Dhexter Villa
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
100% found this document useful (1 vote)
281 views3 pages

Entity

Entities are used to separate users and trunks into groups with specific features. By default, two entities are created for trunks and users. The document then describes how to review and modify entity settings such as name, routing numbers, call distribution settings, voice guides, and incoming state hours which define the operating mode (e.g. attendant, day, night) throughout the day.

Uploaded by

Dhexter Villa
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

ENTITY.

txt
ENTITIES
-USED TO SEPARATE LOCALS ACCORDING TO THIER GROUPING/DEPARTMENT. USEFUL IF
THE
CLIENTS WANT TO HAVE SPECIFIC FEATURES WITH-IN THEIR ENTITIES
NOTE: BY DEFAULT WE HAVE 2 CREATED TRUNK UPON INSTALLATION.
ENTITY 0
ENTITY 1

ENTITY USED FOR TRUNKS


ENTITY USED FOR USERS

PATH: MGR>ENTITIES>REVIEW/MODIFY
"#Review/Modify: Entities######################################################.
/
/
/
Node Number (reserved) : 1
/
/
Entity Number : 0
/
/
/
/
Name : ENTITY_0
/
/
UTF-8 Name : --------------------------------------- /
/
Attendant Group Manager : -1
/
/
Priority + NO
/
/
Emergency call to attd + NO
/
/
Traffic Overflow + Disallowed
/
/
Installation No. (ISDN) : 706
/
/
Supplement.Install.No. (ISDN) : 8700
/
/
Caller ID Secret + No
/
/
AdvOfCharg2 requests (AOC2) + NO
/
/
AdvOfCharg3 requests (A0C3) + NO
/
/
Auto. Locking : 0
/
/
Voice Mail Box No.for attendt : -------/
/
Trunk Group ID : -1
/
/
External Callback Table : 0
/
/
/
/
Call Distribution
/
/
/
/
Overflow Routing No. : -------/
/
Forwarding on routing + NO
/
/
1st Night Routing : 38889
/
/
2nd Night Routing : -------/
/
3nd Night Routing : -------/
/
1st Day Routing : 38889
/
/
2nd Day Routing : -------/
/
3nd Day Routing : -------/
/
1st MODE 1 Routing : -------/
/
2nd MODE 1 Routing : -------/
/
3nd MODE 1 Routing : -------/
/
1st MODE 2 Routing : -------/
/
2nd MODE 2 Routing : -------/
/
3nd MODE 2 Routing : -------/
/
/
/
Calls Priority
/
/
/
/
Normal Public Trk grp Entity : 6
/
/
Urgent Public Trk grp Entity : 5
/
/
Normal Private trk grp Entity : 10
/
/
Urgent Private Trk grp Entity : 9
/
/
Normal Public DID Entity : 6
/
/
Urgent Public DID Entity : 5
/
/
Normal Private DID Entity : 10
/
/
Urgent Private DID Entity : 9
/
/
Normal Int Callee DID Entity : 12
/
Page 1

ENTITY.txt
/
Urgent Int Callee DID Entity : 11
/
/
Normal Public Non-Answer DID : 4
/
/
Urgent Public Non-Answer DID : 3
/
/
Normal Private Non-Answer DID : 8
/
/
Urgent Private Non-Answer DID : 9
/
/
/
/
Voice Guides
/
/
/
/
Waiting Guide : 720
/
/
Attendant Waiting Guide : 494
/
/
/
/
Overflow Timer : 0
/
/
Company Call Number : -------/
/
/
G##############################################################################H
OVERFLOW TIMER

- THE TIMER IN WHICH THE CALL WILL TRANSFER TO ANOTHER SET/LOCAL


DEFINED IN CALL DISTRIBUTION TABLE.
- THE TIMER CAN BE MANAGED BY CHANGING ITS VALUE (per 100ms)
- IF NOT MANAGED, IT WILL FOLLOW THE INTERVAL DEFINED IN THE TIMER

1ST, 2ND, 3RD NIGHT ROUTING


- IS MORE USEFUL TO USE IF NO ATTENDANT IS CONFIGURE
- WHEN NO ATTENDANT CREATED, THE STATUS WILL ALWAYS BE IN THE NIGHT
MODE
WAITING GUIDE

- USE THE VOICES GUIDE CREATED IN THE CONFIGURATION.

INCOMING STATE HOURS


`
- TO DEFINE WHAT WILL BE THE TIME OF EACH MODE IN EVERY DAY
PATH: MGR>ENTITIES>DESCEND>ENTITY INCOMING STATE HOURS
"#Review/Modify: Entity Incoming State Hours#################################.
/
/
/
<<
All instances
>>
/
/
[
Set filters
]
/
/
[
Select attributes
]
/
/
/
/
Node Number (reserved) : 1
/
/
Entity Number : 1
/
/
Day + --------/
/
/
G############################################################################H
* ENTER THE ENTITY NUMBER

"#[ 7 ] Instances: Entity Incoming State Hours#.


/
/
/ -> Monday
/
/
Tuesday
/
/
Wednesday
/
/
Thursday
/
/
Friday
/
/
Saturday
/
/
Sunday
/
/
/
G##############################################H
* ENTER THE DAY YPU WISH TO MANAGE
Page 2

ENTITY.txt
"#Review/Modify: Entity Incoming State Hours#################################.
/
/
/
Node Number (reserved) : 1
/
/
Entity Number : 1
/
/
Day + Monday
/
/
/
/
Changeover 1
/
/
/
/
Hour : 8
/
/
Minute : 0
/
/
Status + Attendant Group
/
/
/
/
Changeover 2
/
/
/
/
Hour : 12
/
/
Minute : 0
/
/
Status + Mode 1
/
/
/
/
Changeover 3
/
/
/
/
Hour : 13
/
/
Minute : 0
/
/
Status + Day
/
/
/
/
Changeover 4
/
/
/
/
Hour : 17
/
/
Minute : 0
/
/
Status + Night
/
/
/
G############################################################################H
NOTE: MILITARY HOUR

Page 3

You might also like