[Sofia-sip-devel] Future of SigComp support?

2007-04-23 Thread Marcus Eriksson Y (LI/EAB)

Hi guys!

I noticed that there is support for denoting that SigComp is available
(RFC 3486) but that SigComp itself (RFC 3320) is not supported. This is
just what the conformance table says.

I saw some code in tport_sigcomp.c that seems to handle SigComp, but it
is unfinished and, as far as I can see, relatively untouched in the last
year. Are there any plans to resume work on this by any of the
developers?

/ Marcus
-
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] Duplicated VIA headers of SIP REQUEST

2007-04-23 Thread James Tsai

Dear all,

Did anyone know how to modify the Via header of outgoing SIP REQUEST by
using nua level apis? Because I want to fill the external IP of NAT that I
obtained (by using some else mechanism outside of sofia-sip).

I add SIPTAG_VIA_STR(SIP/2.0/UDP external_ip) when creating the handle
that is used to sent out SIP REQUEST. But it cause the duplicated Via header
of REQUEST i sent, as following :

Via: SIP/2.0/UDP 192.168.1.100;rport;branch=z9hG4b..
Via: SIP/2.0/UDP external_ip
(It is not exactly I need)

By using nua level api, is that any possible way to replace or remove the
original Via header generated by sofia-sip stack ?


Thanks for your reading, and looking forward to any possible solution?
--
James.CM.Tsai
--
-
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


Re: [Sofia-sip-devel] Duplicated VIA headers of SIP REQUEST

2007-04-23 Thread Michael Jerris
If you add ;maddr=1.2.3.4 where 1.2.3.4 is the interface ip to bind to,
to the end of the url that you pass to the NUTAG_URL on nua_create then
it binds to the address specified in maddr but properly uses the first
part of that url for the via and contact.

 

Mike

 

 

 



From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
James Tsai
Sent: Monday, April 23, 2007 7:52 AM
To: sofia-sip-devel@lists.sourceforge.net
Subject: [Sofia-sip-devel] Duplicated VIA headers of SIP REQUEST

 

Dear all,

 

Did anyone know how to modify the Via header of outgoing SIP REQUEST by
using nua level apis? Because I want to fill the external IP of NAT that
I obtained (by using some else mechanism outside of sofia-sip).

 

I add SIPTAG_VIA_STR(SIP/2.0/UDP external_ip) when creating the
handle that is used to sent out SIP REQUEST. But it cause the duplicated
Via header of REQUEST i sent, as following :

 

Via: SIP/2.0/UDP 192.168.1.100;rport;branch=z9hG4b..

Via: SIP/2.0/UDP external_ip

(It is not exactly I need)

 

By using nua level api, is that any possible way to replace or remove
the original Via header generated by sofia-sip stack ?

 

 

Thanks for your reading, and looking forward to any possible solution?

--

James.CM.Tsai

--

-
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


Re: [Sofia-sip-devel] Future of SigComp support?

2007-04-23 Thread Pekka Pessi
2007/4/23, Marcus Eriksson Y (LI/EAB) [EMAIL PROTECTED]:
 I noticed that there is support for denoting that SigComp is available (RFC
 3486) but that SigComp itself (RFC 3320) is not supported. This is just what
 the conformance table says.

 I saw some code in tport_sigcomp.c that seems to handle SigComp, but it is
 unfinished and, as far as I can see, relatively untouched in the last year.

Yes, the upper layers support SigComp, but the sigcomp interface in
tport module got broken before 1.12.0. The upper layers have to
updated, too, after draft-ietf-rohc-sigcomp-sip gets ready, and that
could happen any century now.

It looks like Adam has now OpenSigComp available, so we could use that
with Sofia-SIP, too.

 Are there any plans to resume work on this by any of the developers?

Currently we have little time or interest in SigComp. Any volunteers
are accepted gladly, however. ;)

-- 
Pekka.Pessi mail at nokia.com

-
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] sofia-sip changes (2007-04-23)

2007-04-23 Thread Sofia-SIP Darcs Changes
This posting was generated automatically from darcs repo
http://sofia-sip.org/repos/sofia-sip.

Mon Apr 23 16:14:44 EEST 2007  [EMAIL PROTECTED]
  * for all files related: 's/static inline/su_inline/g'

