- sr-users - kamailio.org

xavp questions (variables in root/branch)
by Vasiliy Ganchev 25 Jul '17

25 Jul '17

Hi, community! I have a question regarding xavp usage. according to docs, xavp has format: $xavp(root=>branch)="value"; I want to use "root" and "branch" - variables. (as it is implemented with AVPs - the id there, can be variable) e.g.: ... $var(root_key) = "root_1"; $var(branch_key1) = "key_value1"; ... $xavp($var(root_key)[0]=>$var(branch_key1)) = "some_value"; ... Playing around with the script - I found that it is currently impossible (tested with 4.2.5 and 5.2.0 versions). Kamailio interprets variables in "root" and "branch" as static strings. Walking through the mailing list history, I have an impression that xavp are originally designed to operate only with constant keys. The question is: is it planned to add functionality with variables as "root" and "branch" components? Thanks in advance for the answers! Best regards -- View this message in context: http://sip-router.1086192.n5.nabble.com/xavp-questions-variables-in-root-br… Sent from the Users mailing list archive at Nabble.com.

2 4

I_SCSCF_select function dont return the next SCSCF in IMS network!!!
by Mojtaba 25 Jul '17

25 Jul '17

Hello, Today i have a strange problem in IMS network. All nodes (pcscf,icscf,scscf and hss) are configured in independent server. My domain is default(open-ims.test) Now when i want to register bob(a)open-ims.test, I get this error from ICSCF: 500 Error in request. When i saw the log files, i found the icscf could not found the next node(scscf) in registration path. As i defined prefered scscf_uri in configuration file, Why the icscf, could not found the scscf? The dns server works correctly and i have ping of scscf.open-ims.test from icscf node. When i trace the diameter packets, the icscf connect to hss successfully but dont send UAR to hss while registration proccess!! It's strange. Please let me know why i have this problem, Thanks With Regards. -- --Mojtaba Esfandiari.S

2 3

TR: Failure Mode
by Nicolas Breuer 24 Jul '17

24 Jul '17

Hello, Some help here is needed # auto-discard branches from previous serial forking leg modparam("tm", "failure_reply_mode", 3) I test a call with two branches. 1st branch received a 408 timeout error 2nd branch received a 486 busy. Normally the failure route should be with the 486. NOTICE: <script>: Failure route -----2---1--408---- We can see the 408 is the winning reply but I understood from the documentation that if Failure reply mode is "3" , the winning reply is always the reply from the last branch :) It's a problem because if the 1st is timeout (because down), the second is OK but callee is busy ; we don't send the right reply to the caller

2 14

Display name in contact
by Diego Nadares 24 Jul '17

24 Jul '17

Hi guys, Is possible to cut change/delete display name in contact header? Does this breaks something? Cheers, Diego.

3 2

path use_received not working?
by Iskren Hadzhinedev 23 Jul '17

23 Jul '17

Hello, I have a kamailio proxy in front of FreeSWITCH. Whenever FreeSWITCH initiates the dialog (e.g. sends an INVITE), kamailio doesn't use the 'received' parameter and it forwards to the RFC1918 IP address. The initial INVITE from FreeSWITCH has the following headers: To: <sip:1001@192.168.1.200:5063> Route: <sip:1.2.3.4>;lr;received=sip:5.6.7.8:5063 Where 1.2.3.4 is the kamailio public IP and5.6.7.8 is the public IP of the UAC behind NAT. I have modparam("path", "use_received", 1) in my config file and to my understanding that should be sufficient to route to the proper IP, but kamailio keeps sending INVITEs to 192.168.1.200. Can anyone tell me what am I missing? Thanks! Kind regards, Iskren

4 8

Sleep command working
by Nicolas Breuer 21 Jul '17

21 Jul '17

Hello, I'm trying to do a sleep in the request route but seems it's not working if (src_ip == $sel(cfg_get.kamalio2.gw) ){ xlog("L_NOTICE","Sleep 5 seconds"); usleep("5000"); } xlog("L_NOTICE","End of sleeping"); Result : Jul 21 11:38:02 proxy2 /usr/sbin/kamailio[31442]: NOTICE: <script>: Sleep 5 seconds Jul 21 11:38:02 proxy2 /usr/sbin/kamailio[31442]: NOTICE: <script>: End of sleeping Breuer Nicolas Network Supervisor Sales Executive BELCENTER sprl/bvba Operations - NCC 7 Boulevard de France, 1420 Braine - L'Alleud Tel +32 2 403 04 61 Fax +32 2 403 04 63 National Contact Center +32 2 403 04 60

2 1

Re: [SR-Users] Problem with IPv4-IPv6 media bridging using RTPengine
by Ismir Saljic 20 Jul '17

20 Jul '17

