PBX Data Logger -> Mitel 3300 (ICP? standard?) help in next 24hrs

[SirParadox]

So I have a brand new Mitel 3300 going online.
 Prior to today, we had our own custom enterprise wide CDR collection service.
 
 I'm attempting to stop re-inventing the wheel.

 I googled.  And found this product.

 I am VERY excited as I might be able to use about 3 other products including the OPC data importer/exporter.

Now.  Here's my issue.  I attempted to setup the data logger / parser.  So far great.  It connects to my Mitel pbx.  It ships the data off to my MSSQL database.  I noticed my SMDR files have the source extension, but the resulting sql table "PBXDATA" is mangled, loosing caller_phone.

I tried "Mitel 3300 ICP", "Mitel 3300 ICP [Stardard Full]" and a few others.

Can someone assist me in identifying which of the several "Mitel 3300 ICP ..." formats is the correct format?  Is it possible none of them are and I need help tweeking the data parser module, by hand?

Again.  This new PBX is going into beta-production, not production, 09:00AM EST 2013-10-08.

 If I could get this logger operational for this time period we would be immensely grateful and almost without a dbout a customer.

==
Escape character is '^]'.
 10/07 13:47:22  0000:00:08 5108    **** 5107                      I 5107                                  000                                                                                                 

 10/07 13:47:22             5108         19734797902                 T899                                  000                                           A0004829 A     
==

Now if I can't get this fired up in the next 24/48 hours; that will not preclude me from giving this software a shot.  I'm just very excited by it.  Probably more excited then I should be

[SirParadox]

Ok so it was "Mitel 3300 ICP [Full Time]"

Lol!

I posted after trying 3 of the types.  Figured it might need an advanced tweek, so I better start the process of asking for help.

As soon as I posted, I tried one more cycle through the types and it worked.

Now "Why don't I know what type it was".  Simple.  I've been hands-off this [new] phone system, thank god. 

[Arthur Grasin]

About the extensions in the "caller_phone" field. By default our software writes the extension to the corresponding field (EXT). If you need to change this behavior then you may use the "Expressions" plugin.

[SirParadox]

I have to say one developer to another I'm very impressed with the modularity of the software.  And it looks as if that modularity paid off as you were able to re-tool the entire package to do more then just one function 'get a pbx file and send it somewhere'.  Add all the bells and whistles sure.  But now you can take that software, add an OPC driver; and shizam have a totally different package.  Very impressive.

It's crashed out twice on my windows 7 desktop.  Any suggestions on which platform it should run on?
 I am going to move it to a legacy windows-2003 server which runs our older vb6 services.  See how that fares.