Hi,

Please ignore this request. We were not calling su_root_threading(app->root, 0) 
after su_create_root().

thanks,
mayank

________________________________________
From: Mayank Khetan
Sent: Friday, February 01, 2008 10:56 AM
To: sofia-sip-devel@lists.sourceforge.net
Cc: Subbu Rajendran
Subject: No return from nua_create()

Hi,

We are using sofia-sip-1.12.6 on uCLinux 2.4.26 on a MIPS32 platform.

We do not see any return from nua_create() as shown below:

starting Sofia SIP
sip main loop starting
SIP Initializing...
su_init successful
going to start su_home_init
going to start su_root_create
su_socket_port_init(0x10002788, 0x2ac86680) called
su_pthread_port_init(0x10002788, 0x2ac86680) called
su_root_create passed
Calling sip Create
nua: nua_create: entering
su_port_create(): epoll_create() => 4294967295: Function not implemented
su_socket_port_init(0x100033c0, 0x2ac86680) called
su_pthread_port_init(0x100033c0, 0x2ac86680) called
nua: nua_stack_init: entering
nua: nua_stack_set_params: entering
soa_create("default", 0x10003590, 0x10007ec8) called
soa_set_params(static::0x10008260, ...) called
nta_agent_create: initialized hash tables
nta_agent_create: initialized transports
nta_agent_create: initialized random identifiers
nta_agent_create: initialized timer
nta_agent_create: initialized resolver
tport_create(): 0x10009408
nta: master transport created
tport_bind_server(0x10009408) to */192.168.0.10:5080/sip
tport_bind_server(0x10009408): calling tport_listen for udp
tport_alloc_primary(0x10009408): new primary tport 0x100097e0
tport_listen(0x100097e0): listening at udp/192.168.0.10:5080/sip
tport_bind_server(0x10009408): calling tport_listen for tcp
tport_alloc_primary(0x10009408): new primary tport 0x10009a60
tport_listen(0x10009a60): listening at tcp/192.168.0.10:5080/sip
nta: bound to (192.168.0.10:5080;transport=*)
nta: agent_init_via: SIP/2.0/udp 192.168.0.10:5080 (sip)
nta: agent_init_via: SIP/2.0/tcp 192.168.0.10:5080 (sip)
nta: agent_init_via: SIP/2.0/tcp 192.168.0.10:5080 (sip)
nta: Via fields initialized
nta: Contact header created
nua_register: Adding contact URL '192.168.0.10' to list.

< No return after the above >

To start with a simple application, we are calling all the sofia sip 
initialization
functions in the same thread. We are waiting for the nua_create() to be 
successful
before calling nua_set_params() and su_root_run(). We have also tried running
su_root_create(), nua_create(), nua_set_params() in a separate thread from the 
application
but ended up into the same result.

The logic mentioned above worked for windows but when we ported it on this 
uCLinux platform, it failed.

Please let us know if more information is required.

thanks and regards,
mayank

**************** CAUTION - Disclaimer *****************
This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely 
for the use of the addressee(s). If you are not the intended recipient, please 
notify the sender by e-mail and delete the original message. Further, you are 
not to copy, disclose, or distribute this e-mail or its contents to any other 
person and any such actions are unlawful. This e-mail may contain viruses. 
Infosys has taken every reasonable precaution to minimize this risk, but is not 
liable for any damage you may sustain as a result of any virus in this e-mail. 
You should carry out your own virus checks before opening the e-mail or 
attachment. Infosys reserves the right to monitor and review the content of all 
messages sent to or from this e-mail address. Messages sent to or from this 
e-mail address may be stored on the Infosys e-mail system.
***INFOSYS******** End of Disclaimer ********INFOSYS***

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Sofia-sip-devel mailing list
Sofia-sip-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sofia-sip-devel

Reply via email to