Re: [Sofia-sip-devel] Issues with the new tport TLS code in 1.12.10

On Wed, 2009-02-11 at 07:03 -0600, Andrew Rechenberg Lists wrote: > Looks like su_inet_ntop isn't working in my case. The su_family is 528 > which defaults to su_seterrorno(EAFNOSUPPORT). I completely overlooked this earlier. Is the iPhone little endian? http://sofia-sip.sourceforge.net/refdocs

Re: [Sofia-sip-devel] Issues with the new tport TLS code in 1.12.10

> > > > Here are a working and non-working TPORT_LOG=9 (1.12.9 works, > > > 1.12.10/darcs HEAD doesn't). Not much more there than what I posted > > > initially (at least from my layperson's point of view :) ). > > Indeed. The silence is rather distrubing. > > > > > tport_listen(0x1029270): tport

Re: [Sofia-sip-devel] Handling in-dialog requets with NTA

2009/2/4 Saúl Ibarra : > I'm trying to get the control over in-dialog requets, but there is > something I'm doing wrong and I can't get to solve it. If you want to catch requests to particular dialog, use normal leg per dialog (without NO_DIALOG(1), of course). You need from/to/call_id/cseq as tag

Re: [Sofia-sip-devel] PATCH: add/fix more tls init logging

2009/2/12 Jarod Neuner : > Just trying to make tport_tls init a bit noisier. Thanks. Applied. -- Pekka.Pessi mail at nokia.com -- Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackle

Re: [Sofia-sip-devel] Issues with the new tport TLS code in 1.12.10

> > Here are a working and non-working TPORT_LOG=9 (1.12.9 works, > > 1.12.10/darcs HEAD doesn't). Not much more there than what I posted > > initially (at least from my layperson's point of view :) ). > Indeed. The silence is rather distrubing. > > > tport_listen(0x1029270): tport_setname(pf=2

[Sofia-sip-devel] sofia-sip changes (2009-02-12)

This posting was generated automatically from darcs repo . Thu Feb 12 15:17:08 EET 2009 Pekka Pessi * tport.c: return correct errno from tport_connect() Ignore-this: 862cf3e8ef5c17e9ac955dcdba317f1f M ./libsofia-sip-ua/tport/tport.c -2 +2 Thu Feb 1

Re: [Sofia-sip-devel] Issues with the new tport TLS code in 1.12.10

On Thu, 2009-02-12 at 09:18 -0600, Andrew Rechenberg Lists wrote: > Here are a working and non-working TPORT_LOG=9 (1.12.9 works, > 1.12.10/darcs HEAD doesn't). Not much more there than what I posted > initially (at least from my layperson's point of view :) ). Indeed. The silence is rather distr

[Sofia-sip-devel] PATCH: add/fix more tls init logging

Just trying to make tport_tls init a bit noisier. New patches: [tport_tls: add/fix some tls init logging Jarod Neuner **20090212180248] { hunk ./libsofia-sip-ua/tport/tport_tls.c 267 - tls_log_errors(1, "tls_init_context", 0); + tls_log_errors(3, "tls_init_context", 0); hunk ./libsofia-

Re: [Sofia-sip-devel] Stack crash when the IP on the device changes

> -Original Message- > From: Inca Rose [mailto:incar...@gmail.com] > Sent: Wednesday, February 11, 2009 4:31 PM > To: Pekka Pessi > Cc: sofia-sip-devel@lists.sourceforge.net > Subject: Re: [Sofia-sip-devel] Stack crash when the IP on the device > changes > > Hi; > I will grab the changes a

Re: [Sofia-sip-devel] Stack crash when the IP on the device changes

Here is the stack trace: abort __assert_rtn outgoing_create nta.c:7665 nta_outgoing_mcreate nua_base_client_request nua_base_client_trequest nua_register_client_request

Re: [Sofia-sip-devel] Issues with the new tport TLS code in 1.12.10

> > On Wed, 2009-02-11 at 09:01 -0600, Andrew Rechenberg Lists wrote: > > > tport_listen(0x1029630): tport_setname(pf=2, tls/(null)): Address > > > family not supported by protocol family > Interesting. Can you provide a log with TPORT_DEBUG set to 9? Here are a working and non-working TPORT_L

Re: [Sofia-sip-devel] Stack crash when the IP on the device changes

2009/2/12 Inca Rose : > I just patch the code with your two patches from last night and here are the > results: > -- It takes the right case in the switch ( TRY_FULL or ONLY_INFO ) > -- if NUA_NW_DETECT_TRY_FULL is set, the stack crash again with: > Assertion failed: (tport_name_is_resolved(orq->o

Re: [Sofia-sip-devel] NAT keep-alive

Hi, I have identified the problem now. The IMS server use two ports, one for service and answer (5081 in my case) and that what is used for REGISTER and INVITE and works like a charm. The other port (5082) is used for request initiated by the server. The OPTIONS sent will not be answered on 508

Re: [Sofia-sip-devel] IPv6 Link Address Bind Fail

2009/2/12 Jerry Richards : > Thank You. Adding the following line just prior to the bind() call in > tport_bind_socket() did the trick. The bind succeeds when passing it the > IPv6 Link Address or the IPv6 Global Address. > > su->su_sin6.sin6_scope_id = (unsigned long)if_nametoindex("esw0"); Coo

Re: [Sofia-sip-devel] do SDP negotiation in application level

Great thanks. On Thu, Feb 12, 2009 at 9:52 PM, Pekka Pessi wrote: > 2009/2/12 liu yang : >> Do we have API provided to negotiate session capability in application level? >> Let's say, is there one function which takes two parameters of type >> soa_session_t, and return whether they are compatible

Re: [Sofia-sip-devel] sofia 1.12.9 : SOA module : User specified , , of "o=" not updated as local SDP

2009/2/8 liu yang : > I found a weird problem that , > 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 snippe

Re: [Sofia-sip-devel] do SDP negotiation in application level

2009/2/12 liu yang : > Do we have API provided to negotiate session capability in application level? > Let's say, is there one function which takes two parameters of type > soa_session_t, and return whether they are compatible with each other? Not really. What you can do is to clone soa_session_t

Re: [Sofia-sip-devel] Stack crash when the IP on the device changes

Hi; I just patch the code with your two patches from last night and here are the results: -- It takes the right case in the switch ( TRY_FULL or ONLY_INFO ) -- if NUA_NW_DETECT_TRY_FULL is set, the stack crash again with: Assertion failed: (tport_name_is_resolved(orq->orq_tpn)), function out

Re: [Sofia-sip-devel] Stack crash when the IP on the device changes

2009/2/11 Inca Rose : > I will grab the changes and test again. > > Can you pls tell me the changed files so I take only those changes ??? > If it helps, I'm using Sofia SIP on an iPhone. $ darcs changes --last 10 --patch network_change -s Wed Feb 11 22:51:48 EET 2009 Pekka Pessi * nua_i_netwo

Re: [Sofia-sip-devel] NAT keep-alive

2009/2/11 Bengt Werstén : > I have a problem with NAT usage. First I thought I needed STUN but the rport > thing did it so much better and now it works fine doing a register. The > connect fields looks perfect but the problem now is that the keep-alive > mechanism does not work. The first OPTIONS

Re: [Sofia-sip-devel] Using STUN

2009/2/11 Bengt Werstén : > We have got sofia-SIP to work when no NAT is involved but now we need a NAT > solution using STUN. So far I have added the STUN define and changed my > register from: > I think the STUN code was never really polished, the most of the implementation is from pre-bis e

Re: [Sofia-sip-devel] tport_listen patch

2009/2/11 Della Betta Filippo : > tport_listen, when the address is already in use returns error, but fails to > set errno. > I suggest the attached patch to overcome this bug. Thanks. Applied. -- Pekka.Pessi mail at nokia.com ---

Re: [Sofia-sip-devel] Authentication-Info, Allow-Events, and Contact header parsing

2009/2/3 Andrew Rechenberg Lists : > My Sofia-based application is talking to a Microsoft OCS 2007 server and > I believe, in true MS fashion, that certain headers are not quite in > adherence to the RFCs. Could it be that Sofia is not parsing those > headers as a result of them not being standard

[Sofia-sip-devel] do SDP negotiation in application level

Hi, Do we have API provided to negotiate session capability in application level? Let's say, is there one function which takes two parameters of type soa_session_t, and return whether they are compatible with each other? Thanks Kandy -