Advanced PBX Data Logger and NEC Univerge SV8100 help

[steve]

Hi

Wonder if anyone can help me get Advanced PBX Data Logger to connect and read data from a NEC Univerge SV8100.

The NEC Univerge SV8100 is listed on the supported devices list.
I have tried various thing, but am still unable to see any data.

We are interested in licensing the software but need to make sure that we can use it in our configuration and were able to get the results expected.

If I run a sniffing tool, I can see raw data on the phone network. But still unable to get Advanced PBX Data Logger to receive any data at all.

Can someone give us any information on how we should configure it to talk to our system?

Thanks in advance.

[Arthur Grasin]

Please, try the following settings on your PBX.

PROG 10-12-01/02: confirm your IP address given for the CPU
PROG 35-01-01: Output Port Type (select: LAN)
PROG 10-20-05: SMDR Output Port (input: 60010)
PROG 14-01-06: SMDR Print-Out (checked)

Repeat for all the trunks necessary

Reboot SV8100

[steve]

Hi there,

Thanks for the information.
We now have some data ariving in the software

Steve

[Arthur Grasin]

Could you show an example? I'll say is it ok.

[steve]

we are still having some issues.

our PBX (sv8100) is already using two ports for communicating to an existing NEC product.

we have identified them as TCP 4000 & TCP 4001.

if we monitor TCP port 4001, your software parses the data correctly, however the logs are only received once the call is cleared down & for our usage we need instant logs.

if we monitor port 4000, the data is live in the viewer, i.e. as phones go offhook data packets are received.

this is what we need, however when the parser set to SV8100 does not pickup this data on port 4000, although it looks similar to the data on port 4001(unparsed) except it is missing a call duration, as the call has yet to clear down

is there any way we can get the parser to work correctly on the live data ? rather than the call clear down data ?

here is a line from the TCP 4001 port (parses correctly after call clear down)
38 IVIN  18:55 001 123456 00:00:47 5500        0800123123 0:00              <CR><LF>

here is a line from the TCP port 4000 a few minutes later (this only makes it as far as data view & will not parse)
<STX>P21  0101001213185936<ETX><STX>Pt1  0800123123 1213185936<ETX>

thanks in advance


 

[Arthur Grasin]

This is not a problem to add a parser for the port #4000, but we don't have description of the records.

[steve]

what do you need....

sample packets and a breakdown of what fields they are ?

[Arthur Grasin]

a breakdown of what fields they are

what do you need....

sample packets and a breakdown of what fields they are ?

[steve]

ok.

we will run some sample calls through tomorrow (inbond & outbound) and get some field data over to you.

at the same time we will also attempt to contact NEC and see if they have a packet definition.

will post back tomorrow hopefully.