sr-users November 2007

sr-users@lists.kamailio.org

138 participants
249 discussions

Start a nNew thread

[Serusers] rtpproxy and rtcp
by Miles Scruggs 15 Nov '07

15 Nov '07

Just wondering if there is any way to collect rtcp information from rtpproxy? Thanks Miles

1 0

[OpenSER-Users] attention!!! -- mailing list domains
by Daniel-Constantin Mierla 15 Nov '07

15 Nov '07

Hello, as I see that some send emails to xyz(a)lists.openser.org and cc to xyz(a)openser.org. I want to make sure that everybody understands that only the new domain "lists.openser.org" MUST be used now. First is confusing and, also, we do not need duplicates. If you get problems with lists.openser.org, please report. The old domain "openser.org" for mailing lists will stay in place about one more month from now on, to be sure that most of discussion threads started before migration get closed. The reason at migration time was not to create chaos by not being able to reply, or not having enough time to learn about the new domain. The old mailing lists domains are just aliased to the new ones, the messages end in the same archive, same server. Thanks, Daniel

1 0

[OpenSER-Users] Permissions module addition
by Daryl G. Jurbala 15 Nov '07

15 Nov '07

I'm looking for an addition to the permissions module. I'm using the address table to match valid originators. Each originator needs to be placed into a specific route tree (in carrierroute). Right now, I can do something like: $var(orig) = "unauth"; if (allow_source_address("<fist route tree>")) { $var(orig) = "<first route tree>" } if (allow_source_address("<second route tree>")) { $var(orig) = "<second route tree>" } <etc., etc. for each route tree I have> if $var(orig)=="unauth" { sl_send_reply("403", "Unauthorized IP"); exit; } else { ....process the call..... What I'd like to see is a permissions function that would allow me to do something like: $var(orig) = allow_source_address_group() if $var(orig)=="-1" { sl_send_reply("403", "Unauthorized IP"); exit; } else { ....process the call..... Where the proposed allow_source_address_group() function would search all IPs in the address table and return either a -1 if no matching address is found, or return the value of the group column if one is found. Anyone out there willing to make these changes? If so, please contact me. I'm willing to put a bounty on this. Thanks, Daryl G. Jurbala Director of Network Operations Global Convergence Solutions Tel: +1 732 853 0513

1 0

[Serusers] ACK Problem : Not routed to NAT'd port
by Ricardo Martinez 15 Nov '07

15 Nov '07

Hello list. I'm facing a problem with my SER configuration and a call to a NAT'd endpoint. When I call a NAT'd endpoint registered in my SER proxy, the call is established, but the last ACK message is not properly routed by SER. You can see this in the next messsage flow. 100.100.100.50 : Callee 100.100.100.99 : SER 100.100.100.231 : Called U 100.100.100.50:5060 -> 100.100.100.99:5060 INVITE sip:008991000404@sip.mydomain.com SIP/2.0. Via: SIP/2.0/UDP 100.100.100.50;rport;branch=z9hG4bK404c94810000005a43b2b7ee000053dc0000010f. Contact: <sip:551100000121@100.100.100.50;user=phone>. U 100.100.100.99:5060 -> 100.100.100.50:5060 SIP/2.0 100 trying -- your call is important to us. Via: SIP/2.0/UDP 100.100.100.50;rport=5060;branch=z9hG4bK404c94810000005a43b2b7ee000053dc0000 010f. U 100.100.100.99:5060 -> 100.100.100.231:62447 INVITE sip:551100000684@100.100.100.231;user=phone SIP/2.0. Record-Route: <sip:100.100.100.99;ftag=979715625143;lr=on>. Via: SIP/2.0/UDP 100.100.100.99;branch=z9hG4bKe4c7.150a3f81.0. Via: SIP/2.0/UDP 100.100.100.50;rport=5060;branch=z9hG4bK404c94810000005a43b2b7ee000053dc0000 010f. Contact: <sip:551100000121@100.100.100.50;user=phone>. U 100.100.100.231:62447 -> 100.100.100.99:5060 SIP/2.0 100 Trying. Via: SIP/2.0/UDP 100.100.100.99;branch=z9hG4bKe4c7.150a3f81.0,SIP/2.0/UDP 100.100.100.50;rport=5060;branch=z9hG4bK404c94810000005a43b2b7ee000053dc0000 010f. (The call is answered) U 100.100.100.231:62447 -> 100.100.100.99:5060 SIP/2.0 200 OK. Via: SIP/2.0/UDP 100.100.100.99;branch=z9hG4bKe4c7.150a3f81.0,SIP/2.0/UDP 100.100.100.50;rport=5060;branch=z9hG4bK404c94810000005a43b2b7ee000053dc0000 010f. Contact: <sip:551100000684@100.100.100.231;user=phone>. U 100.100.100.99:5060 -> 100.100.100.50:5060 SIP/2.0 200 OK. Via: SIP/2.0/UDP 100.100.100.50;rport=5060;branch=z9hG4bK404c94810000005a43b2b7ee000053dc0000 010f. Contact: <sip:551100000684@100.100.100.231;user=phone>. U 100.100.100.50:5060 -> 100.100.100.99:5060 ACK sip:551100000684@100.100.100.231;user=phone SIP/2.0. Via: SIP/2.0/UDP 100.100.100.50;rport;branch=z9hG4bK404c94810000005a43b2b7f00000182a00000112. Route: <sip:100.100.100.99;ftag=979715625143;lr=on>. U 100.100.100.99:5060 -> 100.100.100.231:5060 ACK sip:551100000684@100.100.100.231;user=phone SIP/2.0. Record-Route: <sip:100.100.100.99;ftag=979715625143;lr=on>. Via: SIP/2.0/UDP 100.100.100.99;branch=0. Via: SIP/2.0/UDP 100.100.100.50;rport=5060;branch=z9hG4bK404c94810000005a43b2b7f00000182a0000 0112. U 100.100.100.231:62447 -> 100.100.100.99:5060 SIP/2.0 200 OK. Via: SIP/2.0/UDP 100.100.100.99;branch=z9hG4bKe4c7.150a3f81.0,SIP/2.0/UDP 100.100.100.50;rport=5060;branch=z9hG4bK404c94810000005a43b2b7ee000053dc0000 010f. Contact: <sip:551100000684@100.100.100.231;user=phone>. U 100.100.100.99:5060 -> 100.100.100.50:5060 SIP/2.0 200 OK. Via: SIP/2.0/UDP 100.100.100.50;rport=5060;branch=z9hG4bK404c94810000005a43b2b7ee000053dc0000 010f. Contact: <sip:551100000684@100.100.100.231;user=phone>. U 100.100.100.50:5060 -> 100.100.100.99:5060 ACK sip:551100000684@100.100.100.231;user=phone SIP/2.0. Via: SIP/2.0/UDP 100.100.100.50;rport;branch=z9hG4bK404c94810000005a43b2b7f000001d6e00000114. Route: <sip:100.100.100.99;ftag=979715625143;lr=on>. . U 100.100.100.99:5060 -> 100.100.100.231:5060 ACK sip:551100000684@100.100.100.231;user=phone SIP/2.0. Record-Route: <sip:100.100.100.99;ftag=979715625143;lr=on>. Via: SIP/2.0/UDP 100.100.100.99;branch=0. Via: SIP/2.0/UDP 100.100.100.50;rport=5060;branch=z9hG4bK404c94810000005a43b2b7f000001d6e0000 0114. (.........) (Timeout and the call is released) U 100.100.100.231:62447 -> 100.100.100.99:5060 BYE sip:551100000121@100.100.100.50;user=phone SIP/2.0. Via: SIP/2.0/UDP 192.168.1.20;rport;branch=z9hG4bKc0a801140000002643b2a9be000036e10000001f. Route: <sip:100.100.100.99;ftag=979715625143;lr=on>. . U 100.100.100.99:5060 -> 100.100.100.50:5060 BYE sip:551100000121@100.100.100.50;user=phone SIP/2.0. Record-Route: <sip:100.100.100.99;ftag=93794163011;lr=on>. Via: SIP/2.0/UDP 100.100.100.99;branch=z9hG4bK15c7.924c3535.0. Via: SIP/2.0/UDP 192.168.1.20;received=100.100.100.231;rport=62447;branch=z9hG4bKc0a801140000 002643b2a9be000036e10000001f. U 100.100.100.50:5060 -> 100.100.100.99:5060 SIP/2.0 200 OK. Via: SIP/2.0/UDP 100.100.100.99;branch=z9hG4bK15c7.924c3535.0,SIP/2.0/UDP 192.168.1.20;rport=62447;received=100.100.100.231;branch=z9hG4bKc0a801140000 002643b2a9be000036e10000001f. U 100.100.100.99:5060 -> 100.100.100.231:62447 SIP/2.0 200 OK. Via: SIP/2.0/UDP 192.168.1.20;rport=62447;received=100.100.100.231;branch=z9hG4bKc0a801140000 002643b2a9be000036e10000001f. I don't understand why the the ACK message is routed to port 5060 and not to the port 62447 like the INVITE or the final OK. Is this maybe a configuration problem?. My ser.cfg is based on the onsip.org configuration documents plus some modifications by me. Can someone help me here Thanks in advance Ricardo Martinez.-

3 5

[OpenSER-Users] Illegal characteres in SIP URI?
by Iñaki Baz Castillo 15 Nov '07

15 Nov '07

Hi, could somebody tell me which characteres are allowd in a SIP URI? which RFC defines it? I ask it because I do a DB query with $ru so a SQL injection it's possible if RURI contains single or double ' So at the begining of the script I'd like to reject a message if the RURI contains illegal symbols. Could be useful a core function for this? Regards. -- Iñaki Baz Castillo ibc(a)in.ilimit.es

2 3

Re: [OpenSER-Users] Aliases table and db aliases
by Iñaki Baz Castillo 15 Nov '07

15 Nov '07

El Thursday 15 November 2007 16:08:27 escribió: > *Hi,* Better replies to the mailist ;) > Iñaki Baz Castillo wrote: > > * alias with DB_ALIASES module: > > > > table dbaliases: > > alias_username: 1234 > > alias_domain: IP_PROXY > > username: bob > > domain: IP_PROXY > > > > db_aliases_lookup() will rewrite URI when it's 1234@IP_PROXY and it'll > > become bob@IP_PROXY > > > > Later lookup("location") will look for the contact of that AOR. > > *Ok. > db_aliases talble is filled in by myself through "openserctl db_alias > add" command.* > > > * alias with ALIASES table: > > > > table aliases: > > username: 1234 > > domain: IP_PROXY > > contact: sip:bob@IP_PROXY > > > > lookup("aliases") will rewrite URI when it's 1234@IP_PROXY and it'll > > become bob@IP_PROXY > > > > Later lookup("location") will look for the contact of that AOR. > > *so, is ALIASES table also created by myself through "openserctl" > command*s ? No idea. In fact I fill these tables via SQL. > > ok now? > > *ok, thank you very much. > daniel > * Regards. -- ilimit... *Iñaki Baz Castillo* ibc(a)in.ilimit.es ÀREA SISTEMES 0034 937 333 375 VOLTA 1, PIS 5 08224 TERRASSA.BCN Aquest enviament és confidencial i està destinat únicament a la persona a qui s'ha enviat. Pot contenir informació privada sotmesa al secret professional, la distribució de la qual està prohibida per la legislació vigent.

