Hi Jude,
Thanks, but it is far from enough, for as a SIP implementor(we do sip stack implementation), we need to know a complete state machin, about which events cause the dialog to which state. It is important, for transaction, the 3261 has given very detailed information. The minisip code has some dialog state machine, but I don’t know whether it is complete. Thanks. Bin Chen _____ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Thursday, November 23, 2006 1:25 PM To: Bin Chen Cc: [email protected]; [EMAIL PROTECTED] Subject: Re: [Sip-implementors] Dialog state machine Hi bin u can actually go through this line from 3261. u can also grep for the definitions of each tag in the below description A dialog contains certain pieces of state needed for further message transmissions within the dialog. This state consists of the dialog ID, a local sequence number (used to order requests from the UA to its peer), a remote sequence number (used to order requests from its peer to the UA), a local URI, a remote URI, remote target, a boolean flag called "secure", and a route set, which is an ordered list of URIs. The route set is the list of servers that need to be traversed to send a request to the peer. A dialog can also be in the "early" state, which occurs when it is created with a provisional response, and then transition to the "confirmed" state when a 2xx final response arrives. For other responses, or if no response arrives at all on that dialog, the early dialog terminates. Thanks & Regards Naveen Pinto ARICENT COMMUNICATION SYSTEMS off: 9180-41069025 mobile: 91-9448481804 "Bin Chen" <[EMAIL PROTECTED]> Sent by: [EMAIL PROTECTED] 11/23/2006 07:46 AM To <[email protected]> cc Subject [Sip-implementors] Dialog state machine Hi, In RFC3261, I found four state machines from transaction, but I can't find any state machine picture about dialog, and the dialog information are spread over a lot of RFCs, and I find a unique information about dialog processing? Thanks. ABAI _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors *********************** Aricent-Private *********************** "DISCLAIMER: This message is proprietary to Aricent and is intended solely for the use of the individual to whom it is addressed. It may contain privileged or confidential information and should not be circulated or used for any purpose other than for what it is intended. If you have received this message in error, please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly prohibited from using, copying, altering, or disclosing the contents of this message. Aricent accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus." _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
