sr-users November 2007

sr-users@lists.kamailio.org

138 participants
248 discussions

by Daniel

Hi all, what is the different between napting interval done by nathelper-module and the other ones done by mediaproxy-module ? Can I set both of them at the same time ? regards, daniel -- Daniel Grotti ________________________ e-mail : d.grotti(a)gmail.com

16 years, 5 months

[OpenSER-Users] Changing From: and To: URIs...

by Phil D'Amore

Hi Everyone... I'm looking for some advice. Let's say I have a To: header in an initial INVITE: To: Bob <sip:8005551212@sip.example.com> Due to carrier requirements, it really needs to be: To: Bob <sip:+18005551212@sip.example.com> I'm not asking how to do it. I know I can use some textops functions to make this happen. I also know that doing this might break something. The uac module already nicely handles the From: header in a way that doesn't break things. I thought about extending this to handle To:, but I worried that the Record-Route header might get too long for some UAs if I wind up having to change both headers. The To tag must also be dealt with somehow, which I think might make it harder to do than From. Using a 302 response is not an option for me, and I'm really trying to avoid getting a B2BUA involved with this right now. Moving from openser 1.1.1 to 1.3 is enough for me without changing my architecture ;). I'm wondering what would be the best way given what openser can do right now (1.3) to re-write that header that doesn't break anything. I'm not adverse to writing some code to make it happen if that is what is needed. Any ideas? Thanks, Phil

16 years, 5 months

[OpenSER-Users] OpenSER 1.3 - release name

by Bogdan-Andrei Iancu

Hi, I would like to make a survey to see if people will consider a nice policy to give to the further openser releases not only version numbers, but also names. If so, I would like to be the first to suggest a name for the upcoming openser 1.3 release -"blackcat" (mainly because of the 13 version :D ). Any other suggestions or comments on the topic are welcomed. Thanks and regards, Bogdan

16 years, 5 months

[OpenSER-Users] OpenSER 1.3 - release date

by Bogdan-Andrei Iancu

Hi, There are still some bugs that need to be fixed before the release of 1.3. I think 2 weeks should from now on should be enough, so I suggest to try to set the release date to 13th of December. Please let me know your thoughts. Regards and a nice weekend, Bogdan

16 years, 5 months

[OpenSER-Users] does CPL change SDP parameter on reply message?

by Daniel

Hi all, if I use <PROXY> in a CPL script, then, how can I change SDP parameter (I want to use media proxy ) in the reply message (200 OK) ? regards, daniel -- Daniel Grotti ________________________ e-mail : d.grotti(a)gmail.com

16 years, 5 months

[OpenSER-Users] CPL and on reply route

by Daniel

Hi all, I use CPL script with "Proxy" element, like this: <cpl> <incoming> <lookup source="registration"> <success> <proxy ordering="sequential" /> </success> </lookup> </incoming> </cpl> and I use onreply_route(), where I make the changes on 180/200 reply messages in case of NAT (change callee's SDP parameter and change Callee's Contact hf). When an INVITE is forwarded, through the <PROXY> element, to the callee, then reply messagges (180 Ringing and 200OK) hasn't processed by Onreply_route. So I can't make my NAT control. Why? Regards, daniel -- Daniel Grotti ________________________ e-mail : d.grotti(a)gmail.com

16 years, 5 months

[OpenSER-Users] openser 1.3 sometimes fails to start

by Robert Dyck

