A parser is the a small part of what you need. Go find yourself a sip stack implementation and use it. If you try to build your own, you will squander man years and probably still end up with something that doesn't work with other sip devices.
Paul
Umesh Balani wrote:
Hi ,
Need help from all you champs in SIP here.
See, I have till date created just a few IOCP Servers on Windows.
They were all text based and in all the servers I had created my own
headers, which held the offsets in the stream where what information was present.
I have been asked to create a prototype using the SIP protocol.
On a very abstract level, here's what I figured out how to go about doing it.
1. Create a SIP Message Parser 2. Create a SIP Message Generator 3. Create an User Agent and Registrar Server (as it's a prototype, might not require proxy) using the 1 and 2 modules.
Can someone comment/suggest, did I miss out on something. ?
What I feel is toughest is to create a parser.
When it comes to creating a parser, there are so many of them available. i.e. Yuck, Lex, Bison, ANTLR.
My Parser will have to be ported to *nix Variants so I decided it has to be
in C#.
It is my understanding that with Rotor, MS Implementation on FreeBSD and Mono on the way to completion, I will be able to port it to Free OS's
without much effort.
So should be the Registrar Server that use the parsers.
Any Comments / Suggestions on this one ?
Now, I am really lost on which Tool should I use to create my parser. Can someone who's created a parser from the ABNF notation in the RFC guide me to the right direction.
I am going ahead with ANTLR as it provides me the C# support. But I am not confident about it. There's are others like CoCo R, from the SSCLI - Share Source Common Language Implementation.
How shud I go about creating the parser (don't have the time to write it by hand) ?
__________________________
Regards
Umesh Balani
----------------------------------------------------------- NOTICE
------------------------------------------------------------ This email and any files transmitted with it are confidential and are solely
for the use of the individual or entity to which it is addressed. Any use,
distribution, copying or disclosure by any other person is strictly
prohibited. If you receive this transmission in error, please notify the
sender by reply email and then destroy the message. Opinions, conclusions
and other information in this message that do not relate to official
business of NIIT shall be understood to be neither given nor endorsed by
NIIT. Any information contained in this email, when addressed to NIIT
Clients is subject to the terms and conditions in governing client contract.
_______________________________________________
Sip-implementors mailing list
[EMAIL PROTECTED]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
_______________________________________________ Sip-implementors mailing list [EMAIL PROTECTED] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
