[reSIProcate] Basic client/server setup
Alan Hawrylyshen
alan at jasomi.com
Mon Nov 1 17:27:56 CST 2004
On Nov 1, 2004, at 13.48, Bryan Klisch wrote:
> Community,
>
> I understand the level of discussion in this development list is
> primarily geared towards functionality improvements and details with
> the implementation. However, I don’t see any “user” lists, so I
> humbly resubmit my newbie question.
>
> Is there anybody who would be willing to work with me to get a simple
> client/server communication going? As I said before, the lack of
> documentation and code comments have left me trying to establish a
> connection with the testServer and testClient apps (only because they
> seem the most aptly named). I have set up the project files in a
> debug Visual Studio windows environment but am unable to get a socket
> connection established. I gave up on trying communicating between two
> different machines and am just trying to get a single-machine scenario
> going at this point.
>
>
>
> The first thing I would like to know is simply what the command lines
> should look like for the testServer and testClient apps? This is what
> I am currently using:
>
> ./testServer LOG_DEBUG 1 TCP
>
> ./testClient LOG_DEBUG "sip:fluffy at 192.168.1.100;transport=TCP"
>
>
> I have details about what the debug trace is outputting and other code
> changes I needed to make, but I think I just need to find somebody
> willing to help me first.
>
>
> My overall goal in getting up and running is to replace OpenSSL with a
> smaller TLS library. Once I have the initial communication framework
> in place (with security), I don’t anticipate having to bother this
> group much. In return for any help, I am willing to document the
> steps necessary to get up and running with a simple client/server
> communication example. I believe the document could be helpful for
> future users who come across reSIProcate.
>
>
In fact; I think there is value in having this on-list.
The test drivers are crusty at best. So it's hard to really launch into
a 'standard' explanation or way of doing things.
I'd almost be tempted to suggest you look at the DUM stuff if you are
wanting to write a user-agent.
There is a lot of hair needed on top of the stack if you are doing a
full user-agent.
Otherwise; I'll bite -- send me some output (off list) showing the
trouble you've been getting and I'll see if I can get a client/server
simple test up and going.
With you over the next short while.
HTH
Alan
More information about the resiprocate-devel
mailing list