< Previous by Date | Date Index | Next by Date > |
< Previous in Thread | Thread Index |
For understanding why the code is the way it is (and what your code needs to do), read more about forking in RFC3261.
RjS On Nov 7, 2008, at 12:24 PM, Adam Roach wrote:
On 11/7/08 12:12 PM, Vasanthi wrote:Can somebody shed light on what is the advantage in having DialogSetId (FromTag and CallId) against just CallId in maintaining SIP Call data ? I have an existing SIP system which uses SIP CallId to maintain Call data andI see that reSIProcate uses DialogSetId. What I'm gaining by using DialogSetId ?Protocol compliance. /a _______________________________________________ resiprocate-users mailing list resiprocate-users@xxxxxxxxxxxxxxx List Archive: http://list.resiprocate.org/archive/resiprocate-users/
Attachment:
smime.p7s
Description: S/MIME cryptographic signature