sr-users December 2008

sr-users@lists.kamailio.org

73 participants
107 discussions

[Serusers] from header as append_hf() param

by caio

Hi all, Is it possible to add the current from header (%fu or $fu) or contact header as parameter of the append_hf textops function? I need to add a custom header like the following: append_hf("P-Asserted-Identity: \"Caller guy\" <%fu>); Result: ...P-Asserted-Identity: "Caller guy" <123(a)10.3.23.5>) There is an "append_urihf()" but it adds as prefix or suffix the R-URI address. Important, SER version 0.9.7. Regards, Claudio

15 years, 10 months

[Serusers] get uri in module

by Netadmin Bensoft

Hello, I made a module and i want to get the uri from sip msg. How can i do this? What i need is the phone from uri or the uri (sip:1234@sip.sip.com) I've tried get_to(msg)->uri.s but it doesn't return the uri.. Thanks.

15 years, 10 months

[Kamailio-Users] drop() and tm timers.

by Aurelien Grimaud

Hi, In my openser, I had to not relay any provisional which is < 180. I used drop in reply route to do this. No provisional < 180 is sent to caller. Unfortunately, dropping 100 seems to make the transaction module not disarming its fr_timer. The 180 has been waited for more time than my fr_timer so request failed and failure_route was called. In fact, there is no 180, only a 200 ok. Can anyone confirm that disarming timer is *not* done if 100 is dropped ? This is openser 1.2.1 Regards. Aurelien

15 years, 10 months

[Kamailio-Users] "Failed" acc log when 183 Session Progress

by Samuel Muller

Hello all, I just have a little question about this thing : when I start a call, my Radius receives before the session is established a "failed" in its accounting log. If I move the setflag() for rad acc and rad failed acc (or one of each, then the other one), the "Start" disappear - but I get the Stop. How to not take acc in charge when there is a 183 Session Progress ? here is the radius acc log : Code: Accounting-Request Identifier: 102 Authentic: Z3z<16>^<230><251>i<233>[6Q<196><12><140><25> Attributes: Acct-Status-Type = Failed Service-Type = Sip-Session Sip-Response-Code = 183 Sip-Method = "<1>" Event-Timestamp = 1230128211 Sip-From-Tag = "a3addce43738cc27o0" Sip-To-Tag = "1c782477072" Acct-Session-Id = "10bdf568-2821ed73(a)192.168.1.7" Sip-Method = "INVITE" SER-From = "0170645745" SER-To = "0663128505" Sip-User-Digest-URI = "sip:0663128505@sip.720.fr<sip%3A0663128505(a)sip.720.fr> " Sip-Req-URI = "sip:0663128505@77.246.81.136:5060;transport=udp" Sip-Source-IP-Address = "87.90.4.63" Sip-Source-Port = "5060" NAS-Port = 5060 Acct-Delay-Time = 0 NAS-IP-Address = 192.168.60.9 the setflag() are here : if (is_method("INVITE")) { setflag(4); # flag "radius acc" setflag(5); # flag "radius failed acc" setflag(8); # flag "dialog" setflag(9); # flag "session timer" route(13); } the only place I found the related "183" taken in charge in the kamailio.cfg is here : onreply_route[2] { if (nat_uac_test("1")) { fix_nated_contact(); } if (isbflagset(14) && status =~ "(180|183|2[0-9][0-9])") #? branch flag nat { if (!search("^Content-Length:[ ]*0")) { force_rtp_proxy(); } } exit; } in the kamailio log for this same call : Dec 24 15:16:51 ser0 kamailio[7748]: DBG:core:parse_msg: SIP Reply (status): Dec 24 15:16:51 ser0 kamailio[7748]: DBG:core:parse_msg: version: <SIP/2.0> Dec 24 15:16:51 ser0 kamailio[7748]: DBG:core:parse_msg: status: <100> Dec 24 15:16:51 ser0 kamailio[7748]: DBG:core:parse_msg: reason: <Trying> Dec 24 15:16:51 ser0 kamailio[7748]: DBG:core:parse_headers: flags=2 Dec 24 15:16:51 ser0 kamailio[7748]: DBG:core:parse_via_param: found param type 232, <branch> = <z9hG4bKbe63.1eddc1f3.0>; state=16 Dec 24 15:16:51 ser0 kamailio[7748]: DBG:core:parse_via: end of header reached, state=5 Dec 24 15:16:51 ser0 kamailio[7748]: DBG:core:parse_headers: via found, flags=2 Dec 24 15:16:51 ser0 kamailio[7748]: DBG:core:parse_headers: this is the first via Dec 24 15:16:51 ser0 kamailio[7748]: DBG:core:receive_msg: After parse_msg... Dec 24 15:16:51 ser0 kamailio[7748]: DBG:core:grep_sock_info: checking if host==us: 13==13 && [77.246.81.132] == [77.246.81.132] Dec 24 15:16:51 ser0 kamailio[7748]: DBG:core:grep_sock_info: checking if port 5060 matches port 5060 Dec 24 15:16:51 ser0 kamailio[7748]: DBG:core:forward_reply: found module tm, passing reply to it Dec 24 15:16:51 ser0 kamailio[7748]: DBG:tm:t_check: start=0xffffffffffffffff Dec 24 15:16:51 ser0 kamailio[7748]: DBG:core:parse_headers: flags=22 Dec 24 15:16:51 ser0 kamailio[7748]: DBG:core:parse_via_param: found param type 235, <rport> = <5060>; state=6 Dec 24 15:16:51 ser0 kamailio[7748]: DBG:core:parse_via_param: found param type 234, <received> = <87.90.4.63>; state=6 Dec 24 15:16:51 ser0 kamailio[7748]: DBG:core:parse_via_param: found param type 232, <branch> = <z9hG4bK-8aeb8bb>; state=16 Dec 24 15:16:51 ser0 kamailio[7748]: DBG:core:parse_via: end of header reached, state=5 Dec 24 15:16:51 ser0 kamailio[7748]: DBG:core:parse_headers: via found, flags=22 Dec 24 15:16:51 ser0 kamailio[7748]: DBG:core:parse_headers: parse_headers: this is the second via Dec 24 15:16:51 ser0 kamailio[7748]: DBG:core:parse_to_param: tag=1c782477072 Dec 24 15:16:51 ser0 kamailio[7748]: DBG:core:parse_to: end of header reached, state=29 Dec 24 15:16:51 ser0 kamailio[7748]: DBG:core:parse_to: display={"0663128505"}, ruri={sip:0663128505@sip.720.fr<sip%3A0663128505(a)sip.720.fr>} Dec 24 15:16:51 ser0 kamailio[7748]: DBG:core:get_hdr_field: <To> [58]; uri=[sip:0663128505@sip.720.fr <sip%3A0663128505(a)sip.720.fr>] Dec 24 15:16:51 ser0 kamailio[7748]: DBG:core:get_hdr_field: to body ["0663128505" <sip:0663128505@sip.720.fr <sip%3A0663128505(a)sip.720.fr>>] Dec 24 15:16:51 ser0 kamailio[7748]: DBG:core:get_hdr_field: cseq <CSeq>: <102> <INVITE> Dec 24 15:16:51 ser0 kamailio[7748]: DBG:core:parse_headers: flags=8 Dec 24 15:16:51 ser0 kamailio[7748]: DBG:tm:t_reply_matching: hash 14059 label 1058856417 branch 0 Dec 24 15:16:51 ser0 kamailio[7748]: DBG:tm:t_reply_matching: REF_UNSAFE: after is 1 Dec 24 15:16:51 ser0 kamailio[7748]: DBG:tm:t_reply_matching: reply matched (T=0x7fcc45ebb090)! Dec 24 15:16:51 ser0 kamailio[7748]: DBG:tm:run_trans_callbacks: trans=0x7fcc45ebb090, callback type 2, id 1 entered Dec 24 15:16:51 ser0 kamailio[7748]: DBG:tm:t_check: end=0x7fcc45ebb090 Dec 24 15:16:51 ser0 kamailio[7748]: DBG:tm:reply_received: org. status uas=0, uac[0]=0 local=0 is_invite=1) Dec 24 15:16:51 ser0 kamailio[7748]: -NAT-ONREPLY----------------------------- Dec 24 15:16:51 ser0 kamailio[7748]: DBG:core:parse_headers: flags=80 Dec 24 15:16:51 ser0 kamailio[7748]: DBG:core:get_hdr_field: content_length=0 Dec 24 15:16:51 ser0 kamailio[7748]: DBG:core:get_hdr_field: found end of header Dec 24 15:16:51 ser0 kamailio[7748]: DBG:tm:t_should_relay_response: T_code=0, new_code=100 Dec 24 15:16:51 ser0 kamailio[7748]: DBG:tm:relay_reply: branch=0, save=0, relay=-1 Dec 24 15:16:51 ser0 kamailio[7748]: DBG:tm:set_timer: relative timeout is 60 Dec 24 15:16:51 ser0 kamailio[7748]: DBG:tm:insert_timer_unsafe: [1]: 0x7fcc45ebb2e0 (95) Dec 24 15:16:51 ser0 kamailio[7748]: DBG:tm:t_unref: UNREF_UNSAFE: after is 0 Dec 24 15:16:51 ser0 kamailio[7748]: DBG:core:destroy_avp_list: destroying list (nil) Dec 24 15:16:51 ser0 kamailio[7748]: DBG:core:receive_msg: cleaning up Dec 24 15:16:51 ser0 kamailio[7747]: DBG:core:parse_msg: SIP Reply (status): Dec 24 15:16:51 ser0 kamailio[7747]: DBG:core:parse_msg: version: <SIP/2.0> Dec 24 15:16:51 ser0 kamailio[7747]: DBG:core:parse_msg: status: <183> Dec 24 15:16:51 ser0 kamailio[7747]: DBG:core:parse_msg: reason: <Session Progress> Dec 24 15:16:51 ser0 kamailio[7747]: DBG:core:parse_headers: flags=2 Dec 24 15:16:51 ser0 kamailio[7747]: DBG:core:parse_via_param: found param type 232, <branch> = <z9hG4bKbe63.1eddc1f3.0>; state=16 Dec 24 15:16:51 ser0 kamailio[7747]: DBG:core:parse_via: end of header reached, state=5 Dec 24 15:16:51 ser0 kamailio[7747]: DBG:core:parse_headers: via found, flags=2 Dec 24 15:16:51 ser0 kamailio[7747]: DBG:core:parse_headers: this is the first via Dec 24 15:16:51 ser0 kamailio[7747]: DBG:core:receive_msg: After parse_msg... Dec 24 15:16:51 ser0 kamailio[7747]: DBG:core:grep_sock_info: checking if host==us: 13==13 && [77.246.81.132] == [77.246.81.132] Dec 24 15:16:51 ser0 kamailio[7747]: DBG:core:grep_sock_info: checking if port 5060 matches port 5060 Dec 24 15:16:51 ser0 kamailio[7747]: DBG:core:forward_reply: found module tm, passing reply to it Dec 24 15:16:51 ser0 kamailio[7747]: DBG:tm:t_check: start=0xffffffffffffffff Dec 24 15:16:51 ser0 kamailio[7747]: DBG:core:parse_headers: flags=22 Dec 24 15:16:51 ser0 kamailio[7747]: DBG:core:parse_via_param: found param type 235, <rport> = <5060>; state=6 Dec 24 15:16:51 ser0 kamailio[7747]: DBG:core:parse_via_param: found param type 234, <received> = <87.90.4.63>; state=6 Dec 24 15:16:51 ser0 kamailio[7747]: DBG:core:parse_via_param: found param type 232, <branch> = <z9hG4bK-8aeb8bb>; state=16 Dec 24 15:16:51 ser0 kamailio[7747]: DBG:core:parse_via: end of header reached, state=5 Dec 24 15:16:51 ser0 kamailio[7747]: DBG:core:parse_headers: via found, flags=22 Dec 24 15:16:51 ser0 kamailio[7747]: DBG:core:parse_headers: parse_headers: this is the second via Dec 24 15:16:51 ser0 kamailio[7747]: DBG:core:parse_to_param: tag=1c782477072 Dec 24 15:16:51 ser0 kamailio[7747]: DBG:core:parse_to: end of header reached, state=29 Dec 24 15:16:51 ser0 kamailio[7747]: DBG:core:parse_to: display={"0663128505"}, ruri={sip:0663128505@sip.720.fr<sip%3A0663128505(a)sip.720.fr>} Dec 24 15:16:51 ser0 kamailio[7747]: DBG:core:get_hdr_field: <To> [58]; uri=[sip:0663128505@sip.720.fr <sip%3A0663128505(a)sip.720.fr>] Dec 24 15:16:51 ser0 kamailio[7747]: DBG:core:get_hdr_field: to body ["0663128505" <sip:0663128505@sip.720.fr <sip%3A0663128505(a)sip.720.fr>>] Dec 24 15:16:51 ser0 kamailio[7747]: DBG:core:get_hdr_field: cseq <CSeq>: <102> <INVITE> Dec 24 15:16:51 ser0 kamailio[7747]: DBG:core:parse_headers: flags=8 Dec 24 15:16:51 ser0 kamailio[7747]: DBG:tm:t_reply_matching: hash 14059 label 1058856417 branch 0 Dec 24 15:16:51 ser0 kamailio[7747]: DBG:tm:t_reply_matching: REF_UNSAFE: after is 1 Dec 24 15:16:51 ser0 kamailio[7747]: DBG:tm:t_reply_matching: reply matched (T=0x7fcc45ebb090)! Dec 24 15:16:51 ser0 kamailio[7747]: DBG:tm:run_trans_callbacks: trans=0x7fcc45ebb090, callback type 2, id 1 entered Dec 24 15:16:51 ser0 kamailio[7747]: DBG:core:parse_headers: flags=8 Dec 24 15:16:51 ser0 kamailio[7747]: DBG:tm:t_check: end=0x7fcc45ebb090 Dec 24 15:16:51 ser0 kamailio[7747]: DBG:tm:reply_received: org. status uas=0, uac[0]=100 local=0 is_invite=1) Dec 24 15:16:51 ser0 kamailio[7747]: -NAT-ONREPLY----------------------------- Dec 24 15:16:51 ser0 kamailio[7747]: DBG:core:parse_headers: flags=80 Dec 24 15:16:51 ser0 kamailio[7747]: DBG:core:parse_headers: flags=ffffffffffffffff Dec 24 15:16:51 ser0 kamailio[7747]: DBG:core:get_hdr_field: content_length=293 Dec 24 15:16:51 ser0 kamailio[7747]: DBG:core:get_hdr_field: found end of header Dec 24 15:16:51 ser0 kamailio[7747]: DBG:nathelper:check_content_type: type <application/sdp> found valid Dec 24 15:16:51 ser0 kamailio[7747]: DBG:core:parse_headers: flags=40 Dec 24 15:16:51 ser0 kamailio[7747]: DBG:core:parse_to_param: tag=a3addce43738cc27o0 Dec 24 15:16:51 ser0 kamailio[7747]: DBG:core:parse_to: end of header reached, state=29 Dec 24 15:16:51 ser0 kamailio[7747]: DBG:core:parse_to: display={"0170645745"}, ruri={sip:0170645745@sip.720.fr<sip%3A0170645745(a)sip.720.fr>} Dec 24 15:16:51 ser0 kamailio[7747]: DBG:nathelper:force_rtp_proxy2_f: proxy reply: 35934 77.246.81.133 Dec 24 15:16:51 ser0 kamailio[7747]: DBG:tm:t_should_relay_response: T_code=0, new_code=183 Dec 24 15:16:51 ser0 kamailio[7747]: DBG:tm:relay_reply: branch=0, save=0, relay=0 Dec 24 15:16:51 ser0 kamailio[7747]: DBG:tm:run_trans_callbacks: trans=0x7fcc45ebb090, callback type 16, id 0 entered Dec 24 15:16:51 ser0 kamailio[7747]: DBG:dialog:run_dlg_callbacks: dialog=0x7fcc45ebc7c0, type=256 Dec 24 15:16:51 ser0 kamailio[7747]: DBG:sst:sst_dialog_response_fwded_CB: Dialog seen REPLY 183 Session Progress Dec 24 15:16:51 ser0 kamailio[7747]: DBG:core:parse_headers: flags=2000 Dec 24 15:16:51 ser0 kamailio[7747]: DBG:core:parse_headers: flags=ffffffffffffffff Dec 24 15:16:51 ser0 kamailio[7747]: DBG:core:clen_builder: content-length: 311 (311) Dec 24 15:16:51 ser0 kamailio[7747]: DBG:core:build_res_buf_from_sip_res: old size: 1027, new size: 983 Dec 24 15:16:51 ser0 kamailio[7747]: DBG:core:build_res_buf_from_sip_res: copied size: orig:1025, new: 981, rest: 2 msg= SIP/2.0 183 Session Progress^M Via: SIP/2.0/UDP 192.168.1.7:5060;rport=5060;received=87.90.4.63;branch=z9hG4bK-8aeb8bb^M From: "0170645745" <sip:0170645745@sip.720.fr <sip%3A0170645745(a)sip.720.fr>>;tag=a3addce43738cc27o0^M To: "0663128505" <sip:0663128505@sip.720.fr <sip%3A0663128505(a)sip.720.fr>>;tag=1c782477072^M Call-ID: 10bdf568-2821ed73(a)192.168.1.7^M CSeq: 102 INVITE^M Contact: < sip:61@77.246.81.136 <sip%3A61(a)77.246.81.136>>^M Record-Route: <sip:77.246.81.132;lr=on;ftag=a3addce43738cc27o0;nat=yes;did=17a.36b075d2>^M Supported: em,timer,replaces,path,resource-priority^M Allow: REGISTER,OPTIONS,INVITE,ACK,CANCEL,BYE,NOTIFY,PRACK,REFER,INFO,SUBSCRIBE,UPDATE^M Server: 720 DEGRES PSTN GW/v.5.40A.030.002^M Content-Type: application/sdp^M Content-Length: 311^M ^M v=0^M o=AudiocodesGW 782585440 782585110 IN IP4 77.246.81.136^M s=Phone-Call^M c=IN IP4 77.246.81.133^M t=0 0^M m=audio 35934 RTP/AVP 18 101^M a=rtpmap:18 G729/8000^M a=fmtp:18 annexb=yes^M a=rtpmap:101 telephone-event/ Dec 24 15:16:51 ser0 kamailio[7747]: DBG:core:_shm_resize: resize(0) called Dec 24 15:16:51 ser0 kamailio[7747]: DBG:tm:relay_reply: sent buf=0x7936d8: SIP/2.0 1..., shmem=0x7fcc45ebef00: SIP/2.0 1 Dec 24 15:16:51 ser0 kamailio[7747]: DBG:tm:run_trans_callbacks: trans=0x7fcc45ebb090, callback type 128, id 1 entered Dec 24 15:16:51 ser0 kamailio[7747]: DBG:core:parse_headers: flags=14000 Dec 24 15:16:51 ser0 kamailio[7747]: DBG:tm:run_trans_callbacks: trans=0x7fcc45ebb090, callback type 128, id 0 entered Dec 24 15:16:51 ser0 kamailio[7747]: DBG:dialog:next_state_dlg: dialog 0x7fcc45ebc7c0 changed from state 1 to state 2, due event 2 Dec 24 15:16:51 ser0 kamailio[7747]: DBG:tm:set_timer: relative timeout is 60 Dec 24 15:16:51 ser0 kamailio[7747]: DBG:tm:insert_timer_unsafe: [1]: 0x7fcc45ebb2e0 (96) Dec 24 15:16:51 ser0 kamailio[7747]: DBG:tm:t_unref: UNREF_UNSAFE: after is 0 Dec 24 15:16:51 ser0 kamailio[7747]: DBG:core:destroy_avp_list: destroying list (nil) Dec 24 15:16:51 ser0 kamailio[7747]: DBG:core:receive_msg: cleaning up Dec 24 15:16:51 ser0 kamailio[7753]: DBG:tm:utimer_routine: timer routine:4,tl=0x7fcc45ebb2b0 next=(nil), timeout=36400000 -- Samuel MULLER sml(a)720.fr

15 years, 10 months

[Kamailio-Users] snmpstats error

by Stagg Shelton

I am planning an upgrade from openser 1.3.4 to kamailio 1.4.3, and I am having an issue starting kamailio with snmpstats enabled. I find the errors below in the kamailio syslog file. It looks like the root issue is a missing symbol, but I have not been able to figure out what provides the symbol. Openser 1.3.4 works fine on the same machine with essentially the same configuration that I am wanting to use for kamailio. The snmpstats.so module compiled without any errors, and is located in the /lib/ kamailio/modules/ directory. The system is fedora core 6 fully yum updated. Dec 24 14:24:26 sip-interop-c61-atl kamailio: ERROR:core:sr_load_module: could not open module <//lib/kamailio/ modules/snmpstats.so>: /usr/lib/libnetsnmpagent.so.10: undefined symbol: make_tempfile Dec 24 14:24:26 sip-interop-c61-atl kamailio: CRITICAL:core:yyerror: parse error in config file, line 57, column 13-14: failed to load module Dec 24 14:24:26 sip-interop-c61-atl kamailio: ERROR:core:set_mod_param_regex: no module matching snmpstats found | Dec 24 14:24:26 sip-interop-c61-atl kamailio: CRITICAL:core:yyerror: parse error in config file, line 142, column 20-21: Can't set module parameter Dec 24 14:24:26 sip-interop-c61-atl kamailio: ERROR:core:set_mod_param_regex: no module matching snmpstats found | Dec 24 14:24:26 sip-interop-c61-atl kamailio: CRITICAL:core:yyerror: parse error in config file, line 143, column 20-21: Can't set module parameter Dec 24 14:24:26 sip-interop-c61-atl kamailio: ERROR:core:set_mod_param_regex: no module matching snmpstats found | Dec 24 14:24:26 sip-interop-c61-atl kamailio: CRITICAL:core:yyerror: parse error in config file, line 144, column 20-21: Can't set module parameter Dec 24 14:24:26 sip-interop-c61-atl kamailio: ERROR:core:set_mod_param_regex: no module matching snmpstats found | Dec 24 14:24:26 sip-interop-c61-atl kamailio: CRITICAL:core:yyerror: parse error in config file, line 145, column 20-21: Can't set module parameter Dec 24 14:24:26 sip-interop-c61-atl kamailio: ERROR:core:main: bad config file (5 errors) Has anyone seen this error, or something similar? Thank You Stagg Shelton www.sheltonjohns.com

15 years, 10 months

[Kamailio-Users] sub:Query on PUA

by skumar453＠gmail.com

Hi All, HAPPY CHRISTMAS , I am working on PUA module.I am running PUA as Apllication server.I have registered ALICE in a client which doesn't have presence support (OpenIC client) and BOB in UCTIMSCLIENT which has presence support.And i am invoking SUBSCRIBE message by a script file to know the presence of BOB to ALICE. When the status of BOB is changed,NOTIFY is getting Terminated at I-CSCF. ERROR i am getting is : "406 Initial Request Method not allowed atthe I-CSCF". According to traces while registration flow is as follows: FLOW 1: PUA------>i-cscf------>s-cscf. But actually the flow should be: FLOW 2: PUA------>p-cscf------>s-cscf. I have enabled outbound proxy server in configuration file to get FLOW 2.But,the flow is not changed. Kindly let me know ,how to get NOTIFY message when status of BOB is changed. Thanks in Advance.

15 years, 10 months

Re: [Kamailio-Users] [Kamailio-Devel] new module: qos

by Daniel-Constantin Mierla

Thanks Ovidiu, readme is online at: http://kamailio.org/docs/modules/devel/qos.html Is the module keeping track of all session negotiated, or is stores the last one (used)? Happy holidays! Daniel On 12/23/08 23:05, Ovidiu Sas wrote: > Hello, > > QoS is an new module that can be used to track per dialog SDP sessions. > The QoS module is sitting on top of the dialog module and provides an > API to be used by other module. > The QoS module does not provide any scripting functionality (it is a > passive module). > See the module documentation for more informations. > > SDP session(s) can be inspected via the dialog dlg_list_ctx MI > interface command: > dialog:: hash=3732:573385728 > state:: 4 > timestart:: 1230068558 > timeout:: 1009 > callid:: d3d816cce3e24a19b937b56e4689e524 > from_uri:: sip:111111111@10.11.10.63 > from_tag:: 8c85c079 > caller_contact:: sip:111111111@10.11.128.129 > caller_cseq:: 100 > caller_route_set:: > caller_bind_addr:: udp:10.11.10.63:5060 > to_uri:: sip:222222222@10.11.10.63 > to_tag:: 43FED9C4-20CF > callee_contact:: sip:222222222@10.111.3.241:5060 > callee_cseq:: 100 > callee_route_set:: > callee_bind_addr:: udp:10.11.10.63:5060 > context:: > qos:: negotiated_sdp > sdp:: m_dir=1 m_id=1 method=INVITE cseq=100 > negotiation=1 > session:: callee cnt_disp= bw_type= > bw_width= streams=2 > stream:: 1 media=video > IP=10.111.3.241 port=0 transport=RTP/AVP payloads_num=0 > stream:: 0 media=audio > IP=10.111.3.241 port=17240 transport=RTP/AVP payloads_num=3 > payload:: 2 rtpmap=100 > codec=X-NSE > payload:: 1 rtpmap=101 > codec=telephone-event > payload:: 0 rtpmap=0 codec=PCMU > session:: caller cnt_disp= bw_type=AS > bw_width=400 streams=2 > stream:: 1 media=video > IP=10.11.128.129 port=22804 transport=RTP/AVP payloads_num=2 > payload:: 1 rtpmap=34 codec=H263 > payload:: 0 rtpmap=107 > codec=H263-1998 > stream:: 0 media=audio > IP=10.11.128.129 port=22800 transport=RTP/AVP payloads_num=12 > payload:: 11 > rtpmap=112 codec=iLBC > payload:: 10 > rtpmap=100 codec=AMR > payload:: 9 rtpmap=13 codec=CN > payload:: 8 rtpmap=101 > codec=telephone-event > payload:: 7 rtpmap=111 > codec=G726-40 > payload:: 6 rtpmap=110 > codec=G726-32 > payload:: 5 rtpmap=109 > codec=G726-24 > payload:: 4 rtpmap=108 > codec=G726-16 > payload:: 3 rtpmap=4 codec=G723 > payload:: 2 rtpmap=18 codec=G729 > payload:: 1 rtpmap=0 codec=PCMU > payload:: 0 rtpmap=8 codec=PCMA > > > > Regards, > Ovidiu Sas > > _______________________________________________ > Devel mailing list > Devel(a)lists.kamailio.org > http://lists.kamailio.org/cgi-bin/mailman/listinfo/devel > > -- Daniel-Constantin Mierla http://www.asipto.com

15 years, 10 months

[Kamailio-Users] Merry Christmas and Happy New Year 2009!

by Daniel-Constantin Mierla

Hello, I wish everyone Merry Christmas and Happy New Year 2009! Day by day, we ended another year. 2008 was full of events, starting with one major release and six minor releases, participation to workshops and conferences wordlwide, adoption in new production environments and acknowledgement of running platforms with millions of users and billions of routed minutes/month using Kamailio (OpenSER), check the News archive at: http://www.kamailio.org There were sad events as well, including the hijacking of the old domain name after the rename in Kamailio, still the source forge project goes on, with same name, proving the genuine openser project: https://sourceforge.net/projects/openser/ We maintained release 1.3.x series, last being 1.3.4, which still keeps the old name and is available at: http://www.openser-project.org/mos/view/News/NewsItem/OpenSER-v1.3.4-Releas… Life is going on, since the latest major release, version 1.4.0, the project boosted in new features, a summary of what is new since then is available here: http://www.kamailio.org/dokuwiki/doku.php/features:new-in-1.5.x An important share of effort was directed to clean the code and improve the stability and performance, a proof of maturity and the need to make the maintenance of the project easier and open for new comers. Lot of documentation was added in doxygen format inside the source code, Devel Guide was published, new developers can start new easier to enhance the application. Reference moment for the future was the launch of SIP Router project in November - a concentration of many people with great SIP and VoIP expertise, backed up by huge programming experience in this field. This came to strengthen the development workforce, to ensure the reliability, to remove the doubts of what projects is better now or is going to develop better in the future. http://sip-router.org So, 2009 is an year that announces already great achievements to be done in its first half: - 1st Quarter - release of Kamailio (OpenSER) 1.5.0 - 2nd Quarter - release of SIP Router project as stable version - dedicated meeting to celebrate the first operational SIP Router and draw future directions With the release of SIP Router project, everyone gets access to the features provided by Kamailio (OpenSER), SIP Express Router and OpenIMSCore projects: http://sip-router.org/benefits/ Looking forward to a fruitful 2009! Daniel -- Daniel-Constantin Mierla http://www.asipto.com

15 years, 11 months

[Kamailio-Users] how to bild "pidf" for network elements

by skumar453＠gmail.com

Hi all I am developing presence network agent(PNA)..IT collects the presence information from the core network elements like Serving-call session control function(scscf)..and home subscriber server(HSS). and it will construct the publish message and send it to the Presence server(PS). here my doubt is what should be the content in the publish message for network presence? can any one suggest how to do it ? and can anyone let me know, whether there are any RFC or Specification for constructing PUBLISH message for network elements? thank you in advance suresh

15 years, 11 months

[Kamailio-Users] Using a b2bua as a prepaid box

by Luciano Afranllie

Hi everybody, I am experimenting trying to build a prepaid solution using prepaid extension for RADIUS (IETF draft). My current test bed is Kamailio as SIP proxy/registrar, asterisk as PSTN gateway, sippy b2bua and a freeRadius server. What I am thinking about is to split users in groups (prepaid, postpaid and suspended, for example) and to send all calls from prepaid users to the b2bua. The b2bua will have the prepaid client logic to enforce balance usage and drop calls. I am new in this area so I will appreciate a lot your feedback about what is the best way to do this. - Regarding groups. Is it worth to use radius for this or can I just use kamailio groups? - Regarding sending prepaid users calls to b2bua. It is a nice solution in kamailio to check user group and if it belongs to prepaid group forward the call to b2bua and b2bua forward the call again to kamailio in order to make the final routing? How should I identify the call has already been sent to the b2bua and is coming again to kamailio, just using the source host, or there is a better way? Thanks for your time. L:uciano

15 years, 11 months

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 December 2008