On 19/07/17 08:31 AM, Ismir Saljic wrote: >* Hello, *>>* I've issue with bridging media between IPv4 and IPv6 clients. *>* IPv4-IPv4 and IPv6-IPv6 calls are working without issues. *>* I'm using kamailio 4.4.2 and configuration according to: *>* http://kb.asipto.com/kamailio:kamailio-mixed-ipv4-ipv6 <http://kb.asipto.com/kamailio:kamailio-mixed-ipv4-ipv6> *>* <http://kb.asipto.com/kamailio:kamailio-mixed-ipv4-ipv6 <http://kb.asipto.com/kamailio:kamailio-mixed-ipv4-ipv6>> *>>* SIP signalling is working without issues,but media addresses in SDP *>* are not rewritten correctly. *>>* The server is on amazon AWS and both kamailio and RTPengine are on the *>* same server. *>* RTPengine is running using these options: *>>* /usr/sbin/rtpengine --interface=privateIPv4!publicIPv4 *>* --interface=GlobalIPv6 *>* --listen-udp=127.0.0.1:22222 <http://127.0.0.1:22222> <http://127.0.0.1:22222 <http://127.0.0.1:22222>> *>* --tos=184 *>* --pidfile=/var/run/rtpengine.pid *>* --log-level=6 *>* --log-facility=daemon * I would suggest to use Kamailio's rtpengine module instead of rtpproxy, together with --listen-ng instead of --listen-udp. The UDP protocol of the rtpproxy module should work with rtpengine, but not many people are using it, so it's always possible that some bugs creep in. I'll look into it anyway, but in the long run, it's much preferable to switch to the rtpengine module. Cheers ########################## Hello Richard, thank you very much for your answer. I will try to use rtpengine module. As I can see from logs, kamailio is sending correctly data to rtpengine but rtp engine failed to parse IPv6 address from SDP body. I'm sending flags to rtpengine according to the howto from link I've posted in the original post. This is the part of the config: if (!(isflagset(FLT_NATS) || isbflagset(FLB_NATB) || isbflagset(FLB_V4V6))) return; if(isbflagset(FLB_V4V6)) { if(af==INET6) { rtpproxy_manage("FAEI"); } else { rtpproxy_manage("FAIE"); } } else { if(af==INET6) { rtpproxy_manage("FAEE"); } else { rtpproxy_manage("FAII"); I'm not sure if I need to inform rtpengine that in SDP body will be IPv6 address. Thanks Ismir On Wed, Jul 19, 2017 at 2:31 PM, Ismir Saljic <isaljic(a)gmail.com> wrote: > Hello, > > I've issue with bridging media between IPv4 and IPv6 clients. IPv4-IPv4 > and IPv6-IPv6 calls are working without issues. > I'm using kamailio 4.4.2 and configuration according to: > http://kb.asipto.com/kamailio:kamailio-mixed-ipv4-ipv6 > > SIP signalling is working without issues,but media addresses in SDP are > not rewritten correctly. > > The server is on amazon AWS and both kamailio and RTPengine are on the > same server. > RTPengine is running using these options: > > /usr/sbin/rtpengine --interface=privateIPv4!publicIPv4 > --interface=GlobalIPv6 > --listen-udp=127.0.0.1:22222 > --tos=184 > --pidfile=/var/run/rtpengine.pid > --log-level=6 > --log-facility=daemon > > > In case of IPv4-IPv6 call, INVITE message contains correct IPv4 address > but 200 OK response to the caller still contains IPv6 address of the callee > in SDP body instead of IPv4 address of the server/RTPengine. > This is the log during generation of the 200 OK response. Seems that > RTPengine failed to parse IPv4 address from SDP body. > > Jul 19 08:02:42 /usr/local/sbin/kamailio[1691]: DEBUG: <core> > [parser/msg_parser.c:618]: parse_msg(): SIP Reply (status): > Jul 19 08:02:42 /usr/local/sbin/kamailio[1691]: DEBUG: <core> > [parser/msg_parser.c:620]: parse_msg(): version: <SIP/2.0> > Jul 19 08:02:42 /usr/local/sbin/kamailio[1691]: DEBUG: <core> > [parser/msg_parser.c:622]: parse_msg(): status: <200> > Jul 19 08:02:42 /usr/local/sbin/kamailio[1691]: DEBUG: <core> > [parser/msg_parser.c:624]: parse_msg(): reason: <OK> > Jul 19 08:02:42 /usr/local/sbin/kamailio[1691]: DEBUG: <core> > [parser/parse_via.c:1254]: parse_via_param(): Found param type 232, > <branch> = <z9hG4bK5afe.c59aef39af345458e17940722ba0c70b.0>; state=6 > Jul 19 08:02:42 /usr/local/sbin/kamailio[1691]: DEBUG: <core> > [parser/parse_via.c:1254]: parse_via_param(): Found param type 234, > <received> = <Server's GlobalIPv6>; state=6 > Jul 19 08:02:42 /usr/local/sbin/kamailio[1691]: DEBUG: <core> > [parser/parse_via.c:1254]: parse_via_param(): Found param type 236, <i> = > <8>; state=16 > Jul 19 08:02:42 /usr/local/sbin/kamailio[1691]: DEBUG: <core> > [parser/parse_via.c:2642]: parse_via(): end of header reached, state=5 > Jul 19 08:02:42 /usr/local/sbin/kamailio[1691]: DEBUG: <core> > [parser/msg_parser.c:496]: parse_headers(): parse_headers: Via found, > flags=2 > Jul 19 08:02:42 /usr/local/sbin/kamailio[1691]: DEBUG: <core> > [parser/msg_parser.c:498]: parse_headers(): parse_headers: this is the > first via > Jul 19 08:02:42 /usr/local/sbin/kamailio[1691]: DEBUG: <core> > [receive.c:178]: receive_msg(): After parse_msg... > Jul 19 08:02:42 /usr/local/sbin/kamailio[1691]: DEBUG: tm > [t_lookup.c:1011]: t_check_msg(): DEBUG: t_check_msg: msg id=143 global > id=142 T start=0xffffffffffffffff > Jul 19 08:02:42 /usr/local/sbin/kamailio[1691]: DEBUG: <core> > [parser/parse_via.c:1254]: parse_via_param(): Found param type 234, > <received> = <178.165.130.177>; state=6 > Jul 19 08:02:42 /usr/local/sbin/kamailio[1691]: DEBUG: <core> > [parser/parse_via.c:1254]: parse_via_param(): Found param type 232, > <branch> = <z9hG4bK.BUIgttWpK>; state=6 > Jul 19 08:02:42 /usr/local/sbin/kamailio[1691]: DEBUG: <core> > [parser/parse_via.c:1254]: parse_via_param(): Found param type 235, <rport> > = <2066>; state=16 > Jul 19 08:02:42 /usr/local/sbin/kamailio[1691]: DEBUG: <core> > [parser/parse_via.c:2642]: parse_via(): end of header reached, state=5 > Jul 19 08:02:42 /usr/local/sbin/kamailio[1691]: DEBUG: <core> > [parser/msg_parser.c:496]: parse_headers(): parse_headers: Via found, > flags=62 > Jul 19 08:02:42 /usr/local/sbin/kamailio[1691]: DEBUG: <core> > [parser/msg_parser.c:509]: parse_headers(): parse_headers: this is the > second via > Jul 19 08:02:42 /usr/local/sbin/kamailio[1691]: DEBUG: <core> > [parser/parse_addr_spec.c:172]: parse_to_param(): DEBUG: add_param: > tag=2996330c > Jul 19 08:02:42 /usr/local/sbin/kamailio[1691]: DEBUG: <core> > [parser/parse_addr_spec.c:894]: parse_addr_spec(): end of header reached, > state=29 > Jul 19 08:02:42 /usr/local/sbin/kamailio[1691]: DEBUG: <core> > [parser/msg_parser.c:173]: get_hdr_field(): DEBUG: get_hdr_field: <To> > [59]; uri=[sip:user@domain.com] > Jul 19 08:02:42 /usr/local/sbin/kamailio[1691]: DEBUG: <core> > [parser/msg_parser.c:175]: get_hdr_field(): DEBUG: to body ["user"< > sip:user@domain.com>] > Jul 19 08:02:42 /usr/local/sbin/kamailio[1691]: DEBUG: <core> > [parser/msg_parser.c:153]: get_hdr_field(): get_hdr_field: cseq <CSeq>: > <21> <INVITE> > Jul 19 08:02:42 /usr/local/sbin/kamailio[1691]: DEBUG: tm > [t_lookup.c:888]: t_reply_matching(): DEBUG: t_reply_matching: hash 61349 > label 0 branch 0 > Jul 19 08:02:42 /usr/local/sbin/kamailio[1691]: DEBUG: tm > [t_lookup.c:943]: t_reply_matching(): DEBUG: t_reply_matching: reply > matched (T=0x7f7f95c19a10)! > Jul 19 08:02:42 /usr/local/sbin/kamailio[1691]: DEBUG: tm > [t_hooks.c:266]: run_trans_callbacks_internal(): DBG: > trans=0x7f7f95c19a10, callback type 2, id 0 entered > Jul 19 08:02:42 /usr/local/sbin/kamailio[1691]: DEBUG: acc > [acc_logic.c:644]: tmcb_func(): acc callback called for t(0x7f7f95c19a10) > event type 2, reply code 200 > Jul 19 08:02:42 /usr/local/sbin/kamailio[1691]: DEBUG: tm > [t_lookup.c:1080]: t_check_msg(): DEBUG: t_check_msg: msg id=143 global > id=143 T end=0x7f7f95c19a10 > Jul 19 08:02:42 /usr/local/sbin/kamailio[1691]: DEBUG: tm > [t_reply.c:2160]: reply_received(): DEBUG: reply_received: org. status > uas=180, uac[0]=180 local=0 is_invite=1) > Jul 19 08:02:42 /usr/local/sbin/kamailio[1691]: DEBUG: <script>: > incoming reply > Jul 19 08:02:42 /usr/local/sbin/kamailio[1691]: DEBUG: <script>: BMX: > FAIE > Jul 19 08:02:42 /usr/local/sbin/kamailio[1691]: DEBUG: <core> > [parser/msg_parser.c:187]: get_hdr_field(): DEBUG: get_hdr_body : > content_length=559 > Jul 19 08:02:42 /usr/local/sbin/kamailio[1691]: DEBUG: <core> > [parser/msg_parser.c:89]: get_hdr_field(): found end of header > Jul 19 08:02:42 /usr/local/sbin/kamailio[1691]: DEBUG: <core> > [parser/sdp/sdp_helpr_funcs.c:504]: extract_mediaip(): located IP address > [IPv6 of the callee] in `o=' field > Jul 19 08:02:42 /usr/local/sbin/kamailio[1691]: DEBUG: <core> > [parser/sdp/sdp_helpr_funcs.c:504]: extract_mediaip(): located IP address > [IPv6 of the callee] in `c=' field > Jul 19 08:02:42 /usr/local/sbin/kamailio[1691]: DEBUG: <core> > [parser/sdp/sdp.c:574]: parse_sdp_session(): ignoring unknown type in a= > line: `a=rtcp-fb:* nack#015#012a=rtcp-fb:* nack pli#015#012' > Jul 19 08:02:42 /usr/local/sbin/kamailio[1691]: DEBUG: <core> > [parser/sdp/sdp.c:574]: parse_sdp_session(): ignoring unknown type in a= > line: `a=rtcp-fb:* nack pli#015#012' > Jul 19 08:02:42 /usr/local/sbin/kamailio[1691]: DEBUG: rtpproxy > [rtpproxy_funcs.c:148]: check_content_type(): type <application/sdp> found > valid > Jul 19 08:02:42 /usr/local/sbin/kamailio[1691]: DEBUG: <core> > [parser/parse_addr_spec.c:172]: parse_to_param(): DEBUG: add_param: > tag=aNfQNJz3e > Jul 19 08:02:42 /usr/local/sbin/kamailio[1691]: DEBUG: <core> > [parser/parse_addr_spec.c:894]: parse_addr_spec(): end of header reached, > state=29 > Jul 19 08:02:42 rtpengine[24330]: Got valid command from udp: > 127.0.0.1:28152: 1691_12 LAEI6 dcMDMrNRhw IPv6 of the callee 58100 > aNfQNJz3e;1 2996330c;1 > Jul 19 08:02:42 rtpengine[24330]: [dcMDMrNRhw] Failed to parse a media > stream: /IPv6 of the callee:58100 > Jul 19 08:02:42 /usr/local/sbin/kamailio[1691]: DEBUG: rtpproxy > [rtpproxy.c:2712]: force_rtp_proxy(): proxy reply: E8 > Jul 19 08:02:42 /usr/local/sbin/kamailio[1691]: ERROR: rtpproxy > [rtpproxy.c:2735]: force_rtp_proxy(): incorrect port 0 in reply from rtp > proxy > Jul 19 08:02:42 /usr/local/sbin/kamailio[1691]: DEBUG: tm > [t_reply.c:1233]: t_should_relay_response(): ->>>>>>>>> T_code=180, > new_code=200 > Jul 19 08:02:42 /usr/local/sbin/kamailio[1691]: DEBUG: tm > [t_reply.c:1751]: relay_reply(): DEBUG: relay_reply: branch=0, save=0, > relay=0 icode=0 > Jul 19 08:02:42 /usr/local/sbin/kamailio[1691]: DEBUG: <core> > [msg_translator.c:2260]: generate_res_buf_from_sip_res(): old size: 1467, > new size: 1319 > Jul 19 08:02:42 /usr/local/sbin/kamailio[1691]: DEBUG: <core> > [msg_translator.c:2278]: generate_res_buf_from_sip_res(): copied size: > orig:164, new: 16, rest: 1303 > msg=#012SIP/2.0 200 OK#015#012 > Via: SIP/2.0/TCP 10.152.108.46:56401;received=X.X.X.X; > branch=z9hG4bK.BUIgttWpK;rport=2066 > Record-Route: <sip:[Server's IPv6];transport=tcp;r2=on;lr;nat=v46> > Record-Route: <sip:X.X.X.X;transport=tcp;r2=on;lr;nat=v46> > Contact: <sip:user@[IPv6 of the callee]:59335;rinstance=836aa3 > 6a01097072;transport=tcp> > To: "user"<sip:user@domain.com>;tag=2996330c > From: "caller" <sip:caller@domain.com>;tag=aNfQNJz3e > Call-ID: dcMDMrNRhw > CSeq: 21 INVITE > Allow: SUBSCRIBE, NOTIFY, INVITE, ACK, CANCEL, BYE, REFER, INFO, OPTIONS, > MESSAGE > Content-Type: application/sdp > Supported: replaces > User-Agent: Bria 5 release 5.0.0 stamp 85993 > Content-Length: 559 > > v=0 > o=- 241380314 3 IN IP6 IPv6 of the callee(should be IPv4 address of the > server) > s=Bria 5 release 5.0.0 stamp 85993 > c=IN IP6 IPv6 of the callee (should be IPv4 address of the server) > > > > The same situation is in case of IPv6-IPv4 call. > This is the part of the log in case of IPV6-IPv4 call when kamailio is > creating INVITE to the IPv4 callee: > > Jul 19 08:04:52 /usr/local/sbin/kamailio[1691]: DEBUG: <script>: BMX: > FAIE > Jul 19 08:04:52 /usr/local/sbin/kamailio[1691]: DEBUG: <core> > [parser/sdp/sdp_helpr_funcs.c:504]: extract_mediaip(): located IP address > [IPv6 Address] in `o=' field > Jul 19 08:04:52 /usr/local/sbin/kamailio[1691]: DEBUG: <core> > [parser/sdp/sdp_helpr_funcs.c:504]: extract_mediaip(): located IP address > [IPv6 Address] in `c=' field > Jul 19 08:04:52 /usr/local/sbin/kamailio[1691]: DEBUG: rtpproxy > [rtpproxy_funcs.c:148]: check_content_type(): type <application/sdp> found > valid > Jul 19 08:04:52 rtpengine[24330]: Got valid command from udp: > 127.0.0.1:28152: 1691_13 UAEI6 85993YWVkNmQ4YTFmN2JkZWQ4NjIzMGYwMDBlM2RlOGY0ZDQ > 2a03:f81:abcd:172:16:20:119:2 50168 1430094e;1 > Jul 19 08:04:52 rtpengine[24330]: [85993YWVkNmQ4YTFmN2JkZWQ4NjIzMGYwMDBlM2RlOGY0ZDQ] > Creating new call > Jul 19 08:04:52 rtpengine[24330]: [85993YWVkNmQ4YTFmN2JkZWQ4NjIzMGYwMDBlM2RlOGY0ZDQ] > Failed to parse a media stream: /IPv6:50168 > Jul 19 08:04:52 /usr/local/sbin/kamailio[1691]: DEBUG: rtpproxy > [rtpproxy.c:2712]: force_rtp_proxy(): proxy reply: E8 > Jul 19 08:04:52 /usr/local/sbin/kamailio[1691]: ERROR: rtpproxy > [rtpproxy.c:2735]: force_rtp_proxy(): incorrect port 0 in reply from rtp > proxy > Jul 19 08:04:52 /usr/local/sbin/kamailio[1691]: DEBUG: siputils > [checks.c:97]: has_totag(): no totag > > > Any help would be very appreciated! > > Thank you > Kind regards >

