Put up a BugTracker.  I’ll be importing the ASPECT projects that I’ve been working on over the years soon, so that if any users want to report bugs for those projects, they can.

Primarily though, this BugTracker is used to track the features/projects/ideas for my Xtools project.  I figured that while a diary is great, tracking future bugs and major progress in the project would be a little more automated if I utilized a BugTracker.  MantisBT is fairly full featured.  I have found a few bugs, and submitted them to the developer’s bug tracker.

Tasks completed:

  • Finished the basic DNB Parser
  • Finished the basic DNB Display page
    • Added simple filter and sort options
  • Finished the basic Batch Upload page

 
  • Completed converting one parse utility from previous scripting language to PHP, currently debugging.  Parse utilities will run as cron jobs to control CPU load.
  • Began writing file upload code, reading up on how files get uploaded via PHP and how to protect the server when permitting file uploads.  I’m currently thinking that I’ll upload to a folder that is not reachable/browsable to prevent scripts/hacks/code from being uploaded.  Retard uploads to prevent non-approved extensions, and then do a file-type check prior to running a cron job against the file to weed out any attempts to upload mis-named JPGs to the parse application.  Not to mention, I need to add a bit to the parse cron job to check if the file is valid or not and ban the user/ip from accessing Xtools again if they attempt such an action.

 

My Goal for August is complete.

Now, to set a goal for September…thinking about this for the last week really stretched me.  There are a number of things that I know which I could blog about, but the problem is that every one of those things is considered confidential piece of information.  Access to and usage of the PDT (i.e., Problem Determination Tool) interface for a Nortel Meridian-1/CS1000 is taught in a series of classes, twice a year (6-12 classes total, given about every 6 months) directly by Nortel.  And the truth is that most of what I know was learned outside of that class by watching the experts at work and taking notes along the way.

I think I’d like to aim for a BARS/NARS 101, 201, 301 type tutorials like what ghtrouthas done, but only more detailed.  Frankly, nothing can really replace the original GHTrout BARS 101 tutorial, but I can certainly try to cover things that he did not and put together a walk through for a 201, 301 type course.  Unfortunately, I think that working out the course material might make that topic a little too difficult to tackle in September.  So instead, I’ll plan on making September my month to put together the outline for that, and also to make September my month to work on:

  1. Prepare for the onslaught of blog scraping.
  2. Install FeedEntryHeader and test thoroughly.
  3. Write 101 style tutorials for the following:
    1. Adding, Changing, Deleting a set (NOTE: impossible to discuss all set types, so it’s basic 101 material only)
    2. Adding, Changing, Deleting a calling party name display record
    3. Managing descriptions (DES), tips & tricks
  4. Write course outline for 101, 201, 301 on BARS/NARS

 

Back in July, I set a goal to work on detailing out some Nortel Meridian-1/CS1000 maintenance routines.  I’m making progress on that goal.

 

  Advanced Distributor Training / Patching Overview [DRN08081301] (1.6 MiB, 466 hits)
You need to be a registered user to download this file.

I presented at the Nortern California Nortel User Association meeting in February 2008 on how to manage patches on your Nortel systems.  This PDF document is derived from that presentation but has been slimmed down from the original Power Point.

 

Programming CPND on DNIS digits

REQ new
TYPE name
CUST 0
DIG
DN
DCNO 1
IDC 3335
NAME Firstname Lastname
DISPLAY_FMT
IDC
DCNO

 

BUG0415 Invalid software trunk state detected. Far-end ONHOOK simulated. TN, TRUNKPM, *(CRPTR). Procedure TRUNKS

 

Status update:

  • Expanded code documentation (comments)
  • Added Site module to project with basic functionality intact.

 

Finally started serious work on my Xtools projects.  Xtools is the nickname I’ve given to the project to convert all of my Meridian/Succession Parse utilities to be web enabled.  Once completed, I’ll have a fully functional, multi-user death star…  I mean management interface for handling all of the customer information I’ll ever come across.

Ultimately, I plan to offer the plugin as a service for others like myself who need help managing Meridian-1 and CS1000 systems.

Planned parse utilities:

  • Parse DNB (Extension, Name, TNB, etc)
  • Parse ESN (ESN, RLI, DGT, NCTL, FCAS, TOD, etc.)
  • Parse CDP (DSC, LSC, TSC)
  • Parse BARS/NARS (NPA, NXX, LOC, SPN, etc.)
  • Parse LD 117 set information
  • Parse LD 117 inventory information
  • Parse TNB (fully functional conversion of a PRT TNB to a web & csv format)
  • Parse CDR
  • Parse TRF
  • Parse HST
  • Parse ACD Reports (really low priority, you should be on Contact Center if you’re need ACD reports)

Since these will all be in a database, I’ll be able to relate this data, and keep multiple instances of information based on upload batches for historical comparisons.

Another useful feature that will be gained from having the ESN/CDP/BARS information contained in this database I’m doing is the ability to set up multi-site networks and test tandem dialing through those networks once all sites are uploaded to the database.

Status:

  • Wrote this post.
  • Started core administration code.
  • Achieved 40% mark on customer module.

To do:

  • All user pages
  • Site module
  • Relationship module (user-site-customer)
  • Settings module (including aging values for how quickly data is aged out of the database)
  • Indices module (to reduce database size a lot of text values will be indexed and their text value converted to an index value for saving, here’s where indices will be managed)
  • Write up a project page with versioning information for storage on Undecided.

There’s more, I need to do a whole write up on the project… not that I’ll give the entire overview to anyone, but if you read these, you’ll get a fair picture of what I’m working on and what the total scope of the project is.

 

configuring SNMP traps on 5520:

Step 1: Connect to 5520 via Telnet
Result: Prompted to press Control-Y to enter Nortel Menu

Step 2: Press “M” for SNMP Configuration submenu
Result: Presented with SNMP Configuration submenu

Step 3: Press the “down arrow” twice to reach Trap #1 IP Address
Result: Trap #1 IP Address field is highlighted

Step 4: Type 10.101.1.31 and press enter
Result: Trap #1 IP Address field is configured with 10.101.1.31

Step 5: Press the “down arrow” once to reach the Trap #1 Community String
Result: Trap #1 Community String is highlighted
NOTE: string is displayed as all astrisks for security reasons

Step 6: Type the community string (e.g., “public”) for the trap receiver and press enter
Result: Trap #1 Community String is configured
NOTE: string is displayed as all astrisks for security reasons

Step 7: Press Control-C to return to the Main Menu
Result: Presented with Main Menu

Step 8: Press “L” for Logout
Result: Disconnected from the 5520

NOTE: Changes to 5520 are saved as soon as they are made.

Favorite Books

Favorite Music

© 2011 Undecided Suffusion theme by Sayontan Sinha