Sathish,
Actually I think the most reliable way to guarantee in order delivery would
be to collect the digits on the client side, and send them within one
request (e.g. as a parameter, in a specific header, etc)
Much like when you're 'dialing' a SIP URI that gets collected and put in an
INVITE (forgetting about the feature that lets you send a URI character by
character for the moment...)
Regards,
Jeroen
----- Original Message -----
From: "Dale Worley" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Thursday, August 04, 2005 8:29 PM
Subject: RE: [Sip-implementors] Query regarding inorder delivery of messages
From: sathish
I have some query regarding inorder delivery of messages.
Reliability and sequence of SIP messages is taken care of by the CSeq
header, which sequentially numbers them.
in an application like money transfer through phone..how can I
ensure that dialled digits( corresponds to amount to be
transferred ) goes exactly in order ?
That is a more exacting requirement, since most SIP systems use the DTMF
RTP
events, which are not SIP messages, and are not protected by CSeq. I
don't
know RTP, but I think the RTP packets have enough timestamping that you
can
put a sequence of DTMF events in order and ensure that you haven't lost
any
digits in the middle.
But it's an interestingly important requirement.
Dale
_______________________________________________
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