I am testing openser 1.3.0-pre1-notls svnversion 2:3201. I believe it is failing while starting the child processes for the modules. If it starts successfully it seems to perform normally. I believe the following excerpt from the console might hold the clue. Thanks Rob Nov 29 14:40:30 [10492] DBG:xlog:child_init: init_child [0] pid [10492] Nov 29 14:40:30 [10492] DBG:core:init_mod_child: type=PROC_MAIN, rank=0, module=avpops Nov 29 14:40:30 [10498] DBG:core:io_watch_add: io_watch_add(0x8160900, 6, 4, 0xb5f824a4), fd_no=0 Nov 29 14:40:30 [10498] DBG:core:io_watch_add: io_watch_add(0x8160900, 7, 4, 0xb5f82530), fd_no=1 Nov 29 14:40:30 [10498] DBG:core:io_watch_add: io_watch_add(0x8160900, 8, 4, 0xb5f825bc), fd_no=2 Nov 29 14:40:30 [10498] DBG:core:io_watch_add: io_watch_add(0x8160900, 9, 4, 0xb5f82648), fd_no=3 Nov 29 14:40:30 [10498] DBG:core:io_watch_add: io_watch_add(0x8160900, 12, 4, 0xb5f826d4), fd_no=4 Nov 29 14:40:30 [10498] DBG:core:io_watch_add: io_watch_add(0x8160900, 11, 4, 0xb5f82760), fd_no=5 Nov 29 14:40:30 [10498] ERROR:core:io_watch_add: epoll_ctl failed: Invalid argument [22] Nov 29 14:40:30 [10498] CRITICAL:core:tcp_main_loop: failed to add process 6 (TCP main) unix socket to the fd list Nov 29 14:40:30 [10498] CRITICAL:core:tcp_main_loop: exiting...Nov 29 14:40:30 [10497] INFO:nathelper:rtpp_test: rtp proxy <unix:/var/run/rt pproxy.sock> found, support for it enabled Nov 29 14:40:30 [10497] DBG:core:init_mod_child: type=CHILD, rank=3, module=xlog Nov 29 14:40:30 [10497] DBG:xlog:child_init: init_child [3] pid [10497] Nov 29 14:40:30 [10497] DBG:core:init_mod_child: type=CHILD, rank=3, module=avpops Nov 29 14:40:30 [10497] DBG:core:io_watch_add: io_watch_add(0x8160a60, 11, 1, (nil)), fd_no=0 Nov 29 14:40:30 [10492] INFO:core:handle_sigs: child process 10498 exited normally, status=255 Nov 29 14:40:30 [10492] INFO:core:handle_sigs: terminating due to SIGCHLD Nov 29 14:40:30 [10493] INFO:core:sig_usr: signal 15 received Memory status (pkg): qm_status (0x8181760): heap size= 1048576 used= 44448, used+overhead=71504, free=977072 max used (+overhead)= 71504 dumping all alloc'ed. fragments: 0. N address=0x8186908 frag=0x8186900 size=32 used=1 1. N address=0x8186938 frag=0x8186930 size=16 used=1 2. N address=0x8186958 frag=0x8186950 size=32 used=1 3. N address=0x8186988 frag=0x8186980 size=32 used=1 4. N address=0x81869b8 frag=0x81869b0 size=16 used=1 5. N address=0x81869d8 frag=0x81869d0 size=16 used=1 6. N address=0x81869f8 frag=0x81869f0 size=32 used=1 7. N address=0x8186a28 frag=0x8186a20 size=32 used=1 8. N address=0x8186a58 frag=0x8186a50 size=64 used=1 9. N address=0x8186aa8 frag=0x8186aa0 size=64 used=1 10. N address=0x8186af8 frag=0x8186af0 size=64 used=1

16 years, 5 months

Re: [OpenSER-Users] auth_db module - get_ha1(): Error while querying database

by Daniel-Constantin Mierla