2 2

kamailio 5.0 with asterisks
by Aidar Kamalov 20 Jul '17

20 Jul '17

Hello! I'm new with kamailio, so may be don't understand some basic. I'm tryin to load balance asterisk servers with kamailio and dispatcher module. My ip phones registered at kamailio, for example: [root@sipchel ~]# kamctl ul show 101 { "jsonrpc": "2.0", "result": { "AoR": "101", "Contacts": [{ "Contact": { "Address": "sip:101@192.168.2.62;line=4733c4bfa459eea", "Expires": 2953, "Q": -1, "Call-ID": "1361221648", "CSeq": 136, "User-Agent": "Linphone/3.6.1 (eXosip2/3.6.0)", "Received": "[not set]", "Path": "[not set]", "State": "CS_SYNC", "Flags": 0, "CFlags": 0, "Socket": "udp:192.168.10.54:5060", "Methods": -1, "Ruid": "uloc-596f5abc-2ce5-2", "Instance": "[not set]", "Reg-Id": 0, "Last-Keepalive": 1500530337, "Last-Modified": 1500530337 } }] }, "id": 15024 } I have realtime asterisk server. [root@sipchel ~]# kamctl dispatcher dump { "jsonrpc": "2.0", "result": { "NRSETS": 1, "RECORDS": [{ "SET": { "ID": 1, "TARGETS": [{ "DEST": { "URI": "sip:192.168.4.16", "FLAGS": "IX", "PRIORITY": 0 } }, { "DEST": { "URI": "sip:192.168.10.47", "FLAGS": "AX", "PRIORITY": 0 } }] } }] }, "id": 15087 } So I want if 101 call to 102 it will process by asterisk(for call recording and other features). Now if I call from 101 to 102 kamailio will forward to asterisk and asterisk dialplan cannot find that extesion(as expected, because it is not registed on asterisk) [kamailio] exten => _1XX,1,Dial(SIP/${EXTEN}) exten => _1XX,n,Hangup If I change dialplan to Dial(SIP/KAMAILIO/${EXTEN}) call wil return to kamailio, but kamailio send it back to asterisk... I hope I explained correctly, my English is terrible. Is my screnario proper? How this usually done? Should I forward sip registrations to asterisks? My kamailio config # dispatcher params modparam("dispatcher", "db_url", "mysql://kamailio:kamailiorw@localhost /kamailio") modparam("dispatcher", "ds_ping_interval", 30) modparam("dispatcher", "table_name", "dispatcher") modparam("dispatcher", "flags", 2) modparam("dispatcher", "dst_avp", "$avp(AVP_DST)") modparam("dispatcher", "grp_avp", "$avp(AVP_GRP)") modparam("dispatcher", "cnt_avp", "$avp(AVP_CNT)") modparam("auth_db", "db_url", DBASTURL) modparam("auth_db", "calculate_ha1", yes) modparam("auth_db", "user_column", "name") modparam("auth_db", "password_column", "sippasswd") modparam("auth_db", "load_credentials", "") #modparam("auth_db", "version_table", 0) request_route { <------># per request initial checks <------>route(REQINIT); <------># NAT detection <------>route(NATDETECT); <------># CANCEL processing <------>if (is_method("CANCEL")) { <------><------>if (t_check_trans()) { <------><------><------>route(RELAY); <------><------>} <------><------>exit; <------>} <------># handle retransmissions <------>if (!is_method("ACK")) { <------><------>if(t_precheck_trans()) { <------><------><------>t_check_trans(); <------><------><------>exit; <------><------>} <------><------>t_check_trans(); <------>} <------># handle requests within SIP dialogs <------>route(WITHINDLG); <------>### only initial requests (no To tag) <------># authentication <------>route(AUTH); <------># record routing for dialog forming requests (in case they are routed) <------># - remove preloaded route headers <------>remove_hf("Route"); <------>if (is_method("INVITE|SUBSCRIBE")) { <------><------>record_route(); <------>} <------># account only INVITEs <------>if (is_method("INVITE")) { <------><------>setflag(FLT_ACC); # do accounting <------>} <------># dispatch requests to foreign domains <------>route(SIPOUT); ------>### requests for my local domains <------># handle presence related requests <------>route(PRESENCE); <------># handle registrations <------>route(REGISTRAR); <------>if ($rU==$null) { <------><------># request with no Username in RURI <------><------>sl_send_reply("484","Address Incomplete"); <------><------>exit; <------>} <------># dispatch destinations to PSTN <------>route(PSTN); <------># user location service <------>route(LOCATION); } # User location service route[LOCATION] { #!ifdef WITH_SPEEDDIAL <------># search for short dialing - 2-digit extension <------>if($rU=~"^[0-9][0-9]$") { <------><------>if(sd_lookup("speed_dial")) { <------><------><------>route(SIPOUT); <------><------>} <------>} #!endif #!ifdef WITH_ALIASDB <------># search in DB-based aliases <------>if(alias_db_lookup("dbaliases")) { <------><------>route(SIPOUT); <------>} #!endif <------>$avp(oexten) = $rU; <------>if (!lookup("location")) { <------><------>$var(rc) = $rc; <------><------>route(TOVOICEMAIL); <------><------>t_newtran(); <------><------>switch ($var(rc)) { <------><------><------>case -1: <------><------><------>case -3: <------><------><------><------>send_reply("404", "Not Found"); <------><------><------><------>exit; <------><------><------>case -2: <------><------><------><------>send_reply("405", "Method Not Allowed"); <------><------><------><------>exit; <------><------>} <------>} <------># when routing via usrloc, log the missed calls also <------>if (is_method("INVITE")) { <------><------>setflag(FLT_ACCMISSED); <------>} route(DISPATCH); <------>route(RELAY); <------>exit; } # Dispatch requests route[DISPATCH] { <------># round robin dispatching on gateways group '1' <------>if(!ds_select_dst("1", "4")) <------>{ <------> xlog("aaaa--- SCRIPT: going to <$ru> via <$du>\n"); <------> send_reply("404", "No destination"); <------> exit; <------>} <------>xlog("--- SCRIPT: going to <$ru> via <$du>\n"); <------>t_on_failure("RTF_DISPATCH"); <------>return; } -- Aydar A. Kamalov

