Hi Diego,
As far as I have understood this. On receving Offer from either side the controller would open a pinhole for media that would be received from the UAC, and corresponding to this it would open another media pinhole on other side. This would mean that on receiving offer2 a pinhole described in offer2' would be opened and once answer2' is recieved a new pinhole answer2 would be opened by controller. This is what should be description (SDP) in the ACK.
regards
Rayees
[EMAIL PROTECTED] wrote: -----As far as I have understood this. On receving Offer from either side the controller would open a pinhole for media that would be received from the UAC, and corresponding to this it would open another media pinhole on other side. This would mean that on receiving offer2 a pinhole described in offer2' would be opened and once answer2' is recieved a new pinhole answer2 would be opened by controller. This is what should be description (SDP) in the ACK.
regards
Rayees
To: [email protected]
From: Diego Susa <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED]
Date: 06/12/2006 11:56AM
Subject: [Sip-implementors] RFC3725 3pcc doubts
Hi:
I'm trying to implement the Controller described in this RFC, but I've had just partial success after a few days of hard work.
I've managed to make "Flow I" work (Figure 1, in RFC's page 4).
But I don't understand some of the instructions at "Flow IV" (RFC's page 9). When it comes to manipulate: offer2 -> offer2' and answer2' -> answer2, I miss the point :-(
Could any one tell me which detailed changes should I do to the SDP info I've got from offer2 and answer2' ?
Does anyone know any document which gives some detail about these SIP messages ?
Is there any example source code doing this with any SIP library ?
Thanks in advance !
Diego
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
*****FSS-Private *****" DISCLAIMER: This message is proprietary to Flextronics Software Systems Limited (FSS) 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. FSS 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
