Hi

We bought PBX data logger last year and it works great. It reads the smnp output from our Avaya IPO and binds the data via ODBC TO SQL Server.

One issue that we have to overcome is that one of the fields from PBX is CALL_ID. This is a "unique" field for every call through the PBX. The problem is that anytime the Avaya is reset, for whatever reason, the CALL_ID number is also reset, so you can end up with non-unique entries in this column. We however always need them to be unique in the database.

Is there a way to get PBX data logger to insert a value into a uniqueidentifier field in the database each time it logs a call into it? Or is there some other way to overcome this problem?

Many thanks

Rich

Sorry my fault, please ignore above. I found that nc process hadn't shutdown properly and was still bound to the port - it's working now!

No I'm afraid it doesn't. Even though netcat still works, is there anything I can do to rule IPOffice out as the problem - any quick way to send something to PBX logger and test it is at least receiving data ?

Thanks

Hi

We're testing Advanced PBX Logger V2.7.1.913 to grab SMDR output from Avaya IPOffice R6 and input into SQL, but are having problems the logger to listen to anything.

We know that the SMDR is being output from Avaya since we've tested it with netcat and it will grab data on the port we specified and output to text.

I've changed PBX Logger to listen on the same port (after stopping netcat) but nothing gets recorded, no errors neither.

Should it work with this ? - When I installed I chose Avaya 500 as the configuration as it seemed to be the closest fit. Is there anything else to check ?

Thanks

Rich