Re: [Sofia-sip-devel] call-ID troubles
Hello Michael, you mean the "tag" in the from header? or the sofia tags? here is the code used to send the re-invite nua_invite(nh, TAG_IF(!proxyAddress.isEmpty(), NUTAG_PROXY(proxyAddress.toLatin1().constData())), NUTAG_AUTOANSWER(0), TAG_IF(!options.isDataCall(), SOATAG_USER_SDP_STR(sdp.toLatin1().constData())), SIPTAG_PRIORITY_STR(m_mapPriorityStrings[prio].toLatin1().constData()), TAG_END()); i am not manipulating the callid at all On Wed, May 25, 2016 at 5:26 PM, Michael Jerris <m...@jerris.com> wrote: > I would triple check the strings you are putting into the tags for this. > I have never seen something like this unless it was actually me somehow > buffer overflowing into it. > > > On May 25, 2016, at 11:16 AM, Francesco Lamonica <alienpeng...@gmail.com> > wrote: > > Hello Michael, > sorry, obviously i meant SIP :) > > > On Sun, May 15, 2016 at 12:02 AM, Michael Jerris <m...@jerris.com> wrote: > >> Callid in sdp? >> >> >> On Saturday, May 14, 2016, Francesco Lamonica <alienpeng...@gmail.com> >> wrote: >> >>> Hi all, i know this might be a shot in the dark however... >>> i am experiencing a strange issue, randomically on a UAC that uses >>> sofia-sip (latest stable from repository) when putting the remote on-hold. >>> the scenario is the following >>> >>> sofia-uac -> invites >>> 100 >>> 180 >>> 200 >>> sofia-uac -> on hold (changing the sdp manually and resending the invite) >>> sofia-uac -> not on hold >>> >>> this scenario 1 out of 20/30 calls does a very strange thing >>> the SDP that is sent out has the wrong callid so the remote party >>> responds correctly with a series of 481 >>> >>> the callid is mangled this way: >>> the correct one is like 01234567890@172.16.17.15 >>> while the one sent is 01234567890@17217.117.15 >>> as if the second octet is overwritten by following parts of the address >>> >>> has anyone experienced something like that? or can give me some hints? >>> thanks a lot >>> >> > > -- Mobile security can be enabling, not merely restricting. Employees who bring their own devices (BYOD) to work are irked by the imposition of MDM restrictions. Mobile Device Manager Plus allows you to control only the apps on BYO-devices by containerizing them, leaving personal data untouched! https://ad.doubleclick.net/ddm/clk/304595813;131938128;j___ Sofia-sip-devel mailing list Sofia-sip-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sofia-sip-devel
Re: [Sofia-sip-devel] call-ID troubles
Hello Michael, sorry, obviously i meant SIP :) On Sun, May 15, 2016 at 12:02 AM, Michael Jerris <m...@jerris.com> wrote: > Callid in sdp? > > > On Saturday, May 14, 2016, Francesco Lamonica <alienpeng...@gmail.com> > wrote: > >> Hi all, i know this might be a shot in the dark however... >> i am experiencing a strange issue, randomically on a UAC that uses >> sofia-sip (latest stable from repository) when putting the remote on-hold. >> the scenario is the following >> >> sofia-uac -> invites >> 100 >> 180 >> 200 >> sofia-uac -> on hold (changing the sdp manually and resending the invite) >> sofia-uac -> not on hold >> >> this scenario 1 out of 20/30 calls does a very strange thing >> the SDP that is sent out has the wrong callid so the remote party >> responds correctly with a series of 481 >> >> the callid is mangled this way: >> the correct one is like 01234567890@172.16.17.15 >> while the one sent is 01234567890@17217.117.15 >> as if the second octet is overwritten by following parts of the address >> >> has anyone experienced something like that? or can give me some hints? >> thanks a lot >> > -- Mobile security can be enabling, not merely restricting. Employees who bring their own devices (BYOD) to work are irked by the imposition of MDM restrictions. Mobile Device Manager Plus allows you to control only the apps on BYO-devices by containerizing them, leaving personal data untouched! https://ad.doubleclick.net/ddm/clk/304595813;131938128;j___ Sofia-sip-devel mailing list Sofia-sip-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sofia-sip-devel
[Sofia-sip-devel] call-ID troubles
Hi all, i know this might be a shot in the dark however... i am experiencing a strange issue, randomically on a UAC that uses sofia-sip (latest stable from repository) when putting the remote on-hold. the scenario is the following sofia-uac -> invites 100 180 200 sofia-uac -> on hold (changing the sdp manually and resending the invite) sofia-uac -> not on hold this scenario 1 out of 20/30 calls does a very strange thing the SDP that is sent out has the wrong callid so the remote party responds correctly with a series of 481 the callid is mangled this way: the correct one is like 01234567890@172.16.17.15 while the one sent is 01234567890@17217.117.15 as if the second octet is overwritten by following parts of the address has anyone experienced something like that? or can give me some hints? thanks a lot -- Mobile security can be enabling, not merely restricting. Employees who bring their own devices (BYOD) to work are irked by the imposition of MDM restrictions. Mobile Device Manager Plus allows you to control only the apps on BYO-devices by containerizing them, leaving personal data untouched! https://ad.doubleclick.net/ddm/clk/304595813;131938128;j___ Sofia-sip-devel mailing list Sofia-sip-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sofia-sip-devel
[Sofia-sip-devel] mac os retransmission bug?
Hi all, i noticed a very strange behaviour on latest sofia (last packaged one): On mac os x (ranging from snow leopard to mavericks) if a request message like INFO is lost (i encountered with an unstable wifi link and later tested by simply disconnecting the uplink cable of the router attached to my mac) then no retrasmission is done, and no more INFO can be sent, the API gets called but nothing goes on the link. The bug(?) does not affect windows or linux builds of sofia. Enabling stack debug info i noticed that none of the various tport messages get printed. Btw the stack automatically keeps acknowledging incoming INFO, OPTIONS and other request coming from other parties. Does anyone have any insight on the subject? regards -- Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available Simple to use. Nothing to install. Get started now for free. http://p.sf.net/sfu/SauceLabs___ Sofia-sip-devel mailing list Sofia-sip-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sofia-sip-devel
Re: [Sofia-sip-devel] Controlling Source IP Address
Hi Jerry, did you solve the problem? i might have the same issue with the VPN On Wed, May 23, 2012 at 8:41 PM, Jerry Richards jerry.richa...@teotech.comwrote: I have a Freeswitch issue, where I have softphones connected to two separate subnets (one on eth0 and the other on eth1). When I send an IM (i.e. SIP MESSAGE) from the eth1 phone to the eth0 phone, a wireshark trace shows the source IP address of the eth1 server address, rather than the eth0 server address. The eth1 address makes no sense on the eth0 subnet, so the softphone does not reply. ** ** Is there a sofia tag to control the source IP in this case? The message is going out the right interface; the issue is just that the source IP address is wrong. ** ** Thanks, Jerry -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Sofia-sip-devel mailing list Sofia-sip-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sofia-sip-devel -- Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and remains a good choice in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev___ Sofia-sip-devel mailing list Sofia-sip-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sofia-sip-devel
Re: [Sofia-sip-devel] Binding on 0.0.0.0 and sending to 127.0.0.1
what if he does not know the correct route? On Thu, Sep 13, 2012 at 8:58 PM, Michael Jerris m...@jerris.com wrote: Don't bind to 0.0.0.0. Bind to the interface address of the network device that you want to show up in your sip packets. Mike On Sep 12, 2012, at 10:47 PM, Huang, Kun-Yao kxh...@dolby.com wrote: Hello: If I use call nua_create() with sip:0.0.0.0:* and then call nua_invite() to another process listening at port 5060, I always get 503 service unavailable. Am I doing something wrong? su_log_set_level(su_log_default, SU_LOG_MAX); su_log_set_level(su_log_global, SU_LOG_MAX); su_log_redirect(su_log_global, logger_callback, NULL); su_log_redirect(su_log_default, logger_callback, NULL); su_init(); root = su_root_create(NULL); nua = nua_create(root, callback, NULL, NUTAG_URL(sip:0.0.0.0:*), TAG_NULL()); handle = nua_handle(nua, NULL, TAG_END()); nua_invite(handle, SIPTAG_TO_STR(sip:127.0.0.1:5060), SOATAG_USER_SDP_STR(sdp), NUTAG_AUTOACK(1),TAG_END()); su_root_run(root); -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Sofia-sip-devel mailing list Sofia-sip-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sofia-sip-devel -- Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and remains a good choice in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev___ Sofia-sip-devel mailing list Sofia-sip-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sofia-sip-devel
[Sofia-sip-devel] nua_shutdown timeout
Hi all, sofia responded with a 500 status message to my nua_shutdown() call. This seems to happen randomly on a linux machine that has a NIC that is configured with multiple aliases (eth0, eth0:0, eth0:1) and two VLANs bound to the same physical NIC. what is the recommended practice? should i try the nua_shutdown again? can i destroy the nua nonetheless? any hints on how to track down the problem? thanks -- This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure___ Sofia-sip-devel mailing list Sofia-sip-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sofia-sip-devel
Re: [Sofia-sip-devel] problem shutting down nua
On Wed, Feb 24, 2010 at 12:48 PM, elisa_murgia elisa_mur...@libero.itwrote:
Hello Francesco, hi all,
have you solve your problem? I'm also having problem to get nua_r_shutdown
signal, handling the eventloop with su_root_step. I'm using sofia 1.12.10 at
the moment.
The problem is that, after executing nua_shutdown(nua), I never get case
nua_r_shutdown inside my callback:
event_callback(nua_event_t event,
int status,
char const *phrase,
nua_t *nua,
nua_magic_t *magic,
nua_handle_t *nh,
nua_hmagic_t *hmagic,
sip_t const *sip,
tagi_t tags[])
{
...
switch(event){
...
case nua_r_shutdown:
printf(got nua_r_shutdown\n);
break;
}
}
This sounds really weird to me, cause when setting NUA_DEBUG= 9,
NTA_DEBUG=9, as Pekka suggested, I can see that signal is sent.
nta: timer not set
nua: nua_shutdown: entering
nua((nil)): recv signal r_shutdown
nua: nua_stack_shutdown: entering
soa_destroy(static::0x10d02c0) called
soa_destroy(static::0x1128130) called
tport_destroy(0x10d2610)
nua((nil)): event r_shutdown 200 Shutdown successful
nua((nil)): sent signal r_shutdown
nua: nua_unregister: entering
nua: nua_destroy: entering
nua_destroy(0x10ced80): FATAL: nua_shutdown not completed
client: su_root.c:432: su_root_destroy: Assertion
`(self-sur_task-sut_port su_port_own_thread(self-sur_task-sut_port))'
failed.
While debbuging, I notice that nua-nua_final_shutdown is never set, so the
fatal error when calling nua_destroy().
Where can I be wrong? Any help would be very appreciated.
Hi Elisa,
unfortunately i can't help you that much, i am using latest sofia-repo but i
am experiencing the very same behaviour you're reporting, i can see the
r_shutdown signal but the nua_r_shutdown is never reported by the callback.
regards
Francesco
--
Download Intel#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev___
Sofia-sip-devel mailing list
Sofia-sip-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sofia-sip-devel
[Sofia-sip-devel] different behaviour on win32 and linux
Hi, i just noticed that there is a difference between the way NUTAG_APPL_METHOD() and NUTAG_ALLOW_METHOD() are handled on linux (amd64 gentoo and ubuntu 9.04) and win32 (msvc 2008) are handled by compilers: On windows (following what is written in the documentation) i use nua_set_params(nua, NUTAG_APPL_METHOD(NULL), TAG_END()); but this does not compile on linux where the only way to make the code compile is to use nua_set_params(nua, NUTAG_APPL_METHOD(), TAG_END()); any ideas? thanks -- The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com___ Sofia-sip-devel mailing list Sofia-sip-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sofia-sip-devel
Re: [Sofia-sip-devel] Fw: Changing IP address.
Hello Robert, may i ask what platform and sofia version are use using? I am facing the same issue but i dont'even get the nua_r_shutdown message... thanks On Thu, Oct 1, 2009 at 11:28 PM, Robert Han robert...@vtech.ca wrote: Hi, I just want to raise the issue that we asked you earlier back in July 31 (see below). You said that if we shutdown the sofia stack, and if there are outstanding sip sessions (for example 4 active sessions), we do not need to nua_bye() or even nua_handle_destroy() before invoking nua_shutdown(). according to your reply, the nua stack is guaranteed to terminate outstanding nua operations, and then publish nua_i_terminate as the final event with a operation handle, so that we can destroy that handle. that never happened. our logs below an IP address change, where we had to recycle the Sofia sip stack: our link status monitor reports an IP address change, so we proceed to recycle our Sofia stack: -NTC-[20021020:112634.600]| 104||cc||sip.fe |DevCoordStatusChange: SIP: NETWORK UP -NTC-[20021020:112634.600]| 104||cc||sip.fe |DevCoordStatusChange: Network Link Recycled == possible new IP address change -NTC-[20021020:112634.600]| 104||cc||sip.fe |DevCoordStatusChange: IP address changed from 192.168.0.52 to 192.168.0.77. -NTC-[20021020:112634.610]| 104||cc||sip.fe |DevCoordStatusChange: Need to recycle Sophia Stack === shutting down the Sophia SIP stack... IsSofiaStackShuttingDown = TRUE; VT_NOTICE(Shutting down the Sofia SIP Stack...); nua_shutdown(PortPtr-sofiaStackPtr); *=== now i expect Sofia stack to terminate the nua operation for each outstanding sip session with nua_i_terminated before receiving nua_r_shutdown * *completion status , but we don't get it hence we don't destroy the nua handle.* DBG [20021020:112635.680]| 168||SIP Event Handler||sip.fe |EventCallback: Received an event = ['nua_r_shutdown'] status = [100 ,'Shutdown started'] on port [5060]. Handle = [(nil)], HMagic = (nil). -NTC-[20021020:112635.680]| 168||SIP Event Handler||sip.fe |EventCallback: Sophia SIP stack shutdown started successfully. DBG [20021020:112635.810]| 168||SIP Event Handler||sip.fe |EventCallback: Received an event = ['nua_r_shutdown'] status = [200 ,'Shutdown successful'] on port [5060]. Handle = [(nil)], HMagic = (nil). -NTC-[20021020:112635.810]| 168||SIP Event Handler||sip.fe |EventCallback: Sophia SIP stack shutdown completed successfully. -NTC-[20021020:112635.820]| 168||SIP Event Handler||sip.fe |EventCallback: --- StartSipStack() nta_agent: received garbage from udp/192.168.0.77:5060/sip nta_agent: received garbage from udp/127.0.0.1:5060/sip -NTC-[20021020:112635.850]| 168||SIP Event Handler||sip.fe |EventCallback: --- StartSipStack() DBG [20021020:112635.850]| 168||SIP Event Handler||sip.fe |EventCallback: Received an event = ['nua_r_set_params'] status = [200 ,'OK'] on port [5060]. Handle = [(nil)], HMagic = (nil). DBG [20021020:112635.850]| 168||SIP Event Handler||sip.fe |EventCallback: Discarding event nua_r_set_params. Handler not implemented. because we don't recieve the nau_i_terminate, we have a *stale* handle on our side, where we did not destroy it, but our client-side binding Session context object is already deleted. would that be a bug? is the Sofia stack suppose to behave as described above?? thanks, Robert Han, Senior Software Engineer VTech Technologies Canada, Ltd. - Forwarded by Robert Han/ENG/VTNCAN/VTECH on 10/01/2009 02:01 PM - *Jen Chitty* 07/31/2009 12:01 PM To:Robert Han/ENG/VTNCAN/vt...@vtech cc: Subject:Fw: [Sofia-sip-devel] Changing IP address. - Forwarded by Jen Chitty/ENG/VTNCAN/VTECH on 07/31/2009 11:57 AM - *Michael Jerris m...@jerris.com* 07/31/2009 11:47 AM To:Jen Chitty jenchi...@vtech.ca cc:sofia-sip-devel sofia-sip-devel@lists.sourceforge.net Subject:Re: [Sofia-sip-devel] Changing IP address. On Jul 31, 2009, at 2:23 PM, Jen Chitty wrote: Hi, I'm wondering if there's a way to change the IPv4 address that the Sofia stack binds to without having to shutdown and restart the stack. We're using the NUA. Nope, but would be nice. Right now, if our device's IPv4 address changes we shutdown the Sofia stack and start it up again. This seems to mostly work, but we are experiencing some race conditions with callbacks from the Sofia event loop thread (running su_root_run) and our application thread, especially with respect to handle destruction. We were hoping that we could just leave the Sofia stack running and tell it to change its IPv4 address. Another question that I'd like an answer to is this: When shutting down the Sofia stack, are we guaranteed to receive a nua_i_terminated event for every
Re: [Sofia-sip-devel] problem shutting down nua
On Mon, Sep 28, 2009 at 4:44 PM, Francesco Lamonica alienpeng...@gmail.com wrote: On Thu, Sep 24, 2009 at 9:57 AM, Pekka Pessi ppe...@gmail.com wrote: 2009/9/23 Francesco Lamonica alienpeng...@gmail.com: hi ppl, i am having some problems in shutting down the nua; i am still using sofia 1.12.9 and i am handling the eventloop with su_root_step. I read on the list the procedure pessi suggested: 1. call nua_shutdown(mynua) 2. wait for nua_r_shutdown with status code 200 then 3. call nua_destroy 4. break out of event loop (this should not be necessary in my case right?) 5. then call su_deinit() my problem is that i never get the nua_r_shutdown, with any status what can i check? That sounds weird. Best you can do is to enable more detailed debugging output (e.g., env vars NUA_DEBUG=9 NTA_DEBUG=9) and try to see where the execution hangs within the stack. Hi all, this is what i get (with latest darcs) when i call nua_shutdown(nua); tport_tsend(0x1a961b0) tpn = */192.168.23.200:5060/sip tport_resolve addrinfo = 192.168.23.200:5060 tport_by_addrinfo(0x1a961b0): not found by name */192.168.23.200:5060/sip tport_vsend(0x1a961b0): 693 bytes of 693 to udp/192.168.23.200:5060 tport_vsend returned 693 tport_pend(0x1a961b0): pending 0x7f8d4801add0 for udp/192.168.23.2:5080 (already 0) shutdown result: 0 tport_wakeup_pri(0x1a961b0): events IN tport_recv_event(0x1a961b0) tport_recv_iovec(0x1a961b0) msg 0x7f8d480197d0 from (udp/192.168.23.2:5080) has 430 bytes, veclen = 1 tport_deliver(0x1a961b0): msg 0x7f8d480197d0 (430 bytes) from udp/192.168.23.200:5080/sip next=(nil) tport_release(0x1a961b0): 0x7f8d4801add0 by 0x7f8d480173a0 with 0x7f8d480197d0 (preliminary) tport_wakeup_pri(0x1a961b0): events IN tport_recv_event(0x1a961b0) tport_recv_iovec(0x1a961b0) msg 0x7f8d480197d0 from (udp/192.168.23.2:5080) has 506 bytes, veclen = 1 tport_deliver(0x1a961b0): msg 0x7f8d480197d0 (506 bytes) from udp/192.168.23.200:5080/sip next=(nil) tport_release(0x1a961b0): 0x7f8d4801add0 by 0x7f8d480173a0 with 0x7f8d480197d0 tport_destroy(0x1ad7650) still no nua_r_shutdown received in my callback any suggestions? -- Come build with us! The BlackBerryreg; Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9#45;12, 2009. Register now#33; http://p.sf.net/sfu/devconf ___ Sofia-sip-devel mailing list Sofia-sip-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sofia-sip-devel
Re: [Sofia-sip-devel] problem shutting down nua
On Thu, Sep 24, 2009 at 9:57 AM, Pekka Pessi ppe...@gmail.com wrote: 2009/9/23 Francesco Lamonica alienpeng...@gmail.com: hi ppl, i am having some problems in shutting down the nua; i am still using sofia 1.12.9 and i am handling the eventloop with su_root_step. I read on the list the procedure pessi suggested: 1. call nua_shutdown(mynua) 2. wait for nua_r_shutdown with status code 200 then 3. call nua_destroy 4. break out of event loop (this should not be necessary in my case right?) 5. then call su_deinit() my problem is that i never get the nua_r_shutdown, with any status what can i check? That sounds weird. Best you can do is to enable more detailed debugging output (e.g., env vars NUA_DEBUG=9 NTA_DEBUG=9) and try to see where the execution hangs within the stack. Hi Pekka, i did set those two env vars but nothing happens when i call nua_shutdown(nua) it seems like going unnoticed. There's nothing printed in the debug output... after a few secs the printfs of new registration happen and that's all. thanks -- Come build with us! The BlackBerryreg; Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9#45;12, 2009. Register now#33; http://p.sf.net/sfu/devconf ___ Sofia-sip-devel mailing list Sofia-sip-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sofia-sip-devel
[Sofia-sip-devel] problem shutting down nua
hi ppl, i am having some problems in shutting down the nua; i am still using sofia 1.12.9 and i am handling the eventloop with su_root_step. I read on the list the procedure pessi suggested: 1. call nua_shutdown(mynua) 2. wait for nua_r_shutdown with status code 200 then 3. call nua_destroy 4. break out of event loop (this should not be necessary in my case right?) 5. then call su_deinit() my problem is that i never get the nua_r_shutdown, with any status what can i check? thanks -- Come build with us! The BlackBerryreg; Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9#45;12, 2009. Register now#33; http://p.sf.net/sfu/devconf ___ Sofia-sip-devel mailing list Sofia-sip-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sofia-sip-devel
Re: [Sofia-sip-devel] Problem compiling a little application with visual studio 2005
Hi Stefano, I am no VS2005 expert either but i had a few problems on lib dependencies as well, what windows lib are you linking against right now? (you can check it in the project properties under the LINKER section) On Thu, Sep 18, 2008 at 5:27 PM, Stefano Sabatini [EMAIL PROTECTED] wrote: Hi all, I'm getting this building problems when compiling a little application with Visual Studio 2005 on Windows Vista which links against libsofia-sip (last checkout, 1.12.9). I got so far to compile libsofia-ua for win32 without hassles. These are the errors I get when compiling: 1Linking... 1 Creating library .\Debug/sip_options_static.lib and object .\Debug/sip_options_static.exp 1libsofia_sip_ua_static.lib(sres.obj) : error LNK2019: unresolved external symbol [EMAIL PROTECTED] referenced in function _sres_parse_win32_ip 1libsofia_sip_ua_static.lib(sres.obj) : error LNK2019: unresolved external symbol [EMAIL PROTECTED] referenced in function _sres_parse_win32_reg 1libsofia_sip_ua_static.lib(sres.obj) : error LNK2019: unresolved external symbol [EMAIL PROTECTED] referenced in function _sres_parse_win32_reg 1libsofia_sip_ua_static.lib(sres.obj) : error LNK2019: unresolved external symbol [EMAIL PROTECTED] referenced in function _sres_parse_win32_reg_parse_dnsserver 1libsofia_sip_ua_static.lib(su_localinfo.obj) : error LNK2019: unresolved external symbol [EMAIL PROTECTED] referenced in function _win_localinfo 1.\Debug/sip_options_static.exe : fatal error LNK1120: 5 unresolved externals 1Build log was saved at file://c:\Users\fooobar\Documents\programmi\sofia-sip-1.12.9\win32\utils\sip_options_static\Debug\BuildLog.htm 1sip_options_static - 6 error(s), 0 warning(s) I think the problem derives from some missing libs/DLLs, can you suggest how to fix the problem (for example which are the libs/DLLs I'm missing if that's the case)? (Sorry I'm definitively not a Visual Studio expert). Many thanks in advance, best regards. - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ Sofia-sip-devel mailing list Sofia-sip-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sofia-sip-devel - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ Sofia-sip-devel mailing list Sofia-sip-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sofia-sip-devel
Re: [Sofia-sip-devel] Fwd: Problems on win32 with latest window SDK
On Jan 11, 2008 4:01 PM, Michael Jerris [EMAIL PROTECTED] wrote: Hi Mike, are you sure this fix is enough? the _WIN32_WINNT is defined to at least 0x501 so it enters that branch and does not complain about the missing headers from the 'else' branch, but i am not certain it would work with ipv6 (i dont use it so i cannot check) since the IPPROTO_IPV6 macro is defined within an enum in w2defs.h so IPPROTO_IPV6 is still not defined (but i don't know if it is still needed) My fix for this one is: Index: sofia-sip/su.h === --- sofia-sip/su.h (revision 6643) +++ sofia-sip/su.h (revision 6644) @@ -67,7 +67,7 @@ # include winsock2.h # include ws2tcpip.h # if SU_HAVE_IN6 -#if defined(IPPROTO_IPV6) +#if defined(IPPROTO_IPV6) || (_WIN32_WINNT = 0x0600) /* case 1: IPv6 defined in winsock2.h/ws2tcpip.h */ #else /* case 2: try to use IPv6 Tech Preview */ it should not require additional includes beyond this. Mike - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ Sofia-sip-devel mailing list Sofia-sip-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sofia-sip-devel
[Sofia-sip-devel] Problems on win32 with latest window SDK
Hi, i found a problem on win32 with the latest windows SDK (the one with vista support) in su.h (line 73 - sofia 1.12.7) it does not enter in the then branch of the #if defined(IPPROTO_IPV6) and tries to use the nonexistent tpipv6.h thing is that with previous windows platform sdk (windows server 2003 R2) the IPPROTO_IPV6 was defined in the winsock2.h header file (included from su.h) hence the definition was correctly found) thanks - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ Sofia-sip-devel mailing list Sofia-sip-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sofia-sip-devel
[Sofia-sip-devel] INVITE retransmitted every 25 minutes
Hi, i am using sofia-sip 1.12.5 on win32 and i noticed that every 25 minutes the stack resends the INVITE on the handle relative to the ongoing call. Is that normal behaviour? if so, is it possible to disable it? or change the timeout? - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Sofia-sip-devel mailing list Sofia-sip-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sofia-sip-devel
[Sofia-sip-devel] Possible bug in deallocating resources?
As i said in the other email i am just starting using sofia-sip so it is most likely that i did something wrong.. however i stumbled into a reproducible crash: win32 VS2005 sofia-sip 1.12.5work1 the sip options example from the wiki i changed the event loop from su_root_run(root); to for (int i=0; i2, i++) su_root_step(root,200); so that i should just get the first 2 events and then proceed to the end of the program but it crashes in the line: nua_destroy (nua); i tried also the following: 1) keep the su_root_run(root); loop 2) copied into a global variable myroot the su_root_t object created: root = su_root_create (NULL); myroot=root; 3) then as the last statement of the event callback i added: su_root_break(myroot); it correctly exits the event loop but crashes on the same line as above. My fault or a bug? thanks - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ Sofia-sip-devel mailing list Sofia-sip-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sofia-sip-devel
