Due to our installer having no engineering resource (again), I'm trying to get call logging sorted out on our OXO. We have Oak aiOffice, but no 4093, so I'm trying to do this via IP. This website (http://www.pbxtools.com/kb/pbx/alcatel) implies that I should be able to connect over FTP, and indeed I can get an authentication prompt on ftp://<switch_ip>:30021, but I can't find the correct password -- neither those given on the website (ftp_nmc/tuxalize) nor Installer/<my installer password> work. I'm tempted to change the NMC password using PM5 (I have PM5 expert) but I'm firing blind here, so I don't want to screw up and lock myself out.
Has anyone actually got call logging working using the network to pick up the tickets? If so, how? I'm not committed to aiOffice yet, so if there's something else that's known to work, tell me. Above all, though, I'd be grateful for working passwords.
OXO call log collection over IP
- tot3nkopf
- Alcatel Unleashed Certified Guru

- Posts: 4058
- Joined: 02 Feb 2006 10:41
- Location: Germany & Romania
- Contact:
Re: OXO call log collection over IP
I am interested in this problem too. It is very interesting for developing 3rd party programs interact with PCX.
About your problem:
It works fine (I'm talking about the logging). But you have to take the following steps (it worked for me - of course there are several possibilities):
1. use the "cmd" command in your run
2. in the command prompt screen type: telnet <PCX IP><space><30021>
3.you are in (you have 60 seconds to deliver user and password)
4. you do that like this (you have to write):<user><space><ftp_nmc>
5.you are being prompted for the password(you have to write):<pass><space><tuxalize>
and you're in.
I've done that but I haven't the slitest ideea how can I take tickets one's I'm in. If you make any progress on that please inform me too.
Good luck. (I'll try to keep you up to date too.)
About your problem:
It works fine (I'm talking about the logging). But you have to take the following steps (it worked for me - of course there are several possibilities):
1. use the "cmd" command in your run
2. in the command prompt screen type: telnet <PCX IP><space><30021>
3.you are in (you have 60 seconds to deliver user and password)
4. you do that like this (you have to write):<user><space><ftp_nmc>
5.you are being prompted for the password(you have to write):<pass><space><tuxalize>
and you're in.
I've done that but I haven't the slitest ideea how can I take tickets one's I'm in. If you make any progress on that please inform me too.
Good luck. (I'll try to keep you up to date too.)
-
kaype_DUP
Hi...
login: ftp_nmc
password: <your pm5 password>
this should work...
actual i do call loging via 4093 and an terminal program to a txt file published on our intranet server, but a well formated HTML page would be nice too
i cant get around with pbxTools, i think the monitor is connected, but in the phone journal i cant see any actual calls... any ideas?
greetings. ...
login: ftp_nmc
password: <your pm5 password>
this should work...
actual i do call loging via 4093 and an terminal program to a txt file published on our intranet server, but a well formated HTML page would be nice too
i cant get around with pbxTools, i think the monitor is connected, but in the phone journal i cant see any actual calls... any ideas?
greetings. ...
-
Odicha
Re: OXO call log collection over IP
Hi!
I've been looking around it this afternoon and I've partial answers for your questions about how getting logs and alarms in OXO R3x. I guess it'll be the same for releases 1x to 4x. It uses a "little strange" system.
Take a look to the traffic A4715 generates using a packet sniffer filtering ports 30021 (ftp) 30020 (ftp-data) and 31002("...control port...")
What I´ve used for replay and how can you make the same
A FTP Client (I used total commander because I had it installed for file management)
An Hex Editor
Putty
It's only a proof of concept about....
First of all we make a connection to the pbx ftp port 30021 passive mode for transfer using ftp_nmc user
when it's connected we open a port 31002 raw session with putty to the pbx
we send a file 44 bytes lenght called LOGIN.DAT specially formed (look A4715 traffic)
if we take a look to putty's session (port 31002) we'll see "LOGIN.DAT"
now we can RETR login.dat
pbx rewrote the file and added serial number and soft ver. from the pbx
now we send ACCOUNTING.DAT (3 bytes)
we'll see in putty' session ACCOUNTING.DAT
we RETR accounting.dat and we'have call tickets (take a read with and hex editor and see....)
the same proccess with ALARM.DAT (4 bytes)
Rest of work ....pseudocommands for erasing tickets and alarms. I supose it'll be done in a similar way but I'll look at it tomorrow.
I'm going to write a little BCB tool for getting logs and parsing in a SQL Server.
I'm not sure if I can give more detailed info or not, because of Alcatel propietary systems. If you think so make me know. Obviusly if you can test this you've an OXO and A4715....
PD. Sorry for my bad english
I've been looking around it this afternoon and I've partial answers for your questions about how getting logs and alarms in OXO R3x. I guess it'll be the same for releases 1x to 4x. It uses a "little strange" system.
Take a look to the traffic A4715 generates using a packet sniffer filtering ports 30021 (ftp) 30020 (ftp-data) and 31002("...control port...")
What I´ve used for replay and how can you make the same
A FTP Client (I used total commander because I had it installed for file management)
An Hex Editor
Putty
It's only a proof of concept about....
First of all we make a connection to the pbx ftp port 30021 passive mode for transfer using ftp_nmc user
when it's connected we open a port 31002 raw session with putty to the pbx
we send a file 44 bytes lenght called LOGIN.DAT specially formed (look A4715 traffic)
if we take a look to putty's session (port 31002) we'll see "LOGIN.DAT"
now we can RETR login.dat
pbx rewrote the file and added serial number and soft ver. from the pbx
now we send ACCOUNTING.DAT (3 bytes)
we'll see in putty' session ACCOUNTING.DAT
we RETR accounting.dat and we'have call tickets (take a read with and hex editor and see....)
the same proccess with ALARM.DAT (4 bytes)
Rest of work ....pseudocommands for erasing tickets and alarms. I supose it'll be done in a similar way but I'll look at it tomorrow.
I'm going to write a little BCB tool for getting logs and parsing in a SQL Server.
I'm not sure if I can give more detailed info or not, because of Alcatel propietary systems. If you think so make me know. Obviusly if you can test this you've an OXO and A4715....
PD. Sorry for my bad english
-
skamanu
Re: OXO call log collection over IP
I collected data as suggested above and got the file ACCOUNTING.DAT that presumably has the call records.
Unfortunately it looks binary to me. Can anybody please help me decode it?
Does anybody have the data format?
Regards
Unfortunately it looks binary to me. Can anybody please help me decode it?
Does anybody have the data format?
Regards
-
drusixtynine
Re: OXO call log collection over IP
Hi guys, I know it's about a year later, but I'm not managing to retrieve the accounting.dat file
I don't know how to send the login.dat and how the login.dat file looks like, I don't have any A4715 or A4760 to connect to my OXO 4.x.
Can anybody help me?
I don't know how to send the login.dat and how the login.dat file looks like, I don't have any A4715 or A4760 to connect to my OXO 4.x.
Can anybody help me?