3 2

Integration of Google Speech API V2
by Rahul MathuR 19 Jul '17

19 Jul '17

Hi, I'm trying to integrate Google cloud speech recognition v2 in it. I can get the audio recorded, have created Service key and API key but whenever I try to access it, I just get 403 access denied. I am at my wits end here. Has anybody tried it ? were you successful ? Could you please guide me how to do it ? I'll be grateful to you if this works ! -- Warm Regds. MathuRahul

2 1

Problem with IPv4-IPv6 media bridging using RTPengine
by Ismir Saljic 19 Jul '17

19 Jul '17

Hello, I've issue with bridging media between IPv4 and IPv6 clients. IPv4-IPv4 and IPv6-IPv6 calls are working without issues. I'm using kamailio 4.4.2 and configuration according to: http://kb.asipto.com/kamailio:kamailio-mixed-ipv4-ipv6 SIP signalling is working without issues,but media addresses in SDP are not rewritten correctly. The server is on amazon AWS and both kamailio and RTPengine are on the same server. RTPengine is running using these options: /usr/sbin/rtpengine --interface=privateIPv4!publicIPv4 --interface=GlobalIPv6 --listen-udp=127.0.0.1:22222 --tos=184 --pidfile=/var/run/rtpengine.pid --log-level=6 --log-facility=daemon In case of IPv4-IPv6 call, INVITE message contains correct IPv4 address but 200 OK response to the caller still contains IPv6 address of the callee in SDP body instead of IPv4 address of the server/RTPengine. This is the log during generation of the 200 OK response. Seems that RTPengine failed to parse IPv4 address from SDP body. Jul 19 08:02:42 /usr/local/sbin/kamailio[1691]: DEBUG: <core> [parser/msg_parser.c:618]: parse_msg(): SIP Reply (status): Jul 19 08:02:42 /usr/local/sbin/kamailio[1691]: DEBUG: <core> [parser/msg_parser.c:620]: parse_msg(): version: <SIP/2.0> Jul 19 08:02:42 /usr/local/sbin/kamailio[1691]: DEBUG: <core> [parser/msg_parser.c:622]: parse_msg(): status: <200> Jul 19 08:02:42 /usr/local/sbin/kamailio[1691]: DEBUG: <core> [parser/msg_parser.c:624]: parse_msg(): reason: <OK> Jul 19 08:02:42 /usr/local/sbin/kamailio[1691]: DEBUG: <core> [parser/parse_via.c:1254]: parse_via_param(): Found param type 232, <branch> = <z9hG4bK5afe.c59aef39af345458e17940722ba0c70b.0>; state=6 Jul 19 08:02:42 /usr/local/sbin/kamailio[1691]: DEBUG: <core> [parser/parse_via.c:1254]: parse_via_param(): Found param type 234, <received> = <Server's GlobalIPv6>; state=6 Jul 19 08:02:42 /usr/local/sbin/kamailio[1691]: DEBUG: <core> [parser/parse_via.c:1254]: parse_via_param(): Found param type 236, <i> = <8>; state=16 Jul 19 08:02:42 /usr/local/sbin/kamailio[1691]: DEBUG: <core> [parser/parse_via.c:2642]: parse_via(): end of header reached, state=5 Jul 19 08:02:42 /usr/local/sbin/kamailio[1691]: DEBUG: <core> [parser/msg_parser.c:496]: parse_headers(): parse_headers: Via found, flags=2 Jul 19 08:02:42 /usr/local/sbin/kamailio[1691]: DEBUG: <core> [parser/msg_parser.c:498]: parse_headers(): parse_headers: this is the first via Jul 19 08:02:42 /usr/local/sbin/kamailio[1691]: DEBUG: <core> [receive.c:178]: receive_msg(): After parse_msg... Jul 19 08:02:42 /usr/local/sbin/kamailio[1691]: DEBUG: tm [t_lookup.c:1011]: t_check_msg(): DEBUG: t_check_msg: msg id=143 global id=142 T start=0xffffffffffffffff Jul 19 08:02:42 /usr/local/sbin/kamailio[1691]: DEBUG: <core> [parser/parse_via.c:1254]: parse_via_param(): Found param type 234, <received> = <178.165.130.177>; state=6 Jul 19 08:02:42 /usr/local/sbin/kamailio[1691]: DEBUG: <core> [parser/parse_via.c:1254]: parse_via_param(): Found param type 232, <branch> = <z9hG4bK.BUIgttWpK>; state=6 Jul 19 08:02:42 /usr/local/sbin/kamailio[1691]: DEBUG: <core> [parser/parse_via.c:1254]: parse_via_param(): Found param type 235, <rport> = <2066>; state=16 Jul 19 08:02:42 /usr/local/sbin/kamailio[1691]: DEBUG: <core> [parser/parse_via.c:2642]: parse_via(): end of header reached, state=5 Jul 19 08:02:42 /usr/local/sbin/kamailio[1691]: DEBUG: <core> [parser/msg_parser.c:496]: parse_headers(): parse_headers: Via found, flags=62 Jul 19 08:02:42 /usr/local/sbin/kamailio[1691]: DEBUG: <core> [parser/msg_parser.c:509]: parse_headers(): parse_headers: this is the second via Jul 19 08:02:42 /usr/local/sbin/kamailio[1691]: DEBUG: <core> [parser/parse_addr_spec.c:172]: parse_to_param(): DEBUG: add_param: tag=2996330c Jul 19 08:02:42 /usr/local/sbin/kamailio[1691]: DEBUG: <core> [parser/parse_addr_spec.c:894]: parse_addr_spec(): end of header reached, state=29 Jul 19 08:02:42 /usr/local/sbin/kamailio[1691]: DEBUG: <core> [parser/msg_parser.c:173]: get_hdr_field(): DEBUG: get_hdr_field: <To> [59]; uri=[sip:user@domain.com] Jul 19 08:02:42 /usr/local/sbin/kamailio[1691]: DEBUG: <core> [parser/msg_parser.c:175]: get_hdr_field(): DEBUG: to body ["user"< sip:user@domain.com>] Jul 19 08:02:42 /usr/local/sbin/kamailio[1691]: DEBUG: <core> [parser/msg_parser.c:153]: get_hdr_field(): get_hdr_field: cseq <CSeq>: <21> <INVITE> Jul 19 08:02:42 /usr/local/sbin/kamailio[1691]: DEBUG: tm [t_lookup.c:888]: t_reply_matching(): DEBUG: t_reply_matching: hash 61349 label 0 branch 0 Jul 19 08:02:42 /usr/local/sbin/kamailio[1691]: DEBUG: tm [t_lookup.c:943]: t_reply_matching(): DEBUG: t_reply_matching: reply matched (T=0x7f7f95c19a10)! Jul 19 08:02:42 /usr/local/sbin/kamailio[1691]: DEBUG: tm [t_hooks.c:266]: run_trans_callbacks_internal(): DBG: trans=0x7f7f95c19a10, callback type 2, id 0 entered Jul 19 08:02:42 /usr/local/sbin/kamailio[1691]: DEBUG: acc [acc_logic.c:644]: tmcb_func(): acc callback called for t(0x7f7f95c19a10) event type 2, reply code 200 Jul 19 08:02:42 /usr/local/sbin/kamailio[1691]: DEBUG: tm [t_lookup.c:1080]: t_check_msg(): DEBUG: t_check_msg: msg id=143 global id=143 T end=0x7f7f95c19a10 Jul 19 08:02:42 /usr/local/sbin/kamailio[1691]: DEBUG: tm [t_reply.c:2160]: reply_received(): DEBUG: reply_received: org. status uas=180, uac[0]=180 local=0 is_invite=1) Jul 19 08:02:42 /usr/local/sbin/kamailio[1691]: DEBUG: <script>: incoming reply Jul 19 08:02:42 /usr/local/sbin/kamailio[1691]: DEBUG: <script>: BMX: FAIE Jul 19 08:02:42 /usr/local/sbin/kamailio[1691]: DEBUG: <core> [parser/msg_parser.c:187]: get_hdr_field(): DEBUG: get_hdr_body : content_length=559 Jul 19 08:02:42 /usr/local/sbin/kamailio[1691]: DEBUG: <core> [parser/msg_parser.c:89]: get_hdr_field(): found end of header Jul 19 08:02:42 /usr/local/sbin/kamailio[1691]: DEBUG: <core> [parser/sdp/sdp_helpr_funcs.c:504]: extract_mediaip(): located IP address [IPv6 of the callee] in `o=' field Jul 19 08:02:42 /usr/local/sbin/kamailio[1691]: DEBUG: <core> [parser/sdp/sdp_helpr_funcs.c:504]: extract_mediaip(): located IP address [IPv6 of the callee] in `c=' field Jul 19 08:02:42 /usr/local/sbin/kamailio[1691]: DEBUG: <core> [parser/sdp/sdp.c:574]: parse_sdp_session(): ignoring unknown type in a= line: `a=rtcp-fb:* nack#015#012a=rtcp-fb:* nack pli#015#012' Jul 19 08:02:42 /usr/local/sbin/kamailio[1691]: DEBUG: <core> [parser/sdp/sdp.c:574]: parse_sdp_session(): ignoring unknown type in a= line: `a=rtcp-fb:* nack pli#015#012' Jul 19 08:02:42 /usr/local/sbin/kamailio[1691]: DEBUG: rtpproxy [rtpproxy_funcs.c:148]: check_content_type(): type <application/sdp> found valid Jul 19 08:02:42 /usr/local/sbin/kamailio[1691]: DEBUG: <core> [parser/parse_addr_spec.c:172]: parse_to_param(): DEBUG: add_param: tag=aNfQNJz3e Jul 19 08:02:42 /usr/local/sbin/kamailio[1691]: DEBUG: <core> [parser/parse_addr_spec.c:894]: parse_addr_spec(): end of header reached, state=29 Jul 19 08:02:42 rtpengine[24330]: Got valid command from udp: 127.0.0.1:28152: 1691_12 LAEI6 dcMDMrNRhw IPv6 of the callee 58100 aNfQNJz3e;1 2996330c;1 Jul 19 08:02:42 rtpengine[24330]: [dcMDMrNRhw] Failed to parse a media stream: /IPv6 of the callee:58100 Jul 19 08:02:42 /usr/local/sbin/kamailio[1691]: DEBUG: rtpproxy [rtpproxy.c:2712]: force_rtp_proxy(): proxy reply: E8 Jul 19 08:02:42 /usr/local/sbin/kamailio[1691]: ERROR: rtpproxy [rtpproxy.c:2735]: force_rtp_proxy(): incorrect port 0 in reply from rtp proxy Jul 19 08:02:42 /usr/local/sbin/kamailio[1691]: DEBUG: tm [t_reply.c:1233]: t_should_relay_response(): ->>>>>>>>> T_code=180, new_code=200 Jul 19 08:02:42 /usr/local/sbin/kamailio[1691]: DEBUG: tm [t_reply.c:1751]: relay_reply(): DEBUG: relay_reply: branch=0, save=0, relay=0 icode=0 Jul 19 08:02:42 /usr/local/sbin/kamailio[1691]: DEBUG: <core> [msg_translator.c:2260]: generate_res_buf_from_sip_res(): old size: 1467, new size: 1319 Jul 19 08:02:42 /usr/local/sbin/kamailio[1691]: DEBUG: <core> [msg_translator.c:2278]: generate_res_buf_from_sip_res(): copied size: orig:164, new: 16, rest: 1303 msg=#012SIP/2.0 200 OK#015#012 Via: SIP/2.0/TCP 10.152.108.46:56401;received=X.X.X.X; branch=z9hG4bK.BUIgttWpK;rport=2066 Record-Route: <sip:[Server's IPv6];transport=tcp;r2=on;lr;nat=v46> Record-Route: <sip:X.X.X.X;transport=tcp;r2=on;lr;nat=v46> Contact: <sip:user@[IPv6 of the callee]:59335;rinstance= 836aa36a01097072;transport=tcp> To: "user"<sip:user@domain.com>;tag=2996330c From: "caller" <sip:caller@domain.com>;tag=aNfQNJz3e Call-ID: dcMDMrNRhw CSeq: 21 INVITE Allow: SUBSCRIBE, NOTIFY, INVITE, ACK, CANCEL, BYE, REFER, INFO, OPTIONS, MESSAGE Content-Type: application/sdp Supported: replaces User-Agent: Bria 5 release 5.0.0 stamp 85993 Content-Length: 559 v=0 o=- 241380314 3 IN IP6 IPv6 of the callee(should be IPv4 address of the server) s=Bria 5 release 5.0.0 stamp 85993 c=IN IP6 IPv6 of the callee (should be IPv4 address of the server) The same situation is in case of IPv6-IPv4 call. This is the part of the log in case of IPV6-IPv4 call when kamailio is creating INVITE to the IPv4 callee: Jul 19 08:04:52 /usr/local/sbin/kamailio[1691]: DEBUG: <script>: BMX: FAIE Jul 19 08:04:52 /usr/local/sbin/kamailio[1691]: DEBUG: <core> [parser/sdp/sdp_helpr_funcs.c:504]: extract_mediaip(): located IP address [IPv6 Address] in `o=' field Jul 19 08:04:52 /usr/local/sbin/kamailio[1691]: DEBUG: <core> [parser/sdp/sdp_helpr_funcs.c:504]: extract_mediaip(): located IP address [IPv6 Address] in `c=' field Jul 19 08:04:52 /usr/local/sbin/kamailio[1691]: DEBUG: rtpproxy [rtpproxy_funcs.c:148]: check_content_type(): type <application/sdp> found valid Jul 19 08:04:52 rtpengine[24330]: Got valid command from udp: 127.0.0.1:28152: 1691_13 UAEI6 85993YWVkNmQ4YTFmN2JkZWQ4NjIzMGYwMDBlM2RlOGY0ZDQ 2a03:f81:abcd:172:16:20:119:2 50168 1430094e;1 Jul 19 08:04:52 rtpengine[24330]: [85993YWVkNmQ4YTFmN2JkZWQ4NjIzMGYwMDBlM2RlOGY0ZDQ] Creating new call Jul 19 08:04:52 rtpengine[24330]: [85993YWVkNmQ4YTFmN2JkZWQ4NjIzMGYwMDBlM2RlOGY0ZDQ] Failed to parse a media stream: /IPv6:50168 Jul 19 08:04:52 /usr/local/sbin/kamailio[1691]: DEBUG: rtpproxy [rtpproxy.c:2712]: force_rtp_proxy(): proxy reply: E8 Jul 19 08:04:52 /usr/local/sbin/kamailio[1691]: ERROR: rtpproxy [rtpproxy.c:2735]: force_rtp_proxy(): incorrect port 0 in reply from rtp proxy Jul 19 08:04:52 /usr/local/sbin/kamailio[1691]: DEBUG: siputils [checks.c:97]: has_totag(): no totag Any help would be very appreciated! Thank you Kind regards

