sr-users November 2005

sr-users@lists.kamailio.org

245 participants
571 discussions

[Serusers] Random Value in Custom Headers
by Andrey Kouprianov 29 Nov '05

29 Nov '05

Hi all: Actually, I already posted this kind of question, but once again: can I configure SER to leave custom headers in responses, because SER seems to strip them off. The problem is that my custom headers are not the same all the time. For instance, X-Header: blah <random value> This <random value> is always changing, that's why I cannot use append_hf() function. Can I somehow make SER leave custom headers untouched?

2 1

[Serusers] Please help with ser/nathelper
by Enky 29 Nov '05

29 Nov '05

Hi, I am trying to run the SER as an outbound proxy. Unfortunately I have some problems. I have used the nathelper/rtpproxy with a customized ser.conf and the result is that the clients behind NAT are making outbound calls with no problems. The audio is two-way and all seems best, but when I try to react a client behind NAT I can not. It is registered in the SIP Proxy, but I can not dial it. My scenario is: SER with MySQL authorization on the first PC and SER with nathelper/rtpproxy for outbound proxy on second PC. Could someone give me some hint as I can not solve this problem. The Outbound Proxy SER version is: version: ser 0.9.3 (i386/linux) flags: STATS: Off, USE_IPV6, USE_TCP, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC, FAST_LOCK-ADAPTIVE_WAIT ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, MAX_URI_SIZE 1024, BUF_SIZE 65535 @(#) $Id: main.c,v 1.197 2004/12/03 19:09:31 andrei Exp $ main.c compiled on 20:51:59 Jun 28 2005 with gcc 3.3 The ser.cfg of the Outbound Proxy SER is: # # $Id: nathelper.cfg,v 1.1 2003/11/10 14:15:36 janakj Exp $ # # simple quick-start config script including nathelper support # This default script includes nathelper support. To make it work # you will also have to install Maxim's RTP proxy. The proxy is enforced # if one of the parties is behind a NAT. # # If you have an endpoing in the public internet which is known to # support symmetric RTP (Cisco PSTN gateway or voicemail, for example), # then you don't have to force RTP proxy. If you don't want to enforce # RTP proxy for some destinations than simply use t_relay() instead of # route(1) # # Sections marked with !! Nathelper contain modifications for nathelper # # NOTE !! This config is EXPERIMENTAL ! # # ----------- global configuration parameters ------------------------ debug=3 # debug level (cmd line: -dddddddddd) fork=yes log_stderror=no # (cmd line: -E) /* Uncomment these lines to enter debugging mode fork=no log_stderror=yes */ check_via=no # (cmd. line: -v) dns=no # (cmd. line: -r) rev_dns=no # (cmd. line: -R) port=5082 children=4 fifo="/tmp/ser_fifo" # ------------------ module loading ---------------------------------- # Uncomment this if you want to use SQL database #loadmodule "/usr/local/lib/ser/modules/mysql.so" loadmodule "/usr/local/lib/ser/modules/sl.so" loadmodule "/usr/local/lib/ser/modules/tm.so" loadmodule "/usr/local/lib/ser/modules/rr.so" loadmodule "/usr/local/lib/ser/modules/maxfwd.so" loadmodule "/usr/local/lib/ser/modules/usrloc.so" loadmodule "/usr/local/lib/ser/modules/registrar.so" loadmodule "/usr/local/lib/ser/modules/textops.so" # Uncomment this if you want digest authentication # mysql.so must be loaded ! #loadmodule "/usr/local/lib/ser/modules/auth.so" #loadmodule "/usr/local/lib/ser/modules/auth_db.so" # !! Nathelper loadmodule "/usr/local/lib/ser/modules/nathelper.so" # ----------------- setting module-specific parameters --------------- # -- usrloc params -- modparam("usrloc", "db_mode", 0) # Uncomment this if you want to use SQL database # for persistent storage and comment the previous line #modparam("usrloc", "db_mode", 2) # -- auth params -- # Uncomment if you are using auth module # #modparam("auth_db", "calculate_ha1", yes) # # If you set "calculate_ha1" parameter to yes (which true in this config), # uncomment also the following parameter) # #modparam("auth_db", "password_column", "password") # -- rr params -- # add value to ;lr param to make some broken UAs happy modparam("rr", "enable_full_lr", 1) # !! Nathelper modparam("registrar", "nat_flag", 6) modparam("nathelper", "natping_interval", 60) # Ping interval 60 s modparam("nathelper", "ping_nated_only", 1) # Ping only clients behind NAT # ------------------------- request routing logic ------------------- # main routing logic route{ # initial sanity checks -- messages with # max_forwards==0, or excessively long requests if (!mf_process_maxfwd_header("10")) { sl_send_reply("483","Too Many Hops"); break; }; if (msg:len >= max_len ) { sl_send_reply("513", "Message too big"); break; }; # !! Nathelper # Special handling for NATed clients; first, NAT test is # executed: it looks for via!=received and RFC1918 addresses # in Contact (may fail if line-folding is used); also, # the received test should, if completed, should check all # vias for rpesence of received if (nat_uac_test("3")) { # Allow RR-ed requests, as these may indicate that # a NAT-enabled proxy takes care of it; unless it is # a REGISTER if (method == "REGISTER" || ! search("^Record-Route:")) { log("LOG: Someone trying to register from private IP, rewriting\n"); # This will work only for user agents that support symmetric # communication. We tested quite many of them and majority is # smart enough to be symmetric. In some phones it takes a configuration # option. With Cisco 7960, it is called NAT_Enable=Yes, with kphone it is # called "symmetric media" and "symmetric signalling". fix_nated_contact(); # Rewrite contact with source IP of signalling if (method == "INVITE") { fix_nated_sdp("1"); # Add direction=active to SDP }; force_rport(); # Add rport parameter to topmost Via setflag(6); # Mark as NATed }; }; # we record-route all messages -- to make sure that # subsequent messages will go through our proxy; that's # particularly good if upstream and downstream entities # use different transport protocol if (!method=="REGISTER") record_route(); # subsequent messages withing a dialog should take the # path determined by record-routing if (loose_route()) { # mark routing logic in request append_hf("P-hint: rr-enforced\r\n"); route(1); break; }; if (!uri==myself) { # mark routing logic in request append_hf("P-hint: outbound\r\n"); route(1); break; }; # if the request is for other domain use UsrLoc # (in case, it does not work, use the following command # with proper names and addresses in it) if (uri==myself) { if (method=="REGISTER") { save("location"); break; }; lookup("aliases"); if (!uri==myself) { append_hf("P-hint: outbound alias\r\n"); route(1); break; }; # native SIP destinations are handled using our USRLOC DB if (!lookup("location")) { sl_send_reply("404", "Not Found"); break; }; }; append_hf("P-hint: usrloc applied\r\n"); route(1); } route[1] { # !! Nathelper if (uri=~"[@:](192\.168\.|10\.|172\.(1[6-9]|2[0-9]|3[0-1])\.)" && !search("^Route:")){ sl_send_reply("479", "We don't forward to private IP addresses"); break; }; # if client or server know to be behind a NAT, enable relay if (isflagset(6)) { force_rtp_proxy(); }; # NAT processing of replies; apply to all transactions (for example, # re-INVITEs from public to private UA are hard to identify as # NATed at the moment of request processing); look at replies t_on_reply("1"); # send it out now; use stateful forwarding as it works reliably # even for UDP2TCP if (!t_relay()) { sl_reply_error(); }; } # !! Nathelper onreply_route[1] { # NATed transaction ? if (isflagset(6) && status =~ "(183)|2[0-9][0-9]") { fix_nated_contact(); if (!search("^Content-Length:\ 0")) { force_rtp_proxy(); }; # otherwise, is it a transaction behind a NAT and we did not # know at time of request processing ? (RFC1918 contacts) } else if (nat_uac_test("1")) { fix_nated_contact(); }; }

2 1

[Serusers] domain trouble
by George Lambson 29 Nov '05

29 Nov '05

For some reason my SER isn't using the sip domain I specify (export SIP_DOMAIN="whatever.edu"). When my UA registers it will only register if I take out all of the digect authentication from my config file (I leave all of them blank instead of putting in a domain) and then use the host name of my server instead of a domain. Any ideas what I am doing wrong? Thanks, George

2 1

[Users] a sample .cfg file for proxy server
by jyotisankar nayak 29 Nov '05

29 Nov '05

hi can u pls send me a sample confuguration file so that i can configure a proxy server. my requerment is simple.. i want to send request to a server through openser regards jyoti --------------------------------- Yahoo! Music Unlimited - Access over 1 million songs. Try it free.

2 1

[Users] domainkeys module
by Klaus Darilion 29 Nov '05

29 Nov '05

Hi! I've just posted a domainkeys module on the tracker on sourceforge: http://sourceforge.net/tracker/index.php?func=detail&aid=1368417&group_id=1… This is a "proof-of-concept" and at the moment not a module for real usage. Further, this is something which not standardized or documented anywhere. It's just an experiment to use the domainkeys technology (invented as anti-SPAM technology for emails) also with SIP. Following some snippets from the README file. If you would like to discuss this idea with me, you'r welcome. regards klaus Chapter 1. User's Guide 1.1. Overview This module is a proof-of-concept. It tries to use the domainkeys technologie, for signing SIP message. Domainkeys were developed as an anti-SPAM technology for emails. But as SIP is familiar with email, it might also be useful to use domainkeys for signing SIP messages. _________________________________________________________ 1.1.1. Installation Just copy the module into openser's module directory. This module needs the libdomainkeys library and the libcrypto library (from openssl). Thus make sure to have openssl installed. If the domainkeys library is not installed in the default directories, you have to modify the library path in the Makefile to point to the location of the domainkeys module and include this directory to /etc/ld.so.conf. Further you have to adopt the inlcude path of #include "/home/darilion/libdomainkeys-0.68/domainkeys.h" in the file domainkeys.c. Then compile and use the module as usual. _________________________________________________________ 1.1.2. Known Limitations * The current version signs only the From: and To: header, and the message body. * This module is far from stable and seriously contains several bugs. * Signing and validation takes time. On a 2GHz Athlon CPU, the signing off an INVITE message (From:, To: and body) took ~8ms. The validation of this message took ~9ms. Additionally, the validation takes time as at least one DNS lookup is necessary to fetch the public key of the signing domain. This can be reduced by a fast resolving name server and long TTLs for the public key. * This module uses the original received SIP message for calculating the message signatur. Thus, if you use function which modify the used headers (e.g. uac module) or which modify the body (e.g. nathelper module), then the added signature will be invalid. 1.3. Exported Parameters 1.3.1. privkey_file (string) Path to the file containing the private key for the signing. (The public key for the validation will be fetched from DNS) Default value is "". Example 1-1. privkey_file example modparam("domainkeys", "privkey_file", "/etc/domainkeys/privkeys/2005") _________________________________________________________ 1.4. Exported Functions 1.4.1. domainkeys_validate Signs the SIP message. This function can be used from REQUEST_ROUTE. Example 1-2. domainkeys_validate usage ... if (is_method("INVITE")) { if (domainkeys_sign()) { xlog("L_INFO","domainkeys - signing: SUCCESS\n"); } else { xlog("L_INFO","domainkeys - signing: FAILURE\n"); } } ... _________________________________________________________ 1.4.2. domainkeys_validate Validates the Domainkeys-Signature in the received SIP message. This function can be used from REQUEST_ROUTE. Example 1-3. search_append usage ... if (is_present_hf("Domainkey-Signature")) { xlog("L_INFO","Domainkey-Signature found, start validating...\n"); if (domainkeys_validate()) { xlog("L_INFO","domainkeys - validate: SUCCESS\n"); } else { xlog("L_INFO","domainkeys - validate: FAILURE\n"); } } ...

2 2

[Users] CANCEL problem
by Klaus Darilion 29 Nov '05

29 Nov '05

Hi! looks like there is a problem if the CANCEL is received during DNS lookup of the ongoing transaction. The CANCEL is answered with 200 Ok, but the cancel will not send upstream, although the INVITE is sent. No 487 either. My CANCEL config: if ( is_method("CANCEL") && !t_check_trans() ) { # CANCEL without matching INVITE transaction, ignore # may happen if the INVITE is slower than the CANCEL # ignore the CANCEL, as the client will retransmit it, and maybe next time # the INVITE transaction is already created xlog("L_WARN","CANCEL without matching transaction ... ignore and discard.\n"); exit; } if ( is_method("CANCEL") ) { # CANCEL with matching INVITE transaction, just # t_relay xlog("L_INFO","CANCEL with matching transaction ... t_relay.\n"); t_relay(); exit; below are the SIP call flow and the syslog output regards klaus openser[3670]: SIP Request: openser[3670]: method: <CANCEL> openser[3670]: uri: <sip:klaus3000@iptel.org> openser[3670]: version: <SIP/2.0> openser[3670]: parse_headers: flags=2 openser[3670]: Found param type 232, <branch> = <z9hG4bK-d87543-5b192d3a37574d15-1--d87543->; state=6 openser[3670]: Found param type 235, <rport> = <n/a>; state=17 openser[3670]: end of header reached, state=5 openser[3670]: parse_headers: Via found, flags=2 openser[3670]: parse_headers: this is the first via openser[3670]: After parse_msg... openser[3670]: preparing to run routing scripts... openser[3670]: parse_headers: flags=100 openser[3670]: DEBUG:parse_to:end of header reached, state=9 openser[3670]: DEBUG: get_hdr_field: <To> [27]; uri=[sip:klaus3000@iptel.org] openser[3670]: DEBUG: to body [<sip:klaus3000@iptel.org>^M ] openser[3670]: get_hdr_field: cseq <CSeq>: <1> <CANCEL> openser[3670]: DEBUG: get_hdr_body : content_length=0 openser[3670]: found end of header openser[3670]: DEBUG: is_maxfwd_present: max_forwards header not found! openser[3670]: parse_headers: flags=ffffffffffffffff openser[3670]: DEBUG: add_param: tag=a83eae01 openser[3670]: DEBUG:parse_to:end of header reached, state=29 openser[3670]: parse_headers: flags=200 openser[3670]: find_first_route: No Route headers found openser[3670]: loose_route: There is no Route HF openser[3670]: parse_headers: flags=78 openser[3670]: DEBUG: t_lookupOriginalT: searching on hash entry 62046 openser[3670]: DEBUG: RFC3261 transaction matched, tid=-d87543-5b192d3a37574d15-1--d87543- openser[3670]: DEBUG: t_lookupOriginalT: canceled transaction found (0x40484280)! openser[3670]: DEBUG: t_lookupOriginalT completed openser[3670]: xl_printf: final buffer length 46 openser[3670]: CANCEL with matching transaction ... t_relay. openser[3670]: DEBUG: t_newtran: msg id=3 , global msg id=2 , T on entrance=0xffffffff openser[3670]: parse_headers: flags=ffffffffffffffff openser[3670]: parse_headers: flags=78 openser[3670]: t_lookup_request: start searching: hash=62046, isACK=0 openser[3670]: DEBUG: RFC3261 transaction matching failed openser[3670]: DEBUG: t_lookup_request: no transaction found openser[3670]: DEBUG: t_lookupOriginalT: searching on hash entry 62046 openser[3670]: DEBUG: RFC3261 transaction matched, tid=-d87543-5b192d3a37574d15-1--d87543- openser[3670]: DEBUG: t_lookupOriginalT: canceled transaction found (0x40484280)! openser[3670]: DEBUG: t_lookupOriginalT completed openser[3670]: DEBUG: e2e_cancel: e2e cancel -- no more pending branches openser[3670]: parse_headers: flags=ffffffffffffffff openser[3670]: check_via_address(83.136.33.3, 83.136.33.3, 0) openser[3670]: WARNING:vqm_resize: resize(0) called openser[3670]: DEBUG: cleanup_uac_timers: RETR/FR timers reset openser[3670]: DEBUG: add_to_tail_of_timer[2]: 0x40486168 openser[3670]: DEBUG:tm:_reply_light: reply sent out. buf=0x8117520: SIP/2.0 2..., shmem=0x40485d00: SIP/2.0 2 openser[3670]: DEBUG:tm:_reply_light: finished openser[3670]: SER: new transaction fwd'ed openser[3670]: DEBUG:destroy_avp_list: destroying list (nil) openser[3670]: receive_msg: cleaning up U 2005/11/28 13:55:39.652279 83.136.33.3:8722 -> 213.239.207.29:5060 INVITE sip:klaus3000@iptel.org SIP/2.0. Via: SIP/2.0/UDP 83.136.33.3:8722;branch=z9hG4bK-d87543-5b192d3a37574d15-1--d87543-;rport. Max-Forwards: 70. Contact: <sip:klaus@83.136.33.3:8722>. To: <sip:klaus3000@iptel.org>. From: "klaus dk.labs.nic.at"<sip:klaus@dk.labs.nic.at>;tag=a83eae01. Call-ID: 9843d9424930591d@a2xhdXNwYw... CSeq: 1 INVITE. Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO. Content-Type: application/sdp. Supported: eventlist. User-Agent: eyeBeam release 3010n stamp 19039. Content-Length: 201. . v=0. o=- 15208201 15208322 IN IP4 83.136.33.3. s=eyeBeam. c=IN IP4 83.136.33.3. t=0 0. m=audio 8468 RTP/AVP 0 8 3 18 101. a=fmtp:101 0-15. a=ptime:18 40. a=rtpmap:101 telephone-event/8000. a=sendrecv. # U 2005/11/28 13:55:39.660699 213.239.207.29:5060 -> 83.136.33.3:8722 SIP/2.0 100 trying -- your call is important to us. Via: SIP/2.0/UDP 83.136.33.3:8722;branch=z9hG4bK-d87543-5b192d3a37574d15-1--d87543-;rport=8722. To: <sip:klaus3000@iptel.org>. From: "klaus dk.labs.nic.at"<sip:klaus@dk.labs.nic.at>;tag=a83eae01. Call-ID: 9843d9424930591d@a2xhdXNwYw... CSeq: 1 INVITE. Server: OpenSer (1.0.0 (i386/linux)). Content-Length: 0. Warning: 392 213.239.207.29:5060 "Noisy feedback tells: pid=3669 req_src_ip=83.136.33.3 req_src_port=8722 in_uri=sip:klaus3000@iptel.org out_uri=sip:klaus3000@iptel.org via_cnt==1". . # U 2005/11/28 13:55:39.661561 213.239.207.29:32792 -> 213.133.98.96:53 ............._sip._udp.iptel.org..!.. # U 2005/11/28 13:55:39.718959 213.133.98.96:53 -> 213.239.207.29:32792 ............._sip._udp.iptel.org..!.....!....N%.........sip.iptel.org.........N%...ns7 fraunhofer.de.........N%...ns1.V........N%...ns2.V........N%...ns3.V........N%...ns5.V.sip........N&...%Mc.R.......>...6"..q......"....,%..............`.. # U 2005/11/28 13:55:39.719287 213.239.207.29:32792 -> 213.133.98.96:53 .............sip.iptel.org..... # U 2005/11/28 13:55:39.913552 83.136.33.3:8722 -> 213.239.207.29:5060 CANCEL sip:klaus3000@iptel.org SIP/2.0. Via: SIP/2.0/UDP 83.136.33.3:8722;branch=z9hG4bK-d87543-5b192d3a37574d15-1--d87543-;rport. To: <sip:klaus3000@iptel.org>. From: "klaus dk.labs.nic.at"<sip:klaus@dk.labs.nic.at>;tag=a83eae01. Call-ID: 9843d9424930591d@a2xhdXNwYw... CSeq: 1 CANCEL. User-Agent: eyeBeam release 3010n stamp 19039. Content-Length: 0. . # U 2005/11/28 13:55:39.918736 213.239.207.29:5060 -> 83.136.33.3:8722 SIP/2.0 200 ok -- no more pending branches. Via: SIP/2.0/UDP 83.136.33.3:8722;branch=z9hG4bK-d87543-5b192d3a37574d15-1--d87543-;rport=8722. To: <sip:klaus3000@iptel.org>;tag=fa997f81440371de71ab448ebdb9af56-3f94. From: "klaus dk.labs.nic.at"<sip:klaus@dk.labs.nic.at>;tag=a83eae01. Call-ID: 9843d9424930591d@a2xhdXNwYw... CSeq: 1 CANCEL. Server: OpenSer (1.0.0 (i386/linux)). Content-Length: 0. Warning: 392 213.239.207.29:5060 "Noisy feedback tells: pid=3670 req_src_ip=83.136.33.3 req_src_port=8722 in_uri=sip:klaus3000@iptel.org out_uri=sip:klaus3000@iptel.org via_cnt==1". . # U 2005/11/28 13:55:40.083745 213.133.98.96:53 -> 213.239.207.29:32792 .............sip.iptel.org.............N&...%Mc........N%...ns7 fraunhofer.de.........N%...ns1.?........N%...ns2.?........N%...ns3.?........N%...ns5.?.;.......>...6"..Z......"....,%..l...........`.. # U 2005/11/28 13:55:40.084090 213.239.207.29:5060 -> 195.37.77.99:5060 INVITE sip:klaus3000@iptel.org SIP/2.0. Record-Route: <sip:213.239.207.29;ftag=a83eae01;lr=on>. DomainKey-Signature: a=rsa-sha1; q=dns; c=simple; s=2005; d=dk.labs.nic.at; h=To:From; b=gQHw1V0nzlaGJgDtZX3DY+9MCck/NlieDzMnVseDjJALaG6/vtgZG98jPtas6CZx. Via: SIP/2.0/UDP 213.239.207.29;branch=z9hG4bKe52f.c88e2d42.0. Via: SIP/2.0/UDP 83.136.33.3:8722;branch=z9hG4bK-d87543-5b192d3a37574d15-1--d87543-;rport=8722. Max-Forwards: 69. Contact: <sip:klaus@83.136.33.3:8722>. To: <sip:klaus3000@iptel.org>. From: "klaus dk.labs.nic.at"<sip:klaus@dk.labs.nic.at>;tag=a83eae01. Call-ID: 9843d9424930591d@a2xhdXNwYw... CSeq: 1 INVITE. Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO. Content-Type: application/sdp. Supported: eventlist. User-Agent: eyeBeam release 3010n stamp 19039. Content-Length: 201. P-hint: outbound. . v=0. o=- 15208201 15208322 IN IP4 83.136.33.3. s=eyeBeam. c=IN IP4 83.136.33.3. t=0 0. m=audio 8468 RTP/AVP 0 8 3 18 101. a=fmtp:101 0-15. a=ptime:18 40. a=rtpmap:101 telephone-event/8000. a=sendrecv. # U 2005/11/28 13:55:40.105264 195.37.77.99:5060 -> 213.239.207.29:5060 SIP/2.0 100 trying -- your call is important to us. Via: SIP/2.0/UDP 213.239.207.29;branch=z9hG4bKe52f.c88e2d42.0;rport=5060. Via: SIP/2.0/UDP 83.136.33.3:8722;branch=z9hG4bK-d87543-5b192d3a37574d15-1--d87543-;rport=8722. To: <sip:klaus3000@iptel.org>. From: "klaus dk.labs.nic.at"<sip:klaus@dk.labs.nic.at>;tag=a83eae01. Call-ID: 9843d9424930591d@a2xhdXNwYw... CSeq: 1 INVITE. Server: Sip EXpress router (0.9.0udpfifo (i386/linux)). Content-Length: 0. Warning: 392 195.37.77.99:5060 "Noisy feedback tells: pid=16799 req_src_ip=213.239.207.29 req_src_port=5060 in_uri=sip:klaus3000@iptel.org out_uri=sip:klaus3000@192.168.2.3:5061 via_cnt==2". . # U 2005/11/28 13:55:40.956023 195.37.77.99:5060 -> 213.239.207.29:5060 SIP/2.0 180 Ringing. To: <sip:klaus3000@iptel.org>;tag=5afee18c3cf2167ei1. From: "klaus dk.labs.nic.at"<sip:klaus@dk.labs.nic.at>;tag=a83eae01. Call-ID: 9843d9424930591d@a2xhdXNwYw... CSeq: 1 INVITE. Via: SIP/2.0/UDP 213.239.207.29;rport=5060;branch=z9hG4bKe52f.c88e2d42.0. Via: SIP/2.0/UDP 83.136.33.3:8722;branch=z9hG4bK-d87543-5b192d3a37574d15-1--d87543-;rport=8722. Record-Route: <sip:195.37.77.99;ftag=a83eae01;lr=on>. Record-Route: <sip:213.239.207.29;ftag=a83eae01;lr=on>. Server: Sipura/SPA2000-3.1.2(NTb). Content-Length: 0. P-NAT-Check: YES. . # U 2005/11/28 13:55:40.958703 213.239.207.29:5060 -> 83.136.33.3:8722 SIP/2.0 180 Ringing. To: <sip:klaus3000@iptel.org>;tag=5afee18c3cf2167ei1. From: "klaus dk.labs.nic.at"<sip:klaus@dk.labs.nic.at>;tag=a83eae01. Call-ID: 9843d9424930591d@a2xhdXNwYw... CSeq: 1 INVITE. Via: SIP/2.0/UDP 83.136.33.3:8722;branch=z9hG4bK-d87543-5b192d3a37574d15-1--d87543-;rport=8722. Record-Route: <sip:195.37.77.99;ftag=a83eae01;lr=on>. Record-Route: <sip:213.239.207.29;ftag=a83eae01;lr=on>. Server: Sipura/SPA2000-3.1.2(NTb). Content-Length: 0. P-NAT-Check: YES. .

2 2

[Serusers] Does SER support TLS?
by Chueh, Weihsin 29 Nov '05

29 Nov '05

Hi All, I download the latest version of SER, 0.9.4, but do not see anything about TLS in ser.cfg file. Does SER support TLS? If it does, how to configure and install SER with TLS feature ON? Thanks, Weihsin Chueh HMP Function Test, Intel 1515 Route 10, Parsippany, NJ 07045 973-967-6243 mailto: <mailto:weihsin.chueh@intel.com> weihsin.chueh(a)intel.com

3 2

[Serusers] rfc3264 and nathelper module
by harry gaillac 28 Nov '05

28 Nov '05

Hello, Does nathelper module would support rfc3264 to provide MOH ? Harry ___________________________________________________________________________ Appel audio GRATUIT partout dans le monde avec le nouveau Yahoo! Messenger Téléchargez cette version sur http://fr.messenger.yahoo.com

2 1

[Users] OpenSER 1.0.0 compile failure?
by Matt Schulte 28 Nov '05

28 Nov '05

All, I browsed around on google and saw no mention of this problem. When compiling I get: gcc -g -O9 -funroll-loops -Wcast-align -Wall -minline-all-stringops -malign-double -falign-loops -mcpu=athlon -DNAME='"openser"' -DVERSION='"1.0.0"' -DARCH='"i386"' -DOS='"linux"' -DCOMPILER='"gcc 3.3"' -D__CPU_i386 -D__OS_linux -DCFG_DIR='"/usr/local/etc/openser/"' -DPKG_MALLOC -DSHM_MEM -DSHM_MMAP -DDNS_IP_HACK -DUSE_MCAST -DDISABLE_NAGLE -DHAVE_RESOLV_RES -DF_MALLOC -DFAST_LOCK -DADAPTIVE_WAIT -DADAPTIVE_WAIT_LOOPS=1024 -DHAVE_GETHOSTBYNAME2 -DHAVE_UNION_SEMUN -DHAVE_SCHED_YIELD -DHAVE_MSG_NOSIGNAL -DHAVE_MSGHDR_MSG_CONTROL -DHAVE_ALLOCA_H -c msg_translator.c -o msg_translator.o msg_translator.c: In function `build_req_buf_from_sip_req': msg_translator.c:1339: error: `id_buf' undeclared (first use in this function) msg_translator.c:1339: error: (Each undeclared identifier is reported only once msg_translator.c:1339: error: for each function it appears in.) msg_translator.c:1340: error: `id_len' undeclared (first use in this function) make: *** [msg_translator.o] Error 1 Simple enough error, any suggestions? I am running: Fedora Core 2 (yum updated of course) gcc 3.3.3 Thanks!

2 2

[Serusers] RADIATOR + LDAP +SER
by Alan Baker 28 Nov '05

28 Nov '05

I configured SER for authentication through RADIATOR to LDAP. I am kind of stumped in regards to the User-Name attribute that is given to the Radius server with the realm attached. Is there a way to send only the username portion? I have included the output from debug. I would appropriate any information. Thanks, Alan -------------------------------------------------------------------------- Mon Nov 28 14:32:44 2005: DEBUG: Reading dictionary file '/etc/radiator/dictionary' Mon Nov 28 14:32:44 2005: DEBUG: Creating authentication port 0.0.0.0:1645 Mon Nov 28 14:32:44 2005: DEBUG: Creating accounting port 0.0.0.0:1646 Mon Nov 28 14:32:44 2005: NOTICE: Server started: Radiator 3.13 on sip (LOCKED) Mon Nov 28 14:32:51 2005: DEBUG: Packet dump: *** Received from 127.0.0.1 port 33032 .... Code: Access-Request Identifier: 247 Authentic: <210>E<8>@m<211>h<133><34><23><16><21><28><242><187><154> Attributes: User-Name = "alan(a)sip.domain.com" Digest-Attributes = "<10><6>alan" Digest-Attributes = "<1><19>sip.domain.com" Digest-Attributes = "<2>*438b5c8fa0ca1bassjsjskakad74ec2c2bd0" Digest-Attributes = "<4><23>sip:sip.domain.com" Digest-Attributes = "<3><10>REGISTER" Digest-Response = "c469a2464876sska898jkdsjs889" Service-Type = Sip-Session Sip-Uri-User = "alan" NAS-IP-Address = UNKNOWN NAS-Port = 5060 Mon Nov 28 14:32:51 2005: DEBUG: Handling request with Handler 'Realm=DEFAULT' Mon Nov 28 14:32:51 2005: DEBUG: Deleting session for alan(a)sip.domain.com, UNKNOWN, 5060 Mon Nov 28 14:32:51 2005: DEBUG: Handling with Radius::AuthLDAP2: Mon Nov 28 14:32:51 2005: INFO: Connecting to ldap.domain.com, port 389 Mon Nov 28 14:32:51 2005: INFO: Attempting to bind to LDAP server ldap.domain.com:389 Mon Nov 28 14:32:51 2005: ERR: ldap search failed with error LDAP_PARAM_ERROR. Mon Nov 28 14:32:51 2005: ERR: LDAP_PARAM_ERROR Mon Nov 28 14:32:51 2005: DEBUG: Radius::AuthLDAP2 looks for match with alan(a)sip.domain.com Mon Nov 28 14:32:51 2005: ERR: ldap search failed with error LDAP_PARAM_ERROR. Mon Nov 28 14:32:51 2005: ERR: LDAP_PARAM_ERROR Mon Nov 28 14:32:51 2005: DEBUG: AuthBy LDAP2 result: REJECT, No such user Mon Nov 28 14:32:51 2005: INFO: Access rejected for alan(a)sip.domain.com: No such user Mon Nov 28 14:32:51 2005: DEBUG: Packet dump: *** Sending to 127.0.0.1 port 33032 .... Code: Access-Reject Identifier: 247 Authentic: <210>E<8>@m<211>h<133><34><23><16><21><28><242><187><154> Attributes: Reply-Message = "Request Denied"

1 0

← Newer
1
...
5
6
7
8
9
10
11
...
58
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 2005