sip server

SIP Server Information Setup  to define the SIP Proxy setup for outbound/ inbound. The 10-29 commands are not used in non-registration mode.If entries are made in Program 10-29-xx for a SIP Server and the SIP Server is then removed or not used, the entries in Program 10-29-xx must be set back to their default settings. Even if 10-29-01 is set to 0 (off), the system still checks the settings in the remaining 10-29 programs.

Daylight Savings Setup

Daylight Savings Setup  to set the options for daylight savings. As the telephone system is used globally, these settings define when the system should automatically adjust for daylight savings as it applies to the region in which the system is installed

Pre-ringing

Pre-Ringing Setup  to enable or disable pre-ringing for trunk calls. This sets how a trunk initially rings a telephone. With pre-ringing, a burst of ringing occurs as soon as the trunk LED flashes. The call then continues ringing with the normal ring cadence cycle. Without pre-ringing, the call starts ringing only when the normal ring cadence cycle occurs. This may cause a ring delay, depending on when call detection occurs in reference to the ring cycle.

To enter programming mode

To enter programming mode : 1. Go to any working display telephone.In a newly installed system, use extension (port 1). 2. Do not lift the handset. 3. Press  Speaker. 4. # *  # *. 5. Dial the system password +  Hold. Refer to the following table for the default system passwords. To change the passwords,

PRI applications

T1/PRI For  T1 or  PRI  applications  (only  PRI on  the  ESI-50; it doesn’t support  T1),  an  ESI  Communications  Server can use a  compatible  digital  line  card  (DLC)1: •  ESI-1000,  ESI-600,  ESI-200,  ESI-100 —  DLC  and  DLC12,  each  for  either  T1  or  PRI. •  ESI-50  —  DLC82  for  only  PRI. Depending  on  how  you configure it,  each  supports  either  (a.)  a  single  T1 circuit  at  24  DS0 channels or  (b.)  a PRI  circuit  supporting  23  “B”  (bearer)  channels  and  one “D”  (data link)  channel.  The DLC12 and  DLC82 each also  support  12  digital  stations.  The  T1 or  PRI  line is  connected  via the  last  two pairs  of  the industry-standard 50-pin  amphenol  cable  connector  on  the front  of  the  DLC. Each  ESI  Communications  Server  has  a  different  maximum  number  of  system-wide  DLCs  (see  “Port  card options,”  page  A.4).  Partial  T1  or  PRI  applications  are supported  through  line  programming. Each DLC has built-in  CSU  functionality.  The  integrated  CSU  can be enabled  or  disabled  via system programming2.  The following functionality is  provided:  line,  payload,  DTE  and none  (normal  operation) loopback  modes  with  the  ability  to  respond  back  controlled  via  system  programming;  alarm  conditions,  and both  ANSI  T1.403  and  TR  54016  performance messages  for  ESF only.  Important:  On  the ESI-50,  the DLC82 may be installed in  only  slot  2. If  you’re  installing more  than one  T1  or  PRI,  the  DLC  in the lowest  number  slot  will synchronize (“slave”) the system  with  the public  network.  The system will  synchronize  to  only one clock  source.  Therefore,  ESI strongly  recommends  that  the first  DLC  in the  system be connected to  the  T1  or  PRI  that’s connected either  to  the local  CO  or  the nationwide long-distance provider,  either  of  which typically will provide  veryhigh-accuracy  clocking (Strata 3).  The DLC  doesn’t  provide master  or  sub-master  clocking for  privatenetwork  T1  spans.

ESI System Programmer

The  ESI  Communications  Server  supports  the  48-Key  IP  Feature  Phone  II,  ESI  IP  Cordless  Handsets,  VIP Softphone,  and  SIP  phones.  (See “System  capacities,”  page  B.1,  for  the maximum  number  of  IP  phones that your  specific  ESI Communications  Server  will  support.) The ESI-50 has  a built-in IVC12.  It  can  support  up to  12 IP  channels,  which can  be  a  combination of  local  IP, remote  IP,  and Esi-Link  channels.  The channels  are  activated in  blocks  of  four  for  local  IP,  singles for  remote IP,  and four  or  twelve  for  Esi-Link.  Here  is  an  example of  some  possible  ESI-50  IVC12 channel  combinations: •  12 all  Esi-Link. •  12  all local IP. •  Eight Esi-Link, four  local IP. •  Four  Esi-Link, four  local IP, four  remote  IP. When  two  or  more  Intelligent  VoIP  Cards  (IVCs)1  and the  necessary licensing are installed in  an  ESI Communications  Server, the  first IVC  (lowest-numbered  slot) will be  designated  as  the  primary  IVC,  which acts  as  a “go-between”  to  associate a  station to  its IVC.  To  each IVC,  the  system  automatically  allocates  24 sequential  extension  numbers,  as  defined  in  the  dial  plan selected  in  Function 169.2  Therefore,  the  primary  IVC must be connected  to  the  same  network  as  all  of  the  other  IVC  station cards. If  an IVC  supports  12  IP  stations,  only  the first  12  extension  numbers  can be  assigned to  IP  stations. Programming  IP  stations  is  similar  to  programming  digital  stations,  except  that  additional,  IP  networking parameters are required for  the former. There  are three ways  IP  networking parameters can  be assigned to  IP  stations in  an  ESI  Communications Server: •  Via  Function  31, as  described  in  the  following  pages. •  Using  ESI  System  Programmer. • Via “setup mode” at an ESI IP Feature Phone II.

Centrex

Centrex/PBX  access code If the  system  is  to  be  used  behind  Centrex  or  another PBX,  you  must  list  the  dial  access  code  used  to  gain access  to  a CO  line from  Centrex  or  the PBX,  so that  toll  restriction  can ignore  the  access  code  digit(s).  Users must  dial  the access  code  after  accessing  a line  by  either: (a.) Dialing 9, 8, 71, 72, 73, 74, 75, or 76.  or (b.)  Pressing  a  line key (if  programmed). The access  code can be one or  two digits  —  e.  g.,  9,  81,  etc.  —  and must  be programmed for  each line group. Default:  0.  Note:  You must  set  the flash duration in Function 151 (page  E.3)  for  the requirements  of  the host  switch. Function  222: Toll restriction exception tables The  system’s  toll  restriction  is  based  on  outbound  calls  being  defined  as  either  toll calls  (i.e.,  calls  in  the  deny table) or non-toll calls (calls in the allow table). Four tables exist for this purpose: 1.  Allow exception  table  (programmable).  Up to  100 entries;  no  entry  can exceed  26  digits. Default: No entries. 2.  Deny exception  table  (programmable).  Up to  100  entries;  no  entry  can exceed  26  digits. Default:  No  entries. A number listed  in  the  allow  exception  table  —  e.g.,  a  branch  office  or  vendor’s  location  —  will  be  allowed  to all  stations,  regardless  of  how they’re  set  in  Function  32  (see  page  G.19).  Conversely,  a number  listed  in  the deny exception table (e.g., a “1-900” number) will be denied to all stations. 3.  Fixed allow  table  (not  programmable). Default:  1800,  1888,  1877,  1866,  1855,  1844,  1833  and  1822.  4.  Fixed  deny  table (not  programmable). Default:  976,  1976,  1xxx976,  900,  1900,  1xxx900,  555,  1555,  1xxx555,  0,  10,  411,  1411  and   11+-digit  restriction. In  extension feature  authorization (Function  321;  see page  G.19),  each  extension is  set  to  be  toll-restricted one of  two  ways:  TOLL  CALLS = Y  (yes) or  TOLL  CALLS  = N  (no).