2 1

dns failover and branches
by Juha Heinanen 19 Jul '17

19 Jul '17

If Request-URI hostpart is a domain name with more than one SRV record, it appears that each SRV destination creates its own Kamailio branch. If branch route is set before t_relay(), it is executed only on the first SRV destination. If the first SRV destination fails, Kamailio tries automatically the second one, but any branch flags set in the branch route are lost. What is the simplest way to make Kamailio preserve the stuff set in the branch route for all SRV destinations? -- Juha

3 13

about rtpengine-[offer-answer] via-branch flag
by Juha Heinanen 18 Jul '17

18 Jul '17

rtpengine-offer function documentation tells this about via-branch flag: via-branch=... - Include the “branch” value of one of the “Via” headers in the request to the RTP proxy. Possible values are: “1” - use the first “Via” header; “2” - use the second “Via” header; “auto” - use the first “Via” header if this is a request, or the second one if this is a reply; “extra” - don't take the value from a header, but instead use the value of the “extra_id_pv” variable. This can be used to create one media session per branch on the RTP proxy. When sending a subsequent “delete” command to the RTP proxy, you can then stop just the session for a specific branch when passing the flag '1' or '2' in the “rtpengine_delete”, or stop all sessions for a call when not passing one of those two flags there. This is especially useful if you have serially forked call scenarios where the RTP proxy gets an “offer” command for a new branch, and then a “delete” command for the previous branch, which would otherwise delete the full call, breaking the subsequent “answer” for the new branch. Is the note about "serial forking" correct or should it be about "parallel forking" instead? In case of serial forking, it would not matter if the whole call is deleted, because a new offer would be issued for the next branch. Or perhaps I just don't understand the meaning of the note? -- Juha

2 2

Info: business directory
by Daniel-Constantin Mierla 18 Jul '17

18 Jul '17

Hello, for those new in the community as well as a reminder for the others: if you offer Kamailio-related services or products, you can get listed at: - https://www.kamailio.org/w/business-directory/ Besides that, also in the case if you just use Kamailio for RTC/VoIP services, you can add yourself in Used By directory: - https://www.kamailio.org/w/used-by/ The website has very good traffic and can increase your visibility in the market. Cheers, Daniel -- Daniel-Constantin Mierla www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - www.asipto.com Kamailio World Conference - www.kamailioworld.com

1 0

rtpengine: Failed to open UDP control connection port
by David Cunningham 17 Jul '17

17 Jul '17