Hello, from the logs seems that the content of subscriber table is corrupted. Please attach /usr/local/etc/openser/dbtext/subscriber file and send it to me. Cheers, Daniel On 11/30/07 11:30, Mihail Gluhowchenko wrote: > Hello, > In file log on level 8 when try 9 openser down. > <list of dir(/usr/local/etc/openser/dbtext)> > acc > active_watchers > address > aliases > dbaliases > domaingrp > gw > gw_grp > lcr > location > missed_calls > pdt > presentity > pua > re_grp > silo > speed_dial > subscriber > trusted > uri > usr_preferences > version > watchers > xcap_xml > <end_list_of_dir(/usr/local/etc/openser/dbtext)> > In README file for dbtext error - > break; replace exit; > modparam("auth_db", "calculate_ha1", 1) > replace > modparam("auth_db", "calculate_ha1", yes) > > Regards, > Mihail Gluhowchenko. > > 2007/11/29, Daniel-Constantin Mierla <daniel(a)voice-system.ro > <mailto:daniel@voice-system.ro>>: > > Hello, > > can you list the content of directory: /usr/local/etc/openser/dbtext ? > > Also, if you can set the debug=9 in cofig, run again, get the > output and > send it to me, would help a lot. > > Thanks, > Daniel > > On 11/28/07 13:46, Mihail Gluhowchenko wrote: > > Hello All; > > I`m trying to tune openser-1.2.2 with dbtext data base > > But have some problems. > > I make db use - textdb.sh > > Then add users use - sc.dbtext > > and add to openser.cfg: > > #set module path > > mpath="/usr/local/lib/openser/modules/" > > > > _______________________________________________ > > Users mailing list > > Users(a)lists.openser.org <mailto:Users@lists.openser.org> > > http://lists.openser.org/cgi-bin/mailman/listinfo/users > > > >

16 years, 5 months

[Serusers] fixup_hostport2proxy

by Tuan Nguyen

Hi everyone, i have a problem when i try with two version of SER: SER 0.9.6 and SER 2.1to connect with SEMS (the 1. SER proxy ). With SER 0.9.6 i don't have problem when start it, but with SER 2.1 it's so: 0(13446) ERROR: mk_proxy: could not resolve hostname: "localhost" 0(13446) ERROR: fixup_hostport2proxy: bad host name in URI <localhost> I guess, problem locate in this code: log("Forwarding to 5070"); rewritehostport("localhost:5070"); t_relay_to_udp("localhost","5070"); Anyone know that where can i fix this problem with new version of SER? Thanks for responce. Tuan.

16 years, 5 months

[OpenSER-Users] FYI: [Fwd: [Sip] SIPit 21 summary]

by Klaus Darilion

-------- Original-Nachricht -------- Betreff: [Sip] SIPit 21 summary Datum: Mon, 19 Nov 2007 14:55:53 -0600 Von: Robert Sparks <rjsparks(a)nostrum.com> An: sip List <sip(a)ietf.org> SIPit 21 was hosted by the BII Group and the Beijing University of Posts and Telecommunications, November 5-9 in Beijing, China. The event was a little smaller than the most recent SIPits: There were 94 attendees from 38 companies visiting from 15 countries. There were 44 teams and around 70 distinct implementations. The majority of the testing I saw was focusing on advanced scenarios rather than basic registration and call setup. As with SIPit 20, the most common area of interoperability problems centered around offer/answer, particularly when attempting to negotiate alternate versions of streams or to explicitly state parameters to be used with a given stream. Forty of the attending teams completed the survey - from those answers: The roles represented (some implementations act in more than one role): 21 endpoints 10 proxy/registrars 3 standalone registrars 5 event servers 4 gateways 6 automaton UAs (voicemail, conference, appserver, etc) 8 b2bua/sbcs 4 UAs with signaling, but without media 1 test/monitoring tool Implementations using each transport for SIP messages: UDP 100% TCP 82% TLS 49% (server auth only) TLS 6% (mutual auth) SCTP 3% DTLS 0% 36% of the implementations supported SIP over IPv6 (up from 25% at SIPit20) 18% supported SIP over IPSec For DNS we had support for: Full RFC3263 : 61% SRV only : 21% A records only : 9% no DNS support : 9% Support for various items: 61% rport 15% sigcomp 22% enum 21% sending multiplexing STUN and SIP 28% receiving multiplexed STUN and SIP 22% RFC4320 fixes 12% identity 70% session-timer There was one implementation of parts of the session-policy framework. There was one implementation of the sip-consent framework. There were two implementations of parts of the sip-config framework (I do not know yet if they worked together). There were three implementations of outbound and four of GRUU. There were two implementations of MSRP present. The endpoints implemented these methods: 100% INVITE, CANCEL, ACK, BYE 87% REGISTER 87% OPTIONS 87% NOTIFY <- still a lot of unsolicted NOTIFYs 87% REFER 77% SUBSCRIBE 77% INFO 70% UPDATE 67% PRACK 47% MESSAGE 33% PUBLISH Support for various extensions in the endpoints: 43% RFC3323 privacy 41% RFC3327 path 13% RFC3840 pref 13% RFC3841 caller-prefs 59% RFC3891 replaces 20% RFC4488 norefersub 0% RFC4538 target-dialog <- There were several folks starting to talk about supporting this Support for various things in the endpoints: 10% ICE (but there was no interoperability - see below) 0% ICE-TCP 13% STUNbis 17% TURN (again, there was no interoperability) 75% symmetric RTP 25% SRTP 0% RTP over DTLS This is how the endpoints answered how they supported multipart/mime: 7% I break if someone sends me multipart/mime 30% I pretend multipart mime doesn't exist if someone sends it to me 20% I ignore multipart/mime, but will proxy it or hand it to my application if it shows up 17% I try to do something useful with multipart/mime I receive, but I never send it 3% I ignore multipart/mime I receive, but I try to send it to do something useful 20% I try to do something useful with multipart/mime I send and receive There were 4 endpoints that would send media over TCP - none of them supported RFC4145 comedia. One of those supported media over TLS. Implementation is all over the map for fork-loop-fix. However, only 3 of the proxy/b2buas present were still vulnerable to the simple form of the attack described in the draft. There were no implementations present with support for location- conveyance or the geopriv common-policy framework. There was one implementation present with support for the RFC4967 dial-string parameter, and one with support for the ecrit service-urn. Of the SIP-Events implementations, the following packages were supported: 62% refer 48% message-summary 38% presence 29% dialog 19% reg 19% conf There was one implementation of each of the following packages: ua-profile certificate/credentials vx-rtcpxp (sipping-rtcp-summary) There was only one implementation of event-lists present. Only 20% of the SIP-Events implementations supported winfo. We had a multiparty sesssion for a full morning focusing on NAT traversal. Basic use of STUN with SIP is hightly interoperable. No two implementations of TURN could even start trying to talk to each other (each having implemented to different points in the recent torrent of changes). I don't think we'll get much implementation feedback until the spec stops making big changes so frequently. No two implementations of ICE worked together. The closest was between two implementations that have worked in the past, but failed during this session when the connectivity checks arrived before the SDP. _______________________________________________ Sip mailing list https://www1.ietf.org/mailman/listinfo/sip This list is for NEW development of the core SIP Protocol Use sip-implementors(a)cs.columbia.edu for questions on current sip Use sipping(a)ietf.org for new developments on the application of sip

16 years, 5 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

sr-users November 2007