1 0

Re: [OpenSER-Users] Aliases table and db aliases
by Daniel 15 Nov '07

15 Nov '07

Thanks. But I don't understand the use of aliases table. I have defined some subscriber users, with username (like BOB) and password (BOBPWD). So, if I wanted to access the system, I would send a REGISTER message with correct username and password (authorization required). Then my proxy address will be "sip:BOB@IP_PROXY" and my Contact will be "sip:BOB@MY _IP_ADRRESS". These information are saved into USER LOCATION table (save("location") function). Now, through DB_aliases module and dbaliases table, I can define some aliases for BOB (like "sip:1234@IP_PROXY", etc...), so if an INVITE for bob has "sip:1234@IP_PROXY" as R-URI, with db_aliases_lookup() function I can rewrite R-URI with Bob's URI ("bob@IP_PROXY") and then call the lookup("location") function. But I don't understand how I can use the ALIASES table. Are there any example explaining its use ? Sorry. Regards, daniel Iñaki Baz Castillo wrote: El Thursday 15 November 2007 14:31:52 Daniel escribi�: Hi all, what is the different between Aliases table and DB aliases table? What is their use ? "aliases" table is same as "location" table but it should be used to look for alias with the function lookup("aliases"). Of course, aliases are simpler than the complex location or aliases tables that manage more info about users, so in order to implement alias system in a simpler way the module ALIAS_DB exists and its table dbaliases. Note that dbaliases table is much simpler (it's just valid for aliases), Look at the module doc: http://www.openser.org/docs/modules/1.3.x/alias_db.html -- Daniel Grotti ________________________ e-mail : d.grotti(a)gmail.com

2 1

[Serusers] Implicit Registration Set
by Magnus Sörman 15 Nov '07

15 Nov '07

Hi, How do you/could you configure SER to use implicit registration set? If e.g. a user with a sip URI registers, then both that address and his tel-uri should be registered. Thanks, /Magnus Sorman

1 0

[OpenSER-Users] Aliases table and db aliases
by Daniel 15 Nov '07

15 Nov '07

Hi all, what is the different between Aliases table and DB aliases table? What is their use ? regards, daniel -- Daniel Grotti ________________________ e-mail : d.grotti(a)gmail.com

2 1

[OpenSER-Users] Presence module help
by Stanisław Pitucha 15 Nov '07

15 Nov '07

Hello Can someone tell me couple of details about presence code? I.e.: 1. There's PUBL_TYPE and WINFO_TYPE define. They are used as flags, but then they are just marking winfo / other packages. What's the effect of PUBL_TYPE on event package exactly? 2. What is the meaning of 'get_rules_doc', 'apply_auth_nbody', 'get_auth_status' funcs? Unfortunately I wasn't able figure it out from source completely. Thanks Stanisław Pitucha

2 2

← Newer
1
...
9
10
11
12
13
14
15
...
25
Older →

Jump to page:

2025

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