Hello, We're using Kamailio 4.2.1 with rtpengine 5.1.2.1 on Ubuntu 16.04. When running rtpengine we get this error: [1500263405.711288] ERR: FAILED TO CREATE KERNEL TABLE 0 (File exists), KERNEL FORWARDING DISABLED [1500263405.712367] CRIT: Fatal error: Failed to open UDP control connection port The first line I think is not important, but the second appears to be. It's being run as root with these options: /usr/sbin/rtpengine --interface=xx.xx.xx.xx --listen-ng=7724 --timeout=60 --silent-timeout=3600 --pidfile=/var/run/rtpengine.pid --port-min=45000 --port-max=50000 --table=0 Running "netstat -lnp | grep 7724" does not report anything listening on port 7724 already. Has anyone any ideas? Thanks in advance. -- David Cunningham, Voisonics Limited http://voisonics.com/ USA: +1 213 221 1092 Australia: +61 (0) 2 8063 9019

3 4

Kamilio new user - help get going
by Kenneth Knudsen 17 Jul '17

17 Jul '17

Hi I have been watching numerous videos on youtube in search of how to configure Kamilio ! I know we I need the Sip Server, but don't know how to get it configured. The installation is obvious with the commands as a root user. Brief description of the project: Have quite a few customers we want to move from PSTN (AT&T primarily) to a Voip/Sip solution. So instead of setting up 1 FreePBX and 1 public ip, we would rather use 1 public IP to many FreePBX servers on the backend. I haven't been able to find one video on how to configure this SIP server, and was hoping somebody here might have some clues to lead me in the right direction. I found one company that would help us, but they said at least 20 hours just to configure the first customer/freePBX installation. If we could get help setting up the first we should be able to figure out the ones to come later. Any help would be appreciated... We know the product is awesome, we have the keys but don't know how to run the thing or even get it started !! Kind regards, Kenneth Knudsen

6 11

Clarification on redis_cmd in ndb_redis module
by vivek＠advaitamtech.com 17 Jul '17

17 Jul '17

Hi, Am using redis_cmd in kamailio.cfg to perform redis operations. I would like to know if redis_cmd() creates new connection everytime I call it in kamailio.cfg?. Since am using redis_cmd() multiple times to access few data's. Also, is calling redis_free() necessary to avoid connections being open? I am facing an error of number of open files exceeded. This error is caused by ndb_redis module. But cannot confirm due to which part of redis. Thanks, Vivek

2 1

Need help to send INVITE to multiple client based on REGISTRATION status
by amit Kumar 15 Jul '17

15 Jul '17

Hi All, Following are the requirement which we want to achieve through Kamailio. Our "voip client" will not be register in advance.When Kamailio get INIVITE request for particular "voip client"(multiple client), we send push notification to make "voip client"(multiple client) alive and get it register for to Kamailio. Meanwhile INIVITE request will wait. the moment, "voip client" get register, Kamailio will send INIVITE to all the client despite their *registration time/status*.for example - if first client get register with in T+1 second,that should also get INVITE and another client get register in T+2 second that should also get INVITE. Could you please help me if this is possible in Kamailio. I have done some code walk through and have the basic idea to save the INVITE transaction(similar to suspend and continue), later point of time when i get the register request, I will use functionality like t_lookup_request and and lookup(which in turn append_branch) and call the t_realy () again. Please let me know if this is correct approach or if there is some other way to solve this. Thanks, Amit

2 1

Database connection handles vs. processes
by Alex Balashov 13 Jul '17

13 Jul '17

