- sr-users - kamailio.org

dispatcher probe
by volga629＠networklab.ca 04 Sep '18

04 Sep '18

Hello Everyone, Is possible access OPTIONS packet generated by dispatcher probe ? I am trying insert something like this. if(is_method("OPTIONS") && $hdr(User-Agent)=~"kamailio") { append_hf("X-Node-ID: $avp(node_id)\r\n"); } volga629

3 4

Can't connect to local MySQL server (13 "Permission denied")
by Ginhoux, Patrick 04 Sep '18

04 Sep '18

Hi, In a previous post ([SR-Users] Questions about changes between 5.0.1 and 5.0.7 <https://lists.kamailio.org/pipermail/sr-users/2018-August/102442.html> ), I reported problem to upgrade my kamailio from 5.0.1 to 5.0.7-7 level. With help from some people, it was finally fixed on my test server in my lab. Now I was expecting to do the same upgrade on a real server using these packages: kamailio-5.0.7-7.el7.x86_64.rpm kamailio-ims-5.0.7-7.el7.x86_64.rpm kamailio-mysql-5.0.7-7.el7.x86_64.rpm kamailio-perl-5.0.7-7.el7.x86_64.rpm kamailio-snmpstats-5.0.7-7.el7.x86_64.rpm But kamailio failed to connect the local MySQL server : Aug 31 08:16:20 in52inmvt2router1-mvt-tpm-sipr /usr/sbin/kamailio[6365]: DEBUG: <core> [db.c:209]: db_bind_mod(): using db bind api for db_mysql Aug 31 08:16:20 in52inmvt2router1-mvt-tpm-sipr /usr/sbin/kamailio[6365]: DEBUG: <core> [db.c:314]: db_do_init2(): connection 0x7fef779958f8 not found in pool Aug 31 08:16:20 in52inmvt2router1-mvt-tpm-sipr /usr/sbin/kamailio[6365]: DEBUG: db_mysql [km_my_con.c:98]: db_mysql_new_connection(): opening connection: mysql://xxxx:xxxx@localhost/siprouter Aug 31 08:16:20 in52inmvt2router1-mvt-tpm-sipr /usr/sbin/kamailio[6365]: ERROR: db_mysql [km_my_con.c:129]: db_mysql_new_connection(): driver error: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (13 "Permission denied") Aug 31 08:16:20 in52inmvt2router1-mvt-tpm-sipr /usr/sbin/kamailio[6365]: ERROR: <core> [db.c:318]: db_do_init2(): could not add connection to the pool Aug 31 08:16:20 in52inmvt2router1-mvt-tpm-sipr /usr/sbin/kamailio[6365]: ERROR: htable [ht_db.c:92]: ht_db_open_con(): failed to connect to the database Aug 31 08:16:20 in52inmvt2router1-mvt-tpm-sipr /usr/sbin/kamailio[6365]: ERROR: <core> [core/sr_module.c:974]: init_mod(): Error while initializing module htable (/usr/lib64/kamailio/modules/htable.so) My "kamailio.cfg" contains the following command: modparam("htable", "db_url", "mysql://siprouter:password@localhost/siprouter") The service unit : "/usr/lib/systemd/system/kamailio.service" content is : [Unit] Description=Kamailio (OpenSER) - the Open Source SIP Server After=network.target mysql.service [Service] Type=simple User=kamailio Group=kamailio Environment='CFGFILE=/etc/kamailio/kamailio.cfg' Environment='SHM_MEMORY=1024' Environment='PKG_MEMORY=8' EnvironmentFile=-/etc/sysconfig/kamailio ExecStart=/usr/sbin/kamailio -DD -P /var/run/kamailio/kamailio.pid -f $CFGFILE -m $SHM_MEMORY -M $PKG_MEMORY Restart=on-failure [Install] WantedBy=multi-user.target The "/etc/sysconfig/kamailio" content is : # # Kamailio startup options # # # Kamailio startup options # # Set to yes to enable kamailio, once configured properly. RUN_KAMAILIO=yes # User to run as USER=kamailio # Group to run as GROUP=kamailio # Amount of shared memory to allocate for the running Kamailio server (in Mb) SHM_MEMORY=1024 # Amount of per-process (package) memory to allocate for Kamailio (in Mb) PKG_MEMORY=8 Below the existing user in mysql : mysql:root:(none)> use mysql; Database changed mysql:root:mysql> select user,host from user; +-----------+-----------+ | user | host | +-----------+-----------+ | myadmin | % | | siprouter | % | | kamailio | localhost | | root | localhost | +-----------+-----------+ I have a symlink to locate the my.cnf : ln -s /myqdata/mysiprdb/data/my.cnf /etc/my.cnf And also this link to fix a htable reload problem : ln -s /myqdata/mysiprdb/data/mysiprdb.sock /var/lib/mysql/mysql.sock I don't find what the problem is this time. So if there is people that could help on the issue, thanks in advance. Cordialement. Patrick GINHOUX

3 6

load-balance to registered trunks?
by David Villasmil 03 Sep '18

03 Sep '18

Hello guys, I've got this scenario where some gateways will register on my kamailio and i need to send them calls on a load-balance fashion. is this possible? Thanks! Regards, David Villasmil email: david.villasmil.work(a)gmail.com phone: +34669448337 ᐧ

4 6

Dispatcher question
by Igor Olhovskiy 03 Sep '18

03 Sep '18

Hi! I’m having some issues with dispatcher and cannot get why it’s not working Idea is to use ds_next_dst right after ds_select_dst I’m having it like this modparam("dispatcher", "list_file", "/tmp/dispatcher.list") modparam("dispatcher", "flags", 2) # Enable dispather failover modparam("dispatcher", "xavp_dst", "_dispacher_dst_list_") … ds_select_dst(«1», «0»); … # Some extra check on $du here … ds_next_dst(); But get in logs WARNING: dispatcher [dispatch.c:2285]: ds_update_dst(): no xavp uri field in next destination record But contents of /tmp/dispatcher.list is 1 sip:172.28.0.12:5060 1 sip:172.28.0.19:5060 Can I somehow dump xavp_dst var to check if ds_select_dst is correct? kamailio 5.2.0-dev6 Regards, Igor

5 17

handle_ruri_alias() question or issue?
by Wilkins, Steve 02 Sep '18

02 Sep '18

Good Morning All, The following Incoming request came in => SIP Incoming Request: [[BYE sip:2406506175@20.20.20.20:5060;alias=10.10.10.5~55157~2 SIP/2.0 I called handle_ruri_alias(), and expected the destination and port to be set to 10.10.10.5:55157, but it was not. It was left 20.20.20.20:5060. Is my thinking correct or is there another way to set the destination and port to the alias? Thanks All!, -Steve

3 9

Having trouble associating response to message request
by Byran Carlock 31 Aug '18

31 Aug '18

Hello, I'll be the first to admit I'm a complete novice to Kamailio, but I'm learning due to necessity. I'm working on setting up Kamailio as a sip proxy (SBC?). Any help would be massively appreciated. The desired setup would be for Kamailio to as an external connection point to authenticate the connection and reverse proxy/NAT the rest of the traffic to the asterisk server, hiding internal topology as we go. Right now I'm using dispatcher with NAT and ALIAS to push connections to proxy@{PROXY IP} to proxy@{ASTERISK EXTERNAL IP}. I'm running into an issue where a "Message" is being sent, forwarded to the Asterisk server and responded to. Then Asterisk spawns a new call ID "To" the proxy rather than the original requestor which of course gets a 484 response. How can I somehow associate these two messages and complete the route? MESSAGE sip:proxy@{ASTERISK<sip:proxy@%7bASTERISK> EXTERNAL IP} SIP/2.0 Via: SIP/2.0/UDP {PROXY IP}:5060;branch=z9hG4bK0542.4d3d95c66b82f5825d9b90ba7ae88191.0 Via: SIP/2.0/UDP {CLIENT IP}:37916;received={CLIENT EXTERNAL IP};rport=37916;branch=z9hG4bKPj9b82293b-8ac4-4314-9cb8-d76716746e Max-Forwards: 69 From: <sip:{CLIENT IP}<sip:%7bCLIENT%20IP%7d>>;tag=8aabdd54-6312-4ba4-bbe4-e713d2cf55a7 To: <sip:proxy@{PROXY IP}<sip:proxy@%7bPROXY%20IP%7d>> Call-ID: 9d7bc193-55d9-479b-8c34-3663c3a8bf3b CSeq: 50215 MESSAGE Accept: text/plain, application/im-iscomposing+xml User-Agent: Digium Android Softphone 4.1.1 (2fccfc8f) X-Digium-User-Agent: Digium Android Softphone 4.1.1 (2fccfc8f) X-Digium-AppServer-RequestType: Preconfig X-Digium-AppServer-Preconfig-Id: ca0175e891557c4e9d6f7314cdbf4044 X-Digium-Software-Version: 4.1.1 (2fccfc8f) X-Digium-AppServer-ID: mobileui0000000004 Content-Type: text/plain Content-Length: 182 P-hint: outbound Message Contents MESSAGE sip:{PROXY<sip:%7bPROXY> IP}:5060 SIP/2.0 Via: SIP/2.0/UDP {ASTERISK EXTERNAL IP}:5060;rport;branch=z9hG4bKPj6c1bdda3-2b78-4ae2-ac19-5ec2ca8b8928 From: <sip:proxy@{ASTERISK INTERNAL IP}<sip:proxy@%7bASTERISK%20INTERNAL%20IP%7d>>;tag=79cb0374-5b41-4550-9158-304a18bb1ee6 To: <sip:{PROXY IP}<sip:%7bPROXY%20IP%7d>> Contact: <sip:asterisk@{ASTERISK EXTERNAL IP}:5060<sip:asterisk@%7bASTERISK%20EXTERNAL%20IP%7d:5060>> Call-ID: 94c778a4-d3b3-42c1-ac26-25664d9d37bc CSeq: 4076 MESSAGE X-Digium-AppServer-ResponseType: PreconfigResponse X-Digium-AppServer-Password: ofPnRi4Pt/tGqdSYNn97tiO8ju/maPvAsG7ZeESGyUUWUgvF0xlMuhAUDVzJE866dv0+QeOowFTawa6UQJKQsQ== X-Digium-AppServer-Session: 471800327353850017 X-Digium-AppServer-Message-Salt: 85DA16A6C8F17E46 X-Digium-AppServer-Message-Sequence: 0 X-Digium-AppServer-ID: mobileui0000000004 Max-Forwards: 70 User-Agent: Asterisk PBX 13.1.0-6.7.rl.1516160751.a9f0643 Content-Type: text/plain Content-Length: 600 MESSAGE CONTENT

1 0

Having trouble associating response to message request
by Byran Carlock 31 Aug '18

31 Aug '18

Hello, I'll be the first to admit I'm a complete novice to Kamailio, but I'm learning due to necessity. I'm working on setting up Kamailio as a sip proxy (SBC?). The desired setup would be for Kamailio to as an external connection point to authenticate the connection and reverse proxy/NAT the rest of the traffic to the asterisk server, hiding internal topology as we go. Right now I'm using dispatcher with NAT and ALIAS to push connections to proxy@{PROXY IP} to proxy@{ASTERISK EXTERNAL IP}. I'm running into an issue where a "Message" is being sent, forwarded to the Asterisk server and responded to. Then Asterisk spawns a new call ID "To" the proxy rather than the original requestor which of course gets a 484 response. How can I somehow associate these two messages and complete the route? MESSAGE sip:proxy@{ASTERISK EXTERNAL IP} SIP/2.0 Via: SIP/2.0/UDP {PROXY IP}:5060;branch=z9hG4bK0542.4d3d95c66b82f5825d9b90ba7ae88191.0 Via: SIP/2.0/UDP {CLIENT IP}:37916;received={CLIENT EXTERNAL IP};rport=37916;branch=z9hG4bKPj9b82293b-8ac4-4314-9cb8-d76716746e Max-Forwards: 69 From: <sip:{CLIENT IP}>;tag=8aabdd54-6312-4ba4-bbe4-e713d2cf55a7 To: <sip:proxy@{PROXY IP}> Call-ID: 9d7bc193-55d9-479b-8c34-3663c3a8bf3b CSeq: 50215 MESSAGE Accept: text/plain, application/im-iscomposing+xml User-Agent: Digium Android Softphone 4.1.1 (2fccfc8f) X-Digium-User-Agent: Digium Android Softphone 4.1.1 (2fccfc8f) X-Digium-AppServer-RequestType: Preconfig X-Digium-AppServer-Preconfig-Id: ca0175e891557c4e9d6f7314cdbf4044 X-Digium-Software-Version: 4.1.1 (2fccfc8f) X-Digium-AppServer-ID: mobileui0000000004 Content-Type: text/plain Content-Length: 182 P-hint: outbound Message Contents MESSAGE sip:{PROXY IP}:5060 SIP/2.0 Via: SIP/2.0/UDP {ASTERISK EXTERNAL IP}:5060;rport;branch=z9hG4bKPj6c1bdda3-2b78-4ae2-ac19-5ec2ca8b8928 From: <sip:proxy@{ASTERISK INTERNAL IP}>;tag=79cb0374-5b41-4550-9158-304a18bb1ee6 To: <sip:{PROXY IP}> Contact: <sip:asterisk@{ASTERISK EXTERNAL IP}:5060> Call-ID: 94c778a4-d3b3-42c1-ac26-25664d9d37bc CSeq: 4076 MESSAGE X-Digium-AppServer-ResponseType: PreconfigResponse X-Digium-AppServer-Password: ofPnRi4Pt/tGqdSYNn97tiO8ju/maPvAsG7ZeESGyUUWUgvF0xlMuhAUDVzJE866dv0+QeOowFTawa6UQJKQsQ== X-Digium-AppServer-Session: 471800327353850017 X-Digium-AppServer-Message-Salt: 85DA16A6C8F17E46 X-Digium-AppServer-Message-Sequence: 0 X-Digium-AppServer-ID: mobileui0000000004 Max-Forwards: 70 User-Agent: Asterisk PBX 13.1.0-6.7.rl.1516160751.a9f0643 Content-Type: text/plain Content-Length: 600 MESSAGE CONTENT

1 0

CentOS_7/kamailio_v5.1.x-rpms/ [Errno -1] Package does not match intended download.
by Denys Pozniak 31 Aug '18

31 Aug '18

Hello! Please check repository for Kamailio v5.1.x for CentOS7: http://download.opensuse.org/repositories/home:/kamailio:/v5.1.x-rpms/CentO… I got error: kamailio-debuginfo-5.1.5-1.el7 FAILED http://download.opensuse.org/repositories/home%3A/kamailio%3A/v5.1.x-rpms/C…: [Errno 14] HTTPS Error 416 - Requested Range Not SatisfiableB --:--:-- ETA Trying other mirror. kamailio-outbound-5.1.5-1.el7. FAILED http://download.opensuse.org/repositories/home%3A/kamailio%3A/v5.1.x-rpms/C…: [Errno -1] Package does not match intended download. Suggestion: run yum --enablerepo=home_kamailio_v5.1.x-rpms clean metadata Trying other mirror. kamailio-5.1.5-1.el7.centos.x8 FAILED http://download.opensuse.org/repositories/home%3A/kamailio%3A/v5.1.x-rpms/C…: [Errno -1] Package does not match intended download. Suggestion: run yum --enablerepo=home_kamailio_v5.1.x-rpms clean metadata Trying other mirror. Error downloading packages: kamailio-5.1.5-1.el7.centos.x86_64: [Errno 256] No more mirrors to try. kamailio-debuginfo-5.1.5-1.el7.centos.x86_64: [Errno 256] No more mirrors to try. kamailio-outbound-5.1.5-1.el7.centos.x86_64: [Errno 256] No more mirrors to try. -- BR, Denys Pozniak

2 1

Re: [SR-Users] Final reply code is wrong in case of 302 and 486 busy
by Marco Capetta 31 Aug '18

31 Aug '18

Hi Daniel, did you have some time to have a look at the issue? Thank you very much Regards Marco

2 1

How to detect and Hangup a call on network lost at Caller or Callee?
by Hamid Hashmi 31 Aug '18

31 Aug '18

Dear Users Please advise how to detect a network lost at caller or callee side. I have tried timeout_socket<https://kamailio.org/docs/modules/5.1.x/modules/rtpproxy.html#rtpproxy.p.ti…> and keepalives <https://kamailio.org/docs/modules/5.1.x/modules/dialog.html#dialog.p.ka_int…> method but nothing worked for me. RTPproxy did not send timeout notification to Kamailio (Issue #1597<https://github.com/kamailio/kamailio/issues/1597>) while there is no options packet within a dialog. Is there any other method to cater such scenario. Regards Hamid R. Hashmi

5 11

Quick way to enable/disable all uac outbound registrations
by Joel Serrano 31 Aug '18

31 Aug '18

Hi, On an active/passive kamailio cluster, we use keepalived to move a virtual IP between the nodes and all signaling goes to that VIP. One of our DID providers requires us to register with every single DID we have from them in order to receive calls for such DID (NOTE: we only want to have the "active" kamailio sending outbound registrations to the carrier). My idea was to have keepalived enable all the outbound registrations when the current node changes to MASTER and disable them when it changes to BACKUP. Is there a quick "enable all" or "disable all" for uac module outbound registrations or do I have to "know in advanced" all of them and enable/disable one by one? In the docs we have: *8.4. uac.reg_disable* *Disable a remote registration record based on a filter. The command has two parameter: attribute and value. The attribute can be: l_uuid, l_username, r_username or auth_username. The value is what should be matcheg against the value of the attribute in the remote registration record.* I don't know if there is an "all" or maybe if a wildcard would work, but from the description it doesn't seem to. Any ideas? Do you guys think this is taking a correct approach? All suggestions are more than welcome!! Thanks, Joel.

3 7

Request Line alases
by Wilkins, Steve 30 Aug '18

30 Aug '18

Hello All, If the below Requests from 40.40.40.40(Asterisk) is received by 10.10.10.10(Kamailio) Request Line: INFO sip:3145553313@10.10.10.10:5060;alias=30.30.30.30~43508~2 SIP/2.0 Shouldn't Kamailio forward this request to 30.30.30.30? so that the '200 OK' can sent back to Asterisk for the response. (In this scenario) Would it be ok to just force a '200 OK' back to Asterisk from Kamailio? Thank you,

2 1

Delay
by Daniel W. Graham 30 Aug '18

30 Aug '18

Recently encountered a delay issue, packets arrive on system but Kamailio doesn't process right away. Here are a few details, any direction on what I can do to narrow down is appreciated. The receive queue normally sits at 0 or has random spike, when this issue occurs receive queue remains high like the below output. Version 5.1.5 ss -4 -n -l | grep 5060 udp UNCONN 321536 0 207.241.130.2:5060 *:* tcp LISTEN 0 128 207.241.130.2:5060 *:* -dan

2 2

IPv6 2 Ipv4
by Karlheinz Knapp 30 Aug '18

30 Aug '18

Hi i serach for a config to convert IPv6 to ipv4. My Provider give me only IPv4 and i have 4000 Customer which have ipv6. Anybody have expierience and a running config ?

3 2

Interesting issue with ACK back from 200 OK INVITE
by Wilkins, Steve 30 Aug '18

30 Aug '18

Hello All, I have had an issue for quite some time where I needed to open two UDP ports (via LISTEN) for some softphone UAC's to stay connected. Funny enough there is one Provider that works with the Single UDP. I think I finally see why I was needing two listening UDP ports. When the ACK is returning from Asterisk to Kamailio, the ACK is coming back as protocol TCP, not SIP, causing the call to drop. I finally realized this but I am not sure what would cause this and why one provider phone works but not the others. Once this is resolved, I may actually say...It works! Thank you, -Steve

1 0

Notify: stateless error reply used: I'm terribly sorry, server error occurred
by Soltanici Ilie 29 Aug '18

29 Aug '18

For some reason, Voicemail Notify messages coming from Asterisk Boxes - are not forwarded to the SIP Extensions by Kamailio. This is the SIP Packet coming to the Kamailio: 2018/08/28 10:59:19.165644 1.1.1.1:5060 -> 2.2.2.2:5060 NOTIFY sip:11@3.3.3.3:21755;rinstance=e6369e13becab3ef;transport=tcp;alias=3.3.3.3~21755~2 SIP/2.0 Via: SIP/2.0/UDP 1.1.1.1:5060;branch=z9hG4bK5f628579;rport Max-Forwards: 70 Route: <sip:2.2.2.2:5060;transport=tcp;ftag=0472e823;lr=on;nat=yes> From: "asterisk" <sip:asterisk@1.1.1.1>;tag=as1833c329 To: <sip:11@3.3.3.3:21755;rinstance=e6369e13becab3ef;transport=tcp;alias=3.3.3.3~21755~2>;tag=0472e823 Contact: <sip:asterisk@1.1.1.1:5060> Call-ID: 93183ZjE3YmI0OGYxMDNiMzhlNzVjZjRjNTc2NTMwZGNmYzk CSeq: 103 NOTIFY User-Agent: NUACOM Event: message-summary Content-Type: application/simple-message-summary Subscription-State: active Content-Length: 93 Messages-Waiting: no Message-Account: sip:asterisk@1.1.1.1 Voice-Message: 0/0 (0/0) And this is the message which I'm receiving in the Kamailio logs: [RELAY] Error when forwarding Request ERROR: sl [sl_funcs.c:362]: sl_reply_error(): stateless error reply used: I'm terribly sorry, server error occurred (1/SL) This is the Relay route: # Forwarding Statefully if ( ! t_relay()) { xlogl( "L_ERR" , "[RELAY] Error when forwarding Request \n " ); sl_reply_error(); } exit ;

2 2

Info: Cluecon Weekly about Kamailio, today at 17:00GMT
by Daniel-Constantin Mierla 29 Aug '18

29 Aug '18

Hello, if you haven't seen the news article on kamailio.org, today at 17:00GMT I will be part of the Cluecon Weekly online video conference to present about what's new lately in Kamailio, plans for the future as well as address questions about using Kamailio together with FreeSwitch. Anyone can join via audio or video calls, more details about at: * https://www.kamailio.org/w/2018/08/kamailio-on-cluecon-weekly-aug-29-2018/ * https://freeswitch.org/confluence/display/FREESWITCH/ClueCon+Weekly+Confere… Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio World Conference -- www.kamailioworld.com Kamailio Advanced Training, Nov 12-14, 2018, in Berlin -- www.asipto.com

1 1

Kamailio consuming UDP packets very slowly leading to high RECV - Q
by sagar malam 29 Aug '18

29 Aug '18

Hello, I am using Kamailio as a SIP proxy.So it receives SIP packet from internet and forwards it to FS servers in local network.When i execute "ss" command i see very high value in RECV-Q column.I THINK IT IS NOT NORMAL.PLEASE CORRECT ME IF I AM WRONG. ==================================================== [root@fep-1 proc]# ss -u -a -n -e | grep 5060 UNCONN 0 0 10.50.8.1:5060 *:* ino:6831630 sk:fd <-> UNCONN 0 0 10.50.7.18:5060 *:* ino:6831629 sk:fe <-> UNCONN *1183104* 0 10.50.7.254:5060 *:* ino:6831627 sk:ff <-> UNCONN *84864* 0 2607:f900:1:3::254:5060 :::* ino:6831628 sk:100 v6only:1 <-> ====================================================== Initially i thought that there is something in script which must be causing kamailio to process UDP request slower but i faced same issue with a very simple script where i simply reply with stateless 200 OK for each sip request : request_route { sl_send_reply("200","OK");exit; $avp(uuid) = $rm + "-" + $ci; ........ ......... ......... ....... Server configuration : OS : CENTOS 7 Kernel : 4.16 CPU : 5 X Intel(R) Xeon(R) CPU E5-2680 v2 @ 2.80GHz RAM : 32 GB Please help me debugging this issue.Thanks in advance

4 9

Using SEMS in IMS-ZTE Network
by Mojtaba 28 Aug '18

28 Aug '18

Hello, I am working with IMS (ZTE vendor), I want to use SBC in front of IMS network for some security policy (Hide Topology), I used SEMS as SBC in this regards, (like what we have in IMS/SEMS in kamailio by Mr Carsten Bock). When the Sebscriber want to register, The Register request received by sems and the forward to IMS(ZTE), But the "503 Service Unavailable" is received from IMS. I enable "enable_reg_caching=yes" in register.sbcprofile''s configuration file in sems. If i use kamailio, instead of SEMS, The Registration request is done successfully.In Kamailio i just forward the Register request to IMS.like this: route { if (is_method("REGISTER")) { $du = "sip:172.23.1.1:5080"; route(RELAY); } } Let me know do the issue is from myself or from IMS(ZTE)? In the fillowing, I paste all SIP Register signalling. First in kamailio, second with SEMS. ================Kamailio================== 172.23.1.252.4080 > 172.23.1.1.5080: [bad udp cksum 0x5e58 -> 0x4193!] UDP, length 787 E../....@.]...............^XREGISTER sip:r-kh.com SIP/2.0 Via: SIP/2.0/UDP 172.23.1.252:4080;branch=z9hG4bK018b.e091260b1b7395975a2ff1be0b9bec60.0 Via: SIP/2.0/UDP 192.168.122.1:64407;branch=z9hG4bK-d8754z-7c208b9d587de818-1---d8754z- Max-Forwards: 69 Contact: <sip:+985137054518@192.168.122.1:64407;rinstance=e664e178fc12691e;transport=UDP> From: <sip:+985137054518@r-kh.com;transport=UDP>;tag=5aef0541 Call-ID: ZWYxMzUzNTQzN2I2MTRiMjE2NWZjMzUzMDFmMDhkOWY. CSeq: 1 REGISTER Expires: 3600 Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, INFO, SUBSCRIBE Supported: replaces, norefersub, extended-refer, timer, X-cisco-serviceuri User-Agent: Z 3.3.25608 r25552 Allow-Events: presence, kpml Content-Length: 0 08:20:53.114198 IP (tos 0x0, ttl 255, id 25839, offset 0, flags [none], proto UDP (17), length 685) 172.23.1.1.5080 > 172.23.1.252.4080: [udp sum ok] UDP, length 657 E...d......$..............l.SIP/2.0 401 Unauthorized Via: SIP/2.0/UDP 172.23.1.252:4080;branch=z9hG4bK018b.e091260b1b7395975a2ff1be0b9bec60.0 Via: SIP/2.0/UDP 192.168.122.1:64407;branch=z9hG4bK-d8754z-7c208b9d587de818-1---d8754z- To: <sip:+985137054518@r-kh.com;transport=UDP>;tag=ztesipTR9m3KdZ*3-5-16648*daei.3 From: <sip:+985137054518@r-kh.com;transport=UDP>;tag=5aef0541 Call-ID: ZWYxMzUzNTQzN2I2MTRiMjE2NWZjMzUzMDFmMDhkOWY. CSeq: 1 REGISTER Content-Length: 0 WWW-Authenticate: Digest realm="r-kh.com",domain="sip:scscf1.r-kh.com",nonce="f42b36e39bdbb33b51599924b304445a",opaque="aW1zLmNvbS5jbg==",stale=TRUE,algorithm=MD5,qop="auth" 08:20:53.120142 IP (tos 0x10, ttl 64, id 48874, offset 0, flags [none], proto UDP (17), length 1137) 172.23.1.252.4080 > 172.23.1.1.5080: [bad udp cksum 0x5f9a -> 0xcc62!] UDP, length 1109 E..q....@.\V.............]_.REGISTER sip:r-kh.com SIP/2.0 Via: SIP/2.0/UDP 172.23.1.252:4080;branch=z9hG4bKd08b.4d2858f41d496b471c01a28e76190390.0 Via: SIP/2.0/UDP 192.168.122.1:64407;branch=z9hG4bK-d8754z-a4d19146375d56f6-1---d8754z- Max-Forwards: 69 Contact: <sip:+985137054518@192.168.122.1:64407;rinstance=e664e178fc12691e;transport=UDP> To: <sip:+985137054518@r-kh.com;transport=UDP> From: <sip:+985137054518@r-kh.com;transport=UDP>;tag=5aef0541 Call-ID: ZWYxMzUzNTQzN2I2MTRiMjE2NWZjMzUzMDFmMDhkOWY. CSeq: 2 REGISTER Expires: 3600 Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, INFO, SUBSCRIBE Supported: replaces, norefersub, extended-refer, timer, X-cisco-serviceuri User-Agent: Z 3.3.25608 r25552 Authorization: Digest username="+985137054518(a)r-kh.com",realm="r-kh.com",nonce="f42b36e39bdbb33b51599924b304445a",uri="sip:r-kh.com;transport=UDP",response="9469852a06c01efeabf3a7a5dd1a9f3b",cnonce="79d36600575648a1cc7221d8e1b5d53d",nc=00000001,qop=auth,algorithm=MD5,opaque="aW1zLmNvbS5jbg==" Allow-Events: presence, kpml Content-Length: 0 08:20:53.203871 IP (tos 0x0, ttl 255, id 25842, offset 0, flags [none], proto UDP (17), length 1118) 172.23.1.1.5080 > 172.23.1.252.4080: [udp sum ok] UDP, length 1090 E..^d......p.............J.5SIP/2.0 200 OK Via: SIP/2.0/UDP 172.23.1.252:4080;branch=z9hG4bKd08b.4d2858f41d496b471c01a28e76190390.0 Via: SIP/2.0/UDP 192.168.122.1:64407;branch=z9hG4bK-d8754z-a4d19146375d56f6-1---d8754z- To: <sip:+985137054518@r-kh.com;transport=UDP>;tag=ztesipjRydzgMa*3-5-16648*daej.3 From: <sip:+985137054518@r-kh.com;transport=UDP>;tag=5aef0541 Call-ID: ZWYxMzUzNTQzN2I2MTRiMjE2NWZjMzUzMDFmMDhkOWY. CSeq: 2 REGISTER Contact: <sip:+985137054518@192.168.122.1:64407;transport=UDP;rinstance=e664e178fc12691e>;expires=1800 Contact: <sip:ZTEAGCF000f425704be720000@agcf2.r-kh.com:5079;appid=2-7;UserRegInfo=002-02-00-0b80-04-172.30.48.143;BACaddr=172.30.48.143;BACport=2944>;expires=1800;+sip.instance="<urn:uuid:172.30.35.41-000>";reg-id=1 P-Associated-URI: <tel:+985137054518> P-Associated-URI: <sip:+985137054518@r-kh.com> Date: Sat, 25 Aug 2018 12:25:17 GMT Authentication-Info: nextnonce="00cfbd64b136c12a4e27b67fd28d19fb",qop=auth,rspauth="91ca956c5eb6ee9f1934e2e770750077",cnonce="79d36600575648a1cc7221d8e1b5d53d",nc=00000001 Content-Length: 0 ============================SEMS======================== 172.23.1.252.5080 > 172.23.1.1.5080: [bad udp cksum 0x5e16 -> 0xe11e!] UDP, length 721 E...C.@.@.................^. REGISTER sip:r-kh.com SIP/2.0 Via: SIP/2.0/UDP 172.23.1.252:5080;branch=z9hG4bK~0uk0ahN;rport From: <sip:+985137054518@r-kh.com;transport=UDP>;tag=34384541-5B814A44000AE296-4B5F5700 To: <sip:+985137054518@r-kh.com;transport=UDP> CSeq: 10 REGISTER Call-ID: 37B52BC0-5B814A44000AE592-4B5F5700 Route: <sip:172.23.1.1:5080;lr> Max-Forwards: 70 Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, INFO, SUBSCRIBE Supported: replaces, norefersub, extended-refer, timer, X-cisco-serviceuri User-Agent: Z 3.3.25608 r25552 Allow-Events: presence, kpml Contact: <sip:+985137054518@192.168.122.1:64407;rinstance=868560f8328d39e9;transport=UDP>;expires=3600 Content-Length: 0 08:23:32.790414 IP (tos 0x0, ttl 255, id 35790, offset 0, flags [none], proto UDP (17), length 593) 172.23.1.1.5080 > 172.23.1.252.5080: [udp sum ok] UDP, length 565 E..Q.....................=..SIP/2.0 401 Unauthorized Via: SIP/2.0/UDP 172.23.1.252:5080;rport=5080;branch=z9hG4bK~0uk0ahN To: <sip:+985137054518@r-kh.com;transport=UDP>;tag=ztesipDEmH2AWT*3-5-16648*egei.3 From: <sip:+985137054518@r-kh.com;transport=UDP>;tag=34384541-5B814A44000AE296-4B5F5700 Call-ID: 37B52BC0-5B814A44000AE592-4B5F5700 CSeq: 10 REGISTER Content-Length: 0 WWW-Authenticate: Digest realm="r-kh.com",domain="sip:scscf1.r-kh.com",nonce="179797f920a09d65b5641e5e87df0d8c",opaque="aW1zLmNvbS5jbg==",stale=TRUE,algorithm=MD5,qop="auth" 08:23:32.855067 IP (tos 0x0, ttl 64, id 17364, offset 0, flags [DF], proto UDP (17), length 1071) 172.23.1.252.5080 > 172.23.1.1.5080: [bad udp cksum 0x5f58 -> 0xf553!] UDP, length 1043 E../C.@.@................._X REGISTER sip:r-kh.com SIP/2.0 Via: SIP/2.0/UDP 172.23.1.252:5080;branch=z9hG4bKeAfKkaZa;rport From: <sip:+985137054518@r-kh.com;transport=UDP>;tag=5A64C27D-5B814A44000CD034-4B6F6700 To: <sip:+985137054518@r-kh.com;transport=UDP> CSeq: 10 REGISTER Call-ID: 5380C97E-5B814A44000CD2A5-4B6F6700 Route: <sip:172.23.1.1:5080;lr> Max-Forwards: 70 Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, INFO, SUBSCRIBE Supported: replaces, norefersub, extended-refer, timer, X-cisco-serviceuri User-Agent: Z 3.3.25608 r25552 Authorization: Digest username="+985137054518(a)r-kh.com",realm="r-kh.com",nonce="179797f920a09d65b5641e5e87df0d8c",uri="sip:r-kh.com;transport=UDP",response="017efb986e17506a82bb01e8eb136b90",cnonce="3764fd5eb2ea9539d61ec14196a2bf00",nc=00000001,qop=auth,algorithm=MD5,opaque="aW1zLmNvbS5jbg==" Allow-Events: presence, kpml Contact: <sip:+985137054518@192.168.122.1:64407;rinstance=868560f8328d39e9;transport=UDP>;expires=3600 Content-Length: 0 08:23:32.860417 IP (tos 0x0, ttl 255, id 35804, offset 0, flags [none], proto UDP (17), length 508) 172.23.1.1.5080 > 172.23.1.252.5080: [udp sum ok] UDP, length 480 E...........................SIP/2.0 503 Service Unavailable Via: SIP/2.0/UDP 172.23.1.252:5080;rport=5080;branch=z9hG4bKeAfKkaZa To: <sip:+985137054518@r-kh.com;transport=UDP>;tag=ztesipxxsD3FR2VG8e9zxR_1dx*1-1-16648*ihad.1 From: <sip:+985137054518@r-kh.com;transport=UDP>;tag=5A64C27D-5B814A44000CD034-4B6F6700 Call-ID: 5380C97E-5B814A44000CD2A5-4B6F6700 CSeq: 10 REGISTER X-ZTE-Cause: "CSCF-1.1.BC004016-BC004288-0-0.pcscf1.r-kh.com" Retry-After: 30 Content-Length: 0 -- --Mojtaba Esfandiari.S

2 3

Parmas in lcr_gw
by Ashutosh chaubey 28 Aug '18

28 Aug '18

Hi, How to give username and password for the gateway in params column in lcr_gw? Regards, Ashutosh

2 1

regular expression in kamailio
by Wilkins, Steve 25 Aug '18

25 Aug '18

Hi All, I am trying get the 10digit number called in on using the following $var(caller) = $(fu{re.subst,[0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9]}); I thought I could use a regular expression for the expression in re.subst,expression Thank you, -Steve

2 8

Listner problems
by Wilkins, Steve 25 Aug '18

25 Aug '18

Hi Joel, Actually, I have a strange issue. If I have a single UDP IP:Port listening, most Providers/Phones have two-way Audio/Video, however, with some Providers/Phones, I need to have two UDP IP:Port listners in order to get two-way Audio/Video. Here is the strange thing. If I enable two, the Providers/Phones that worked when I had a single listener only have one-way Audi/Video. I use Kamailio 5.1 and Asterisk 15.3 (pjsip). This behavior is so strange, Thank you, -Steve

2 2

add listen dynamically
by Wilkins, Steve 24 Aug '18

24 Aug '18

Hi All, Is it possible to add or remove "listen" dynamically? Thank you, -Steve

2 2

Struggling with RTPEngine
by Wilkins, Steve 24 Aug '18

24 Aug '18

Hi Florian, Thank you for your response. I checked and direct-media is off. Just as a recap, here is where I am I just can't get rtpengine to work. I have tried multiple configurations, but to no avail. Note that calls work good if rtpengine is disabled. Here is my setup => Public IP: 20.20.20.20 Private IP 10.10.10.10 flow => webrtc client <-> kamailio+rtpengine <-> asterisk <-> kamailio <-> legacy sip phone rtpenngine startup (I have tried a few different startups) => rtpengine --interface=int/10.10.10.10 --interface=ext/10.10.10.10\!20.20.20.20 --listen-ng=127.0.0.1:12221 --pidfile=/var/run/rtpengine --dtls-passive -f -m 10000 -M 20000 -E kamailio => Invites: rtpengine_manage("trust-address replace-origin replace-session-connection direction=ext direction=int ICE=remove RTP/AVP"); Reply's: rtpengine_manage("trust-address replace-origin replace-session-connection ICE=force RTP/SAVPF"); I have tried direction ext ext; and many other combinations, each producing its own incorrect behavior. Thanks again, Steve

1 0

Struggling with RTPProxy and RTPEngine
by Wilkins, Steve 24 Aug '18

24 Aug '18

Hello all, I can't seem to get either RTPProxy or RTPEngine to work correctly. I have decided to concentrate on RTPEngine because I have read that it works the best. I am using Asterisk with Kamailio in front. When I make calls, I see RTPEngine being hit but I continually get the error "Call-ID not found", calls work but media traffic doesn't go through RTPEngine. I have tried many combination of the flags but I seem to always get the same error. When I look at the tcpdump log, I see that the media offer is not on the RTPEngine port. Is there a common mis-configuration error that can cause this? I know I can send all my logs and configurations but I really want to try and resolve this as a learning experience. Thanks all, -Steve

8 17

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