Written by DB
Time Sync - The Network Time Synchronization feature is designed to ensure that all time stamps in a network are synchronized from one source. One switch becomes the master for this purpose. In a private network environment, each switch in the network has an individual system clock. These system clocks can, under certain conditions, lose or gain time, causing inaccurate time stamps for different features. Also, in a private network, several switches can be located in different time zones. As features become more centralized in a network environment, it is useful to have time stamps based on one time zone.
LD 87
REQ new
CUST 0
FEAT cdp
TYPE dsc
DSC
FLEN 4
DSP lsc
RRPA
RLI 2
Additionally, what is important:
RLB (for RLI) - LD 86
RLB - RLI
...... - RLI
...... - RLI - ENTR 0 --> Route x
.................ENTR 1 - Route A
.................ENTR 2 - Route C
DGT (for DMI Digit Manipulation Index) - LD 86
DEL --> How MANY digits to delete
INS --> WHICH digits to insert
DSC --> DN --> RLI (RLI) - ENTR --> Route
A good place to start is GHTrout's website. GH suggests you can use pretranslation, so every number you dial will be dialled with a 9 in front. Problem is of course that you cannot dial internal numbers that start with a 9 this way ...
LD 24
REQ prt
TYPE dis
CUST 0
First, make sure you have programmed a superloop. Do this by using LD 97 :
LD 97
REQ prt
TYPE supl
SUPL
Now you see a list of all cards that are programmed. I assume you have R 24 or above. If so, your Phantom cards are somewhere between 61 and 80. If you don't see them in the list, add a superloop as following :
LD 97
REQ chg (!!!)
TYPE supl
SUPL N96
Yes, you do have to use CHG, since LD 97 doesn't provide NEW as command. By adding a 'N' in front of the loopnumber, you ADD a loop. The mapping of loopnumbers and TN's for R24 or above is :
Did you know you can change and set users and passwords in LD17? Well, here is a short description. You will need PWD2 in order to perform these actions.
Be careful !!!
LD 17
REQ chg
TYPE pwd
PWD2 xxxxxxxx
Change the LOGIN_NAME and the OVLA (OVerLays Allowed) options for instance.
The rest is described on page 436 of the NTP. If you do not have one, just send an email to tom8787@tspforum.com
Suppose you have a CS1000E, and an MG1000.
After you have programmed a new set on the CS1K, it might take a few days before it can be used on the local site, depending on your backup scheme defined on your Element Manager. To speed things up:
On the CS1000E
>ld 43
EDD
After this is all done:
>ld 43
BKR xx (xx is the zone of your local MG1000)
To look up the correct zone, open your Element Manager in your webbrowser, and click
Tools - Backup&Restore - Call Server - Backup Rules
If you want to trace a SIP call, this is what you should do.
When you're at the normal prompt, return to the OAM prompt:
>~.
oam> SIPCallTrace num
To turn the tracing back off:
oam> SIPCallTrace num
Useful information can be returned by using:
oam> help sipnpm (for all SIP related commands)
oam> help SIPCallTrace (for specific info on SIPCallTrace)
On NRS:
Click "Configuration"
Click "Set standby view"
Gateway endpoints
Click Show
Click "# routing entries" (number after "site")
Click "Show"
Click Add
Enter: Private level 0 regional (CDP steering code) - DN - Routing Cost 1
Click Save
Click Tools
Click Database actions
Choose Cut over&Commit, Click Submit. Notification: Command Succesful
On CS1K
>ld 87
ESN000
MEM AVAIL: (U/P): 97451031 USED U P: 6058398 742984 TOT: 104252413
DISK SPACE NEEDED: 1496 KBYTES
REQ prt
CUST 0
FEAT cdp
TYPE dsc
DSC 50149
DSC 50149
PROCEDURE: IP@-modification PABX (OPT11C)
>LD 137
CIOD000
.STAT ELNK
ELNK ENABLED
Ethernet (qu unit number 0):
Host: PRIMARY_ENET
Internet address: 137.135.128.253 this is the default ip-@ of the OPT11C
Broadcast address: 137.135.129.255
Ethernet address: 00:00:75:4a:7e:99
Netmask: 0xffff0000; Subnetmask: 0xfffffe00
622 packets received; 8 packets sent
0 input errors; 0 output errors
0 collisions
>LD 117
=> PRT HOST
ID Hostname IP Address
1 PRIMARY_ENET 137.135.128.253
2 SECONDARY_ENET 137.135.128.254