Re: [Sofia-sip-devel] Sofia-sip on symbian

Thank you for your reply, I will test your suggestion tomorrow. test_nua.exe passed correctly with that darcs branch: http://people.collabora.co.uk/~alban/darcs/sofia-sip-alban-linkage/ (for viewing patchs: http://monkey.collabora.co.uk/sofia-sip-alban-linkage/ ) The first patch fixs the bug in m

[Sofia-sip-devel] sofia-sip changes (2008-02-26)

This posting was generated automatically from darcs repo . Tue Feb 26 20:02:06 EET 2008 [EMAIL PROTECTED] * nua_session.c: determine INVITE overlap with re-INVITEs, too M ./libsofia-sip-ua/nua/nua_session.c -6 +3 Tue Feb 26 19:45:52 EET 2008 [EMAIL P

Re: [Sofia-sip-devel] Sofia-sip on symbian

2008/2/26, Alban Crequy <[EMAIL PROTECTED]>: > > I think the static variable is initialized before the DLL linkage is > > complete. > > It makes sense. Do you think this problem occurs only on the simulator, > or also on the device ? (I only tested the simulator.) I have no idea, but I think

Re: [Sofia-sip-devel] sofia-sip changes (2008-02-12)

2008/2/18, [EMAIL PROTECTED] <[EMAIL PROTECTED]>: > >Tue Feb 12 21:26:26 EET 2008 [EMAIL PROTECTED] > > * tport.c: tport_name_dup() now validates the input > > > >M ./libsofia-sip-ua/tport/tport.c +3 > > So, a null tpn_port field is not allowed? > Any idea on what might cause it to be NU

[Sofia-sip-devel] [ sofia-sip-Bugs-1827511 ] Don't terminate if BYE was restarted with nua_authenticate()

Bugs item #1827511, was opened at 2007-11-07 15:18 Message generated for change (Comment added) made by ppessi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=756076&aid=1827511&group_id=143636 Please note that this message will contain a full copy of the comment th

Re: [Sofia-sip-devel] REFER without auto answer?

Thx! Am Dienstag, den 26.02.2008, 17:32 +0200 schrieb Pekka Pessi: > 2008/2/26, Bernhard Suttner <[EMAIL PROTECTED]>: > > is it possible that sofia sip does not send the auto answer to a > > incoming REFER? In my case sofia sip does always response with 202 > > ACCEPTED without a possibility t

[Sofia-sip-devel] Sofia Crash

Hello, I am using Sofia 1.12.6 and using nta directly. I have written a server for our system. Sofia crashes. The problem I believe is that there is too many threads opened. In point #11 below I call auth_mod_check_client. The problem seams to me that to many people try to REGISTER but they fail

Re: [Sofia-sip-devel] REFER without auto answer?

2008/2/26, Bernhard Suttner <[EMAIL PROTECTED]>: > is it possible that sofia sip does not send the auto answer to a > incoming REFER? In my case sofia sip does always response with 202 > ACCEPTED without a possibility to change the response value in the > nua_i_refer callback function. I want t

[Sofia-sip-devel] REFER without auto answer?

Hi folks, is it possible that sofia sip does not send the auto answer to a incoming REFER? In my case sofia sip does always response with 202 ACCEPTED without a possibility to change the response value in the nua_i_refer callback function. I want to respond with FORBIDDEN in some cases. I think t

Re: [Sofia-sip-devel] Sofia-sip on symbian

Le Mon, 25 Feb 2008 15:43:44 +0200, "Pekka Pessi" <[EMAIL PROTECTED]> a écrit : > 2008/2/21, Alban Crequy <[EMAIL PROTECTED]>: (...) > > I tried to fix it but then test_nua.exe just crashes as soon as it > > gets started. My breakpoint in the main() function is not > > triggered: it crashes befor

Re: [Sofia-sip-devel] Replaces header and 407 Proxy Authentication Required

2008/2/26, Alberto Takeshi Mayama <[EMAIL PROTECTED]>: > I learned the network is set to block TCP traffic, therefore, Sofia was not > able to open connection to the server. > Then, since it haven't received RST from the server it didn't retry using > UDP. So Sofia is strictly obeying the above

Re: [Sofia-sip-devel] Replaces header and 407 Proxy Authentication Required

Pekka Pessi wrote: 2008/2/19, Alberto Takeshi Mayama <[EMAIL PROTECTED]>: Sorry, my mistake. Sofia is indeed trying to send the message. It turned out, the INVITE containing the additional authentication data was too large: INVITE (95600833) too large for UDP, trying TCP so it was trying