Off the top of my head, I'd think you'd need the following objects/structures:
- call context has state and all other data about the call
- call map to hold the call contexts mapped by call id most likely
- some sort of stack manager to start/stop the stack and have a call map
I normally use the state pattern for states where you'd have states like initial, ringing, answered, disconnecting, disconnected.
That is basic call stuff, not SIP specific.
On Tue, Sep 14, 2010 at 1:38 AM, Vijayalakshmi <vijayalakshmi@xxxxxxxxxxx> wrote:
Hi,
Iam trying to develop a SIP server in VxWorks. Please assist me with how to implement SIP in my Server. Where do I get these info...????
Thanks in Advance...!!!!
Lakshmi Marudhanayagam
_______________________________________________
Sipping mailing list https://www.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@xxxxxxxxxxxxxxx for questions on current sip
Use sip@xxxxxxxx for new developments of core SIP
_______________________________________________ Sipping mailing list https://www.ietf.org/mailman/listinfo/sipping This list is for NEW development of the application of SIP Use sip-implementors@xxxxxxxxxxxxxxx for questions on current sip Use sip@xxxxxxxx for new developments of core SIP
