Hi,
I found a weird problem that <unicast_addr>, <onwer id> <session id>
specified by application via SOATAG_USER_SDP_STR would be changed as other
value forcely by sofia internally.
Went through the stack, I caught the spotted code.
File : soa_static.c
Function: soa_offer_answer_step()
Code snippet :
if (local->sdp_origin) {
o->o_username = local->sdp_origin->o_username;
/* o->o_address = local->sdp_origin->o_address; */
}
if (!o->o_address)
o->o_address = c0;
local->sdp_origin = o;
if (soa_init_sdp_origin(ss, o, c_address) < 0) {
phrase = "Cannot Get IP Address for Media";
goto internal_error;
}
We can see, the code which expects to perform <unicast_addr> copy from user
sdp to local sdp which is finally used by sofia stack is commented out.
I don;t know why this is commented. Is there any speicial consideration?
This prevents application customized address being used by stack.
Also if you dive into function soa_init_sdp_origin, you will understand why
user specified <onwer id> and <session id> are not used as expected. Stack
always generates them
once again regardless whether application customizes them.
Thanks
Kandy
------------------------------------------------------------------------------
Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM)
software. With Adobe AIR, Ajax developers can use existing skills and code to
build responsive, highly engaging applications that combine the power of local
resources and data with the reach of the web. Download the Adobe AIR SDK and
Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com
_______________________________________________
Sofia-sip-devel mailing list
Sofia-sip-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sofia-sip-devel
