> I think this is how the SipX PBX is implemented and from what I have
read on the list, this is how the RFCs for SIP are written.
Well, I'm not considering the proxy side. I'm only looking at the
application side. And as far as I know, sipX pbx is rather meant to be a
proxy-side solution. Similarly it seems to me that the RFC defines the
application side (UAs - which can be UA Client and UA Server) and the
proxy side (proxies).
> It seems to me what you are "defining" is SIP.
Not exactly, I'm probably not crystal clear explaining what I would like
to do, let me try another way. I would like to define an implementation
of the application side of SIP that would be independent of any media. I
agree this is a plain implementation of a part of SIP as defined in RFC
3261 (e.g., in sections 8, 9.1, 9.2, 12, 13, 14, 15 - hey that's a large
part of the RFC :-).
So the question still remains, does it make sense to develop such a
thing, that would be shared by several media applications, each of them
providing their own SDP descriptions and associated media processing?
________________________________
Lionel Mallet - Gemalto
Tel: +33 (0)4 42 36 59 70
_______________________________________________
sipxtapi-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipxtapi-dev/