Hi, By way of illustration, I have one server with children=8, a single UDP listener, and 23 processes total: -- 21117 attendant 21118 udp receiver child=0 sock=xxx.xxx.xxx.xxx:5060 21119 udp receiver child=1 sock=xxx.xxx.xxx.xxx:5060 21120 udp receiver child=2 sock=xxx.xxx.xxx.xxx:5060 21121 udp receiver child=3 sock=xxx.xxx.xxx.xxx:5060 21122 udp receiver child=4 sock=xxx.xxx.xxx.xxx:5060 21123 udp receiver child=5 sock=xxx.xxx.xxx.xxx:5060 21124 udp receiver child=6 sock=xxx.xxx.xxx.xxx:5060 21125 udp receiver child=7 sock=xxx.xxx.xxx.xxx:5060 21126 slow timer 21127 timer 21128 MI FIFO 21129 ctl handler 21130 RTIMER USEC EXEC 21131 RTIMER USEC EXEC 21132 RTIMER USEC EXEC 21133 RTIMER USEC EXEC 21134 RTIMER USEC EXEC 21135 RTIMER USEC EXEC 21136 RTIMER USEC EXEC 21137 Dialog KA Timer 21138 Dialog Clean Timer 21139 tcp main process # kamcmd -s /tmp/kamailio_ctl ps | wc -l 23 -- This appears to result in 23 total database connections to the Postgres server: -- # lsof -n | grep -i '^kam' | grep IPv4 | grep TCP | grep -i :postgres | wc -l 23 -- But I have another Kamailio server that has three listeners, two UDP and one TCP, and children=24, i.e. -- children=24 listen=udp:xxx.xxx.xxx.xxx:5060 listen=udp:yyy.yyy.yyy.yyy:5060 listen=tcp:zzz.zzz.zzz.zzz:5060 -- I am given to understand that the total number of worker processes there will be (children_setting * listeners), i.e. 72 in this case, plus some number of rtimer and supervisory processes, as in my case. And true enough: -- # kamcmd -s /tmp/kamailio_ctl ps | wc -l 86 # kamcmd -s /tmp/kamailio_ctl ps | sed 's/65.254.44.195/yyy.yyy.yyy.yyy/g' | sed 's/65.254.44.194/zzz.zzz.zzz.zzz/g' 22065 main process - attendant 22069 udp receiver child=0 sock=zzz.zzz.zzz.zzz:5060 22070 udp receiver child=1 sock=zzz.zzz.zzz.zzz:5060 22071 udp receiver child=2 sock=zzz.zzz.zzz.zzz:5060 22073 udp receiver child=3 sock=zzz.zzz.zzz.zzz:5060 22074 udp receiver child=4 sock=zzz.zzz.zzz.zzz:5060 22076 udp receiver child=5 sock=zzz.zzz.zzz.zzz:5060 22079 udp receiver child=6 sock=zzz.zzz.zzz.zzz:5060 22080 udp receiver child=7 sock=zzz.zzz.zzz.zzz:5060 22082 udp receiver child=8 sock=zzz.zzz.zzz.zzz:5060 22085 udp receiver child=9 sock=zzz.zzz.zzz.zzz:5060 22086 udp receiver child=10 sock=zzz.zzz.zzz.zzz:5060 22089 udp receiver child=11 sock=zzz.zzz.zzz.zzz:5060 22091 udp receiver child=12 sock=zzz.zzz.zzz.zzz:5060 22093 udp receiver child=13 sock=zzz.zzz.zzz.zzz:5060 22095 udp receiver child=14 sock=zzz.zzz.zzz.zzz:5060 22097 udp receiver child=15 sock=zzz.zzz.zzz.zzz:5060 22099 udp receiver child=16 sock=zzz.zzz.zzz.zzz:5060 22100 udp receiver child=17 sock=zzz.zzz.zzz.zzz:5060 22103 udp receiver child=18 sock=zzz.zzz.zzz.zzz:5060 22105 udp receiver child=19 sock=zzz.zzz.zzz.zzz:5060 22107 udp receiver child=20 sock=zzz.zzz.zzz.zzz:5060 22109 udp receiver child=21 sock=zzz.zzz.zzz.zzz:5060 22111 udp receiver child=22 sock=zzz.zzz.zzz.zzz:5060 22113 udp receiver child=23 sock=zzz.zzz.zzz.zzz:5060 22115 udp receiver child=0 sock=yyy.yyy.yyy.yyy:5060 22117 udp receiver child=1 sock=yyy.yyy.yyy.yyy:5060 22119 udp receiver child=2 sock=yyy.yyy.yyy.yyy:5060 22121 udp receiver child=3 sock=yyy.yyy.yyy.yyy:5060 22123 udp receiver child=4 sock=yyy.yyy.yyy.yyy:5060 22125 udp receiver child=5 sock=yyy.yyy.yyy.yyy:5060 22127 udp receiver child=6 sock=yyy.yyy.yyy.yyy:5060 22129 udp receiver child=7 sock=yyy.yyy.yyy.yyy:5060 22131 udp receiver child=8 sock=yyy.yyy.yyy.yyy:5060 22132 udp receiver child=9 sock=yyy.yyy.yyy.yyy:5060 22135 udp receiver child=10 sock=yyy.yyy.yyy.yyy:5060 22137 udp receiver child=11 sock=yyy.yyy.yyy.yyy:5060 22139 udp receiver child=12 sock=yyy.yyy.yyy.yyy:5060 22141 udp receiver child=13 sock=yyy.yyy.yyy.yyy:5060 22143 udp receiver child=14 sock=yyy.yyy.yyy.yyy:5060 22145 udp receiver child=15 sock=yyy.yyy.yyy.yyy:5060 22147 udp receiver child=16 sock=yyy.yyy.yyy.yyy:5060 22149 udp receiver child=17 sock=yyy.yyy.yyy.yyy:5060 22151 udp receiver child=18 sock=yyy.yyy.yyy.yyy:5060 22153 udp receiver child=19 sock=yyy.yyy.yyy.yyy:5060 22155 udp receiver child=20 sock=yyy.yyy.yyy.yyy:5060 22156 udp receiver child=21 sock=yyy.yyy.yyy.yyy:5060 22159 udp receiver child=22 sock=yyy.yyy.yyy.yyy:5060 22161 udp receiver child=23 sock=yyy.yyy.yyy.yyy:5060 22163 slow timer 22165 timer 22167 secondary timer 22168 ctl handler 22169 RTIMER USEC EXEC 22170 RTIMER USEC EXEC 22172 RTIMER USEC EXEC 22173 RTIMER USEC EXEC 22175 Dialog Clean Timer 22176 TIMER NH 22177 TIMER NH 22178 TIMER NH 22179 tcp receiver (generic) child=0 22180 tcp receiver (generic) child=1 22182 tcp receiver (generic) child=2 22184 tcp receiver (generic) child=3 22186 tcp receiver (generic) child=4 22188 tcp receiver (generic) child=5 22190 tcp receiver (generic) child=6 22192 tcp receiver (generic) child=7 22194 tcp receiver (generic) child=8 22196 tcp receiver (generic) child=9 22198 tcp receiver (generic) child=10 22200 tcp receiver (generic) child=11 22202 tcp receiver (generic) child=12 22204 tcp receiver (generic) child=13 22206 tcp receiver (generic) child=14 22208 tcp receiver (generic) child=15 22210 tcp receiver (generic) child=16 22212 tcp receiver (generic) child=17 22214 tcp receiver (generic) child=18 22216 tcp receiver (generic) child=19 22218 tcp receiver (generic) child=20 22220 tcp receiver (generic) child=21 22223 tcp receiver (generic) child=22 22225 tcp receiver (generic) child=23 22227 tcp main process -- But, for some reason, the number of database connections to Postgres seems to be considerably higher than the number of total processes: -- # lsof -n | grep '^kam' | grep TCP | grep IPv4 | grep ':postgres' | wc -l 114 -- This is not due to orphaned/unterminated Kamailio processes. There's only one process lineage: -- |-kamailio(22065)-+-kamailio(22069) | |-kamailio(22070) | |-kamailio(22071) | |-kamailio(22073) | |-kamailio(22074) | |-kamailio(22076) | |-kamailio(22079) | |-kamailio(22080) | |-kamailio(22082) | |-kamailio(22085) | |-kamailio(22086) | |-kamailio(22089) | |-kamailio(22091) | |-kamailio(22093) | |-kamailio(22095) | |-kamailio(22097) | |-kamailio(22099) | |-kamailio(22100) | |-kamailio(22103) | |-kamailio(22105) | |-kamailio(22107) | |-kamailio(22109) | |-kamailio(22111) | |-kamailio(22113) | |-kamailio(22115) | |-kamailio(22117) | |-kamailio(22119) | |-kamailio(22121) | |-kamailio(22123) | |-kamailio(22125) | |-kamailio(22127) | |-kamailio(22129) | |-kamailio(22131) | |-kamailio(22132) | |-kamailio(22135) | |-kamailio(22137) | |-kamailio(22139) | |-kamailio(22141) | |-kamailio(22143) | |-kamailio(22145) | |-kamailio(22147) | |-kamailio(22149) | |-kamailio(22151) | |-kamailio(22153) | |-kamailio(22155) | |-kamailio(22156) | |-kamailio(22159) | |-kamailio(22161) | |-kamailio(22163) | |-kamailio(22165) | |-kamailio(22167) | |-kamailio(22168) | |-kamailio(22169) | |-kamailio(22170) | |-kamailio(22172) | |-kamailio(22173) | |-kamailio(22175) | |-kamailio(22176) | |-kamailio(22177) | |-kamailio(22178) | |-kamailio(22179) | |-kamailio(22180) | |-kamailio(22182) | |-kamailio(22184) | |-kamailio(22186) | |-kamailio(22188) | |-kamailio(22190) | |-kamailio(22192) | |-kamailio(22194) | |-kamailio(22196) | |-kamailio(22198) | |-kamailio(22200) | |-kamailio(22202) | |-kamailio(22204) | |-kamailio(22206) | |-kamailio(22208) | |-kamailio(22210) | |-kamailio(22212) | |-kamailio(22214) | |-kamailio(22216) | |-kamailio(22218) | |-kamailio(22220) | |-kamailio(22223) | |-kamailio(22225) | `-kamailio(22227) -- Yet, for some reason, some of the processes have two established DB connections from different ports: -- kamailio 22220 root 3u IPv4 189895303 0t0 TCP 127.0.0.1:46550->127.0.0.1:postgres (ESTABLISHED) kamailio 22220 root 86u IPv4 189895067 0t0 TCP 127.0.0.1:46458->127.0.0.1:postgres (ESTABLISHED) kamailio 22223 root 3u IPv4 189895315 0t0 TCP 127.0.0.1:46556->127.0.0.1:postgres (ESTABLISHED) kamailio 22223 root 86u IPv4 189895067 0t0 TCP 127.0.0.1:46458->127.0.0.1:postgres (ESTABLISHED) kamailio 22225 root 3u IPv4 189895321 0t0 TCP 127.0.0.1:46560->127.0.0.1:postgres (ESTABLISHED) kamailio 22225 root 86u IPv4 189895067 0t0 TCP 127.0.0.1:46458->127.0.0.1:postgres (ESTABLISHED) kamailio 22227 root 86u IPv4 189895067 0t0 TCP 127.0.0.1:46458->127.0.0.1:postgres (ESTABLISHED) -- ... while others don't ... -- kamailio 22111 root 3u IPv4 189894820 0t0 TCP 127.0.0.1:46326->127.0.0.1:postgres (ESTABLISHED) kamailio 22113 root 3u IPv4 189894828 0t0 TCP 127.0.0.1:46332->127.0.0.1:postgres (ESTABLISHED) kamailio 22115 root 3u IPv4 189894834 0t0 TCP 127.0.0.1:46334->127.0.0.1:postgres (ESTABLISHED) kamailio 22117 root 3u IPv4 189894842 0t0 TCP 127.0.0.1:46338->127.0.0.1:postgres (ESTABLISHED) kamailio 22119 root 3u IPv4 189894848 0t0 TCP 127.0.0.1:46340->127.0.0.1:postgres (ESTABLISHED) -- So, this gives rise to two questions in my mind: 1. I don't seem to understand the relationship between the number of database connection handles and the total number of child processes. I had always assumed that only SIP workers and other processes specialised into a role with possible "database involvement" (e.g. rtimer, async workers, etc.) would hold database connections. 2. What's going on in the second scenario such that some processes have two connections? Both servers running: -- # kamcmd -s /tmp/kamailio_ctl core.version kamailio 4.4.6 (x86_64/linux) becbde -- Insights much appreciated! -- Alex -- Alex Balashov | Principal | Evariste Systems LLC Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free) Web: http://www.evaristesys.com/, http://www.csrpswitch.com/

5 12

What happens to calls when Kamailio restarts?
by Samuel F. 13 Jul '17

13 Jul '17

Hi, I have a question regarding calls and Kamailio restarts. Suppose Kamailio crashes (and started again), is restarted or failed over to a different server (same IP). What then happens with calls? Let's suppose the following scenario: - 1000 calls active on the machine - Some are in call setup, some are in call, some are in teardown phases - The proxy is stateful - The proxy forwards calls from B2BUA machines to an ITSP (outbound only) - Uses record-routing - Uses loose routing What will be the likely outcome of the restart with regards to the calls in the different phases and accounting for said calls? All the best, Samuel

4 6

Subst_body M Audio
by Nicolas Breuer 13 Jul '17

13 Jul '17

Hello, I'm trying to replace the M part in the SDP Body. Seems not working as expected ( I changed the "s" part without problems ) Code : if ( subst_body('/(^m=.*)/m=testing of rewrite.\r/') ) { $var(s)=""; }; Here's the incoming body message c=IN IP4 217.112.180.235. t=0 0. m=audio 49152 RTP/AVP 8 9 18 101. a=rtpmap:8 PCMA/8000. a=rtpmap:9 G722/8000. a=rtpmap:18 G729/8000. a=fmtp:18 annexb=no. a=rtpmap:101 telephone-event/8000. a=fmtp:101 0-15. After subst. ( note the .10840 on the m line) c=IN IP4 217.112.180.10. t=0 0. m=testing of rewrite..10840 a=rtpmap:8 PCMA/8000. a=rtpmap:9 G722/8000. a=rtpmap:101 telephone-event/8000. a=fmtp:101 0-15. a=nortpproxy:yes.

2 3

issue sending http_async_client POST request
by Abdul Basit 13 Jul '17

13 Jul '17

Hi folks, I am using kamailio -v version: kamailio 5.0.2 (x86_64/linux) flags: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC, Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLACKLIST, HAVE_RESOLV_RES ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. id: unknown compiled on 10:02:27 Jul 4 2017 with gcc 4.9.2 I was trying to send http POST request to my web server example.com following example Example 1.12. http_async_query() usage <https://www.kamailio.org/docs/modules/5.0.x/modules/http_async_client.html#…> https://www.kamailio.org/docs/modules/5.0.x/modules/http_async_client.html according to that we should send parameters in body like # POST $http_req(body) = "{'r_uri':'" + $rU + "', 'f_uri':'" + $fU + "'}"; http_async_query("http://example.com/test.php", "HTTP_REPLY"); But its not working out of the box as described with error message from server: INFO: <script>: route[HTTP_REPLY]: status 400 INFO: <script>: route[HTTP_REPLY]: body Insufficient parameters. I even tried adding additional parameters $http_req(hdr) = "Content-Type: application/x-www-form-urlencoded"; $http_req(method) = "POST"; But again it didn't work. I tried the alternative way which worked fine. # POST $http_req(body) = "r_uri=$rU&f_uri=$fU"; http_async_query("http://example.com/test.php", "HTTP_REPLY"); Is there any issue with documentation or i am missing something for POST request? -- regards, abdul basit | p: +92 32 1416 4196 | o: +92 30 0841 1445

