Server Help

Versetti · Novice Gender: Joined: Jan 05 2004 Posts: 54 Offline

What Biller module I should use for a CatId biller?

external:billing
external:billing_ssc

and does this look right for the golbal.conf:

-Smong- · Guest Offline

I think you only need the proxy for external:billing, billing_ssc connects directly.

I couldn't get asss-1.1.6 to connect to SSI, SSG, SOS's mod on catid's (11j) or subbill2. Although in some cases the biller claimed the server was connected (but server says otherwise).

Anyway, I'm working on a test biller using the new TCP protocol. I think I've got the basics done already (in 2 days, go me), but used client sockets instead of server listen sockets, lol.

ExplodyThingy · Posted: Mon Jan 19, 2004 6:44 pm Post subject:

Theres a new TCP protocol? I thought that was only theoretical. Can you paste the packet list or whatever? Id like to intergrate it into my new biller.
_________________
There are no stupid question, but there are many inquisitive idiots.
Loot

Dr Brain> I hate clean air and clean water. I'm a member of Evil Conservitive Industries

Smong · Posted: Tue Jan 20, 2004 8:29 am Post subject:

It is new-biller-prot.txt in the docs/ directory.
But I will attach it here so you don't have to download the whole .tar.gz.

Edit: Java TCP biller v019 http://sscont.net/smong/download/pocob.zip Only has basic log/in out, ?find, ?broadcast and persist.

ExplodyThingy · Posted: Thu Jan 22, 2004 5:04 pm Post subject:

This is groovy and all, but its pretty unspecific. Theres nothing showing like at offset 0, len 2, the the value is 0x0001 for connect request or anything. I can figure out things to a degree, but if it just shows "CONNECTOK:BILLERNAME" then its preyy uselss.

[edit]
Nevermind, I see from your source that those werent placeholders but rather actual strings. This seems kid of crapy. As a suggestion for CONNECTOK:BILLERNAME, make it CONNECTOK:SOFTWARE:BILLERNAME, as there will be several billers out there. I am currently writing a dual tcp-udp biller, you have yours, Im sure there will be others, and adding the SOFTWARE should help people identify what they are connection to. This would be a great diagnostic tool.

Smong · Posted: Fri Jan 23, 2004 1:40 pm Post subject:

BILLERNAME is the software. In global.conf, Billing:ServerNetwork gets sent in the g->b CONNECT message. If the network is incorrect the biller can reject the server. It is a good idea to look at billing[_ssc].c as there are undocument .conf values in there.

You can also start a convention by sending CONNECTOK:software:billername, but you will have to edit the server or observe the console output from the server side to see this (I <billing> logged into billing server (POCoB v0.3.2)). Or just edit the server and make it part of the protocol and not just a convention.

ExplodyThingy · Posted: Sat Jan 24, 2004 6:58 pm Post subject:

Most people refer to biller name as the network. Then we should definately do a :SOFTWARE thing. One for network, one for software. So do CONNECTOK:ExplBill v0.0:SSI. But there should also be a strictly numeric version check, so that you can make it only access versions x and above/below.

Versetti · Novice Gender: Joined: Jan 05 2004 Posts: 54 Offline

Hmmmmm I think the biller will not let the ASSS Server connect. It gets the singles but will not connect for some strange reason...........

Smong · Posted: Sun Jan 25, 2004 1:05 pm Post subject:

g->b: "CONNECT:version:swname:zonename:network:password"
version is the version of the protocol used.

Isn't that good enough?

I don't think it is likely that there will be more than one biller per IP address, can't that be used to identify the 'software'?. DNS is even better: tcp-biller.foo.bar, where foo clearly shows what network it is.

ExplodyThingy · Posted: Sun Jan 25, 2004 2:06 pm Post subject:

I suppose youre right. This just stemmed from a misunderstanding of what was meant by BILLERNAME. We should at least start the convention of sticking the software name in there with the version to help diagnostics. CONNECTOK:ExplBill v0.0.3