Diameter client and server examples are now the applications under the name diameter_client and diameter_server respectively. Both of them are implemented using two processes: one of them using the gen_fsm behaviour and another one using the gen_server behaviour to handle the transport connection.
The applications may be configured (address and port) by editing their application (diameter_client.app/diameter_server.app) file. To start any of the applications it is required to start diameter application previously to provide the capability to encode/decode messages.
At the moment, only a small subset of the peer state machine in RFC3588 has been implemented so more effort will be put to be as compliant as possible with this state machine and to improve diameter stack to handle basic error cases such as avp/command definition not found.
skip to main |
skip to sidebar
Blog for the diameterl (diameter in erlang) project
2 comments:
Hey jcollado. I'm really interested in your project. I have strong interest in learing erlang, as well as working on a diameter project. Do you have an email address I can contact with?
Thanks.
Hello,
I'm glad to read that you're interested in the project and in erlang itself.
Please contact me at the following e-mail address: h5bvvjjaypucdvc@jetable.org
Best regards.
Post a Comment