3 4

issue sending http_async_client POST request
by Abdul Basit 13 Jul '17

13 Jul '17

Hi folks, I am using I was trying to send http POST request to my web server example.com following example Example 1.12. http_async_query() usage <https://www.kamailio.org/docs/modules/5.0.x/modules/http_async_client.html#…> https://www.kamailio.org/docs/modules/5.0.x/modules/http_async_client.html according to that we should send parameters in body like # POST $http_req(body) = "{'r_uri':'" + $rU + "', 'f_uri':'" + $fU + "'}"; http_async_query("http://example.com/test.php", "HTTP_REPLY"); But its not working out of the box as described with error message from server: INFO: <script>: route[HTTP_REPLY]: status 400 INFO: <script>: route[HTTP_REPLY]: body Insufficient parameters. I even tried adding additional parameters $http_req(hdr) = "Content-Type: application/x-www-form-urlencoded"; $http_req(method) = "POST"; But again it didn't work. I tried the alternative way which worked fine. # POST $http_req(body) = "r_uri=$rU&f_uri=$fU"; http_async_query("http://example.com/test.php", "HTTP_REPLY"); Is there any issue with documentation or i am missing something for POST request? -- regards, abdul basit | p: +92 32 1416 4196 | o: +92 30 0841 1445

1 0

Call is not placing in kamailio
by Logeshwaran G 13 Jul '17

13 Jul '17

Dear Team, I have installed Kamailio-5.0, and i have included subscriber table as well. Two users have successfully registered but cant able to place the call in between the users. Kindly help me for placing the call. Thanks in Advance, Logesh

2 9

RTPProxy - lookup request failed
by Marian Piater 12 Jul '17

12 Jul '17

Hello, I have a problem with RTPProxy. Scenario: SS7 (PSTN) ---> ASTERISK BOX --> Kamailio --> UAC In case of incoming call from PSTN, when called party answer the call after 60 seconds of ringing, then the call is without audio and in this case I see in the log this message: Creating session Jul 11 11:24:32 b2b-voice-sipproxy-v3 rtpproxy[731]: INFO:handle_command: new session 766d0e006d8969d36c628e363ea7c3e1(a)upc.cz, tag as7a7c86ae;1 requested, type strong Jul 11 11:24:32 b2b-voice-sipproxy-v3 rtpproxy[731]: INFO:handle_command: new session on a port 52902 created, tag as7a7c86ae;1 Jul 11 11:24:32 b2b-voice-sipproxy-v3 rtpproxy[731]: INFO:handle_command: pre-filling caller's address with XXX.XXX.XXX.XXX:32740 Answer after approx 60 seconds Jul 11 11:25:40 b2b-voice-sipproxy-v3 rtpproxy[731]: INFO:handle_command: lookup request failed: session 766d0e006d8969d36c628e363ea7c3e1(a)upc.cz, tags as7a7c86ae;1/l0g9iusua2;1 not found Jul 11 11:25:40 b2b-voice-sipproxy-v3 rtpproxy[731]: INFO:handle_delete: forcefully deleting session 1 on ports 35196/36656 Kamailio log (answer) Jul 11 11:25:40 b2b-voice-sipproxy-v3 kamailio[5268]: INFO: <script>: UID:766d0e006d8969d36c628e363ea7c3e1@upc.cz -- ONREPLY_ROUTE: rtpproxy_manage(co) Jul 11 11:25:40 b2b-voice-sipproxy-v3 kamailio[5268]: ERROR: rtpproxy [rtpproxy.c:2536]: force_rtp_proxy(): incorrect port 0 in reply from rtp proxy It looks like there is somewhere 60 seconds session timeout. But I don't know where. When the call is answered during first 60 seconds, then everything is OK and we have both audio. Kamailio reply route configuration: onreply_route[REPLYROUTE] { # #-- On-replay block routing -- # xlog("L_INFO","UID:$ci -- ONREPLY_ROUTE1: $rm $si avp $avp(s:131) $avp(s:132)"); if(has_body("application/sdp")) { xlog("L_INFO","UID:$ci -- ONREPLY_ROUTE: rtpproxy_manage(co)"); rtpproxy_manage("co"); } if ((isflagset(FLT_NATS) || isbflagset(FLB_NATB)) && status=~"(183)|(2[0-9][0-9])"){ xlog("L_INFO","UID:$ci -- ONREPLY_ROUTE1: force_rtp_proxy"); append_hf("P-hint: onreply_route|force_rtp_proxy \r\n"); } if (isbflagset(FLB_NATB)) { xlog("L_INFO","UID:$ci -- ONREPLY_ROUTE1: P-hint: Onreply-route - fixcontact"); append_hf("P-hint: Onreply-route - fixcontact \r\n"); fix_nated_contact(); } exit; } Some parameters settings. modparam("rtpproxy", "rtpproxy_sock", "udp:127.0.0.1:7722") modparam("rtpproxy", "extra_id_pv", "$avp(extra_id)") modparam("rtpproxy", "rtpproxy_disable_tout", 20) modparam("rtpproxy", "rtpproxy_tout", 2) modparam("tm", "disable_6xx_block", 1) modparam("tm", "fr_timer", 5000) ## 5 seconds. modparam("tm", "restart_fr_on_each_reply", 0) modparam("tm", "auto_inv_100_reason", "Trying") modparam("dialog", "dlg_flag", 4) modparam("dialog", "rr_param", "rtp") modparam("dialog", "default_timeout", 7230) modparam("dialog", "dlg_match_mode", 1) modparam("dialog", "db_mode", 1) modparam("dialog", "enable_stats", 1) modparam("dialog", "send_bye", 1) modparam("dialog", "lreq_callee_headers", "TH: dlh\r\n") modparam("rr", "enable_full_lr", 1) modparam("rr", "append_fromtag", 1) modparam("rr", "enable_double_rr", 1) RTPproxy is installed from Debian package: /usr/bin/rtpproxy -s udp:127.0.0.1 7722 -u rtpproxy rtpproxy -p /var/run/rtpproxy/rtpproxy.pid -F -l XXX.XXX.XXX.XXX -d DBUG LOG_LOCAL0 Any advice? Thanks

3 9

Re: [SR-Users] Setup IMS core Network When Network behind nat
by Mojtaba 12 Jul '17

12 Jul '17

Hi. I found where was my problem. I had a misunderestanding. I used public domaim as outbound proxy and i could register to ims. On 11 Jul 2017 15:00, "Mojtaba" <mespio(a)gmail.com> wrote: > Hi Daniel. > Let me describe more clearly the network. Let me suppose these > configurations: > Private IMS Domain: kamailio0ims.test (192.168.100.200) > username: bob(a)kamailio-ims.test > secret: bob > outboundproxy: pcscf.kamailio-ims.test (192.168.100.101) > With these informations, all things works correctly. > Now suppose we have one public IP with predefined > domain(sbc.ims-domain.com) that is set on PCSCF.(This node has two ip > address, one private ip and on public ip), > How can the bob register to network like as before?because the domain > sbc.ims-domain.com is not validate on IMS network. > should i use the sems-sbc? becuase in this situation the private > domain is not reachables. > If it is needed, let me to describe more. > Thanks > > > > On Tue, Jul 11, 2017 at 2:24 PM, Daniel-Constantin Mierla > <miconda(a)gmail.com> wrote: > > Hello, > > > > do you want the entire platform to be behind a single public ip, or each > > node in the network to run on a private ip but have also a public ip > > associated? > > > > Cheers, > > Daniel > > > > > > On 11.07.17 11:31, Mojtaba wrote: > >> Hello, I am working on IMS core network. In this network we have these > >> node with private IP: > >> P-CSCF: 192.168.100.101(pcscf.kamailio-ims.test) > >> I-CSCF: 192.168.100.102(icscf.kamailio-ims.test) > >> S-CSCF: 192.168.100.103(scscf.kamailio-ims.test) > >> HSS: 192.168.100.200(hss.kamailio-ims.test) > >> I have two default users (bob and alice) and all things right great. > >> Now i want use this network with one public IP behind nat. Let me know > >> What should i do? > >> In one way i could use SEMS-SBC and set public IP on it, How should i > >> config sems-sbc to work correctly? > >> Thanks.With Regads. > >> M.ES.S > >> > >> _______________________________________________ > >> Kamailio (SER) - Users Mailing List > >> sr-users(a)lists.kamailio.org > >> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > > > > -- > > Daniel-Constantin Mierla > > www.twitter.com/miconda -- www.linkedin.com/in/miconda > > Kamailio Advanced Training - www.asipto.com > > Kamailio World Conference - www.kamailioworld.com > > > > > > -- > --Mojtaba Esfandiari.S >

2 1

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