M ./libsofia-sip-ua/bnf/bnf.c -6 +6
M ./libsofia-sip-ua/bnf/sofia-sip/bnf.h -11 +11
M ./libsofia-sip-ua/http/http_basic.c -1 +1
M ./libsofia-sip-ua/http/http_extra.c -2 +2
M ./libsofia-sip-ua/http/sofia-sip/http_tag.h.in -6 +6
M ./libsofia-sip-ua/iptsec/auth_common.c -2 +2
M ./libsofia-sip-ua/iptsec/auth_module.c -2 +2
M ./libsofia-sip-ua/iptsec/auth_ntlm.c -1 +1
M ./libsofia-sip-ua/iptsec/sofia-sip/auth_module.h -2 +2
M ./libsofia-sip-ua/msg/msg_date.c -2 +2
M ./libsofia-sip-ua/msg/msg_header_copy.c -2 +2
M ./libsofia-sip-ua/msg/msg_internal.h -5 +5
M ./libsofia-sip-ua/msg/msg_parser.c -20 +20
M ./libsofia-sip-ua/msg/sofia-sip/msg_header.h -2 +2
M ./libsofia-sip-ua/msg/sofia-sip/msg_mclass_hash.h -1 +1
M ./libsofia-sip-ua/msg/test_class.h -1 +1
M ./libsofia-sip-ua/msg/test_protos.h.in -4 +4
M ./libsofia-sip-ua/nea/nea_server.c -2 +2
M ./libsofia-sip-ua/nta/nta.c -63 +63
M ./libsofia-sip-ua/nth/nth_server.c -4 +4
M ./libsofia-sip-ua/nua/nua_dialog.h -11 +11
M ./libsofia-sip-ua/nua/nua_session.c -1 +1
M ./libsofia-sip-ua/nua/nua_stack.c -1 +1
M ./libsofia-sip-ua/nua/nua_stack.h -3 +3
M ./libsofia-sip-ua/nua/test_nua.h -2 +2
M ./libsofia-sip-ua/sdp/sdp.c -2 +2
M ./libsofia-sip-ua/sip/sip_event.c -2 +2
M ./libsofia-sip-ua/sip/sofia-sip/sip_tag.h.in -6 +6
M ./libsofia-sip-ua/sip/validator.c -2 +2
M ./libsofia-sip-ua/soa/soa.c -2 +2
M ./libsofia-sip-ua/sresolv/sres.c -4 +4
M ./libsofia-sip-ua/sresolv/sres_cache.c -4 +4
M ./libsofia-sip-ua/sresolv/test_sresolv.c -4 +4
M ./libsofia-sip-ua/stun/stun.c -2 +2
M ./libsofia-sip-ua/su/sofia-sip/htable.h -1 +1
M ./libsofia-sip-ua/su/sofia-sip/htable2.h -1 +1
M ./libsofia-sip-ua/su/sofia-sip/rbtree.h -9 +9
M ./libsofia-sip-ua/su/sofia-sip/su_strlst.h -1 +1
M ./libsofia-sip-ua/su/sofia-sip/su_tag.h -4 +4
M ./libsofia-sip-ua/su/sofia-sip/su_tag_inline.h -8 +8
M ./libsofia-sip-ua/su/sofia-sip/su_vector.h -1 +1
M ./libsofia-sip-ua/su/sofia-sip/su_wait.h -1 +1
M ./libsofia-sip-ua/su/su_alloc.c -5 +5
M ./libsofia-sip-ua/su/su_localinfo.c -1 +1
M ./libsofia-sip-ua/su/su_port.h -24 +24
M ./libsofia-sip-ua/su/su_strlst.c -1 +1
M ./libsofia-sip-ua/su/su_taglist.c -1 +1
M ./libsofia-sip-ua/su/su_timer.c -10 +10
M ./libsofia-sip-ua/su/torture_rbtree.c -2 +2
M ./libsofia-sip-ua/tport/tport.c -11 +11
M ./libsofia-sip-ua/tport/tport_internal.h -2 +2
M ./libsofia-sip-ua/tport/tport_sigcomp.c -2 +2
M ./libsofia-sip-ua/tport/tport_threadpool.c -2 +2
M ./libsofia-sip-ua/url/url.c -3 +3
M ./libsofia-sip-ua/url/urlmap.c -1 +1

-
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


Re: [Sofia-sip-devel] Duplicated VIA headers of SIP REQUEST

2007-04-23 Thread James Tsai

Hello Mike,

Thank you for your suggestion, it works !!
I modified the url passed to the NUTAG_URL on nua_create() as following :
NUTAG_URL(sip:external-ip:local-port;maddr=local-ip)

The Via header of outgoing REQUEST becames :
Via: SIP/2.0/UDP external-ip:local-port;rport;branch=z9hG4

However, this still is not exactly what I need. It's my mistake that did
not explain my question completely during the last post. I have local-ip,
local-port which I want the sip stack to bind to, and I also have its
corresponding external-ip external-port obtained by stun (not use sofia-sip
api). So, I want the outgoing Via header as following, and sip stack still
bind to local-ip:local-port.

Via: SIP/2.0/UDP external-ip:external-port;branch=z9hG4

Is there any possible way to do this ? If my wish is simply not possible,
what should I try to do ? modify rport, or some else ways ??

I very appreciate your help, Mike. And thanks for all your reading, look
forward to the reply.


On 4/23/07, Michael Jerris [EMAIL PROTECTED] wrote:


 If you add ;maddr=1.2.3.4 where 1.2.3.4 is the interface ip to bind to,
to the end of the url that you pass to the NUTAG_URL on nua_create then it
binds to the address specified in maddr but properly uses the first part of
that url for the via and contact.



Mike






  --

*From:* [EMAIL PROTECTED] [mailto:
[EMAIL PROTECTED] *On Behalf Of *James Tsai
*Sent:* Monday, April 23, 2007 7:52 AM
*To:* sofia-sip-devel@lists.sourceforge.net
*Subject:* [Sofia-sip-devel] Duplicated VIA headers of SIP REQUEST



Dear all,



Did anyone know how to modify the Via header of outgoing SIP REQUEST by
using nua level apis? Because I want to fill the external IP of NAT that I
obtained (by using some else mechanism outside of sofia-sip).



I add SIPTAG_VIA_STR(SIP/2.0/UDP external_ip) when creating the handle
that is used to sent out SIP REQUEST. But it cause the duplicated Via header
of REQUEST i sent, as following :



Via: SIP/2.0/UDP 192.168.1.100;rport;branch=z9hG4b..

Via: SIP/2.0/UDP external_ip

(It is not exactly I need)



By using nua level api, is that any possible way to replace or remove the
original Via header generated by sofia-sip stack ?





Thanks for your reading, and looking forward to any possible solution?

--

James.CM.Tsai

--

-
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