(from another post)
I would've tried that, but the billing server isn't running on the same computer...
If anyone wants to see the two packets sent, I have them so just ask.
Edit: It has a syncronization request packet (connection request packet), then the billing server sends back a reset;acknowledgement packet, which means probably that the billing server doesn't like what ASSS is saying
Smong - Fri Sep 05, 2003 5:19 pm
Post subject:
Maybe uncomment ";Proxy = bin/proxy"
AlphaBoB - Fri Sep 05, 2003 5:20 pm
Post subject:
When bin/proxy is uncommented it gives an error and segfaults about not being able to find it.
Edit: I found a bproxy, and when I tried it out, it gave this:
bproxy: Sep 5 16:49:43 2003 bproxy 0.1 started
bproxy: Sep 5 16:49:43 2003 contacting remote server
........ (more stuff here)
bproxy: Sep 5 16:49:56 2003 no packets from biller in 13 seconds, assuming down
I <billing> lost connection to billing server (read eof)
|
and SubBill2.exe (Catid's subbill) gives a Connection request from 192.168.0.9:-32584
Session timeout: 192.168.0.9:32952 |
subbill.exe (default subbill) just sits like a dead duck...
Grelminar - Fri Sep 05, 2003 7:17 pm
Post subject:
Use the billing_ssc module to connect to subbill or other billers using the standard protocol.
AlphaBoB - Fri Sep 05, 2003 10:34 pm
Post subject:
billing_ssc is in what so file? core? external? I tried billing, that's not it...
Edit: I think I found it... but do I need to take off external:billing to use external:billing_ssc?
Edit again: Okay it connects and accepts and all, but every subbill.ini:KickOutDelay milliseconds it gets bumped off. Should I just change it to like 99999999999?