I thought transaction identifier is via:branch. is it dialog id you are 
referring to?
Stateless is ok because for Dirty Invite you would receive ACK after you 
send a 4xx. And you can safely drop it.


From: Chrisil Joseph 
Arackaparambil<[EMAIL PROTECTED]>
To: [email protected]
Subject: [Sip-implementors] Malformed transaction identifiers
Date: Wed, 21 Jun 2006 17:41:12 +0530

Hi,

The Call-ID, To, From alongwith the CSeq headers are used as
transaction identifiers. Now, if a request arrives with one of these
headers as malformed or missing, what is the best way to handle and
respond to the request?

Even if we are able to manage to send a 400 Bad Request response, it
will be difficult to maintain the transaction state. Should we handle
the request statelessly in this case? Then it might not be possible to
respond correctly to retransmissions of the request.

Thanks,
Chrisil
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors


_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors

Reply via email to