- sr-users - kamailio.org

Suspend INVITE between ip4 and ip6 users
by Péter Barabás 08 Oct '21

08 Oct '21

Hi, I try to modify the kamailio configuration to work between ipv4 and ipv6 clients. Clients are mobile sofphones, so they are mostly in background without registration. 1. When an INVITE arrives from IPV4 address, transaction is suspended and a push notification is sent to callee. 2. Callee gets push notification and registers to kamailio. 3. INVITE transaction continues. My kamailio config is based on this article: https://kb.asipto.com/kamailio:kamailio-mixed-ipv4-ipv6 using … [View More]

1 0

Missing line in line.count transformation
by Daniel Donoghue 08 Oct '21

08 Oct '21

I think I’ve found an edge case with the string transformations for line.count: In pv_trans.c, the following code does not appear to consider the last line if there are multiple lines and the last one is not terminated with \n. case TR_LINE_COUNT: n=0; for(i=0; i<val->rs.len; i++) if(val->rs.s[i]=='\n') n++; if(n==0 && val->rs.len>0) n = 1; val->flags = PV_TYPE_INT|PV_VAL_INT|PV_VAL_STR; val->ri = n; val->rs.s … [View More]

4 5

Parsing Error in Timer Module of kamailio
by Surabhi Garg 07 Oct '21

07 Oct '21

Hi Team, Greetings! I am trying to use Timer Module of Kamailio to keep calling particular route at particular time interval. Here is the snippet of my config: loadmodule "timer.so" modparam("timer", "declare_timer", "MYTIMER=SHUTDOWN,5000,slow,enable"); route[SHUTDOWN] { xlog("system shutdown: $sht(graceful_shutdown=>shutdown)\n"); } But after restarting the Kamailio, I keep on getting parsing errors in every 5 sec and my route "SHUTDOWN" never get called. Which … [View More]

2 2

[kamailio/kamailio] SIP Preconditions Settings?
by Luis Joel Borrego Soto 07 Oct '21

07 Oct '21

Hi Team, According with the RFC3312 (https://datatracker.ietf.org/doc/html/rfc3312) The SDP parameters are the following We define the following media level SDP attributes: current-status = "a=curr:" precondition-type SP status-type SP direction-tag desired-status = "a=des:" precondition-type SP strength-tag SP status-type SP direction-tag confirm-status = "a=conf:" precondition-type … [View More]

3 3

Need kamailio to use advertise public IP only in cases of SIP communication over internet.
by Voip support 06 Oct '21

06 Oct '21

Dear Community, I have a need of communicating with other servers using private IP with private IP in Via and SDP connection information but at same time sometime need connect to public IP SIP server and on outgoing INVITE's i need advertise public IP in Record-Route and SDP Connection information. Currently if i work on listen=udp:privateip:5060 i get working the LAN part but cannot work over internet (no audio) but when i add advertise i get SDP public IP also over local network. Is it … [View More]

4 3

Understanding regex format for subst_hf
by Joel Serrano 06 Oct '21

06 Oct '21

Hey guys, I'm trying to do a replacement regex using subst_hf but I can't seem to get the format right and the docs are confusing. *subst_hf: *docs say it uses perl-like regex (as I understand it, that would mean PCRE). Docs also say in the 'subexp' param that it uses the same format as *subst.* *subst: *at the beginning it says it uses perl or sed format, but in the '/re/repl/flags' param it says that sed format. https://www.kamailio.org/docs/modules/devel/modules/textops.html#textops.f.… … [View More]

3 7

seas module
by Daniel Paape 05 Oct '21

05 Oct '21

I am having some difficulties with the seas module under Kam 5.5.2. If my application server is not connected then the config file script below never returns if (!as_relay_t ("myserver")) { Xlog ("LM_NOTICE", "myserver not connected\n"); } A diagnostic in the "seas.c" file does report that the app server is not connected, but the one above is never printed. Any help here would be appreciated. This email is intended only for the use of the party to which it is addressed and may contain … [View More]

2 5

Kamailio/RTPengine as a proxy for FreePBX/Asterisk...
by Micah Quinn 03 Oct '21

03 Oct '21

Hello all, I'm new to Kamailio, so bear with me as I stumble through this. First, I'll describe what I'm trying to achieve at a high level and then perhaps somebody can advise me on whether Kamailio is a good fit for this solution or not. I'd like to be able to deploy a small appliance type server to our customer's sites that just runs Kamailio and a VPN connection back to our datacenter. At our datacenter, we run virtualized instances of Asterisk for each of our customers. The idea is that … [View More]

6 22

Kamailio 4.4 + rtpproxy behind the NAT (debian stretch 9.13)
by Youssef Boujraf 02 Oct '21

02 Oct '21

Dear, I am testing the kakamilio 4.4 with rtpproxy on Debian stretch 9.13 I have installed the packages - apt-get install kamailio and rtpproxy. - kamailio 4.4 - rtpproxy Basic version: 20040107 *My version of RTPPROXY doesn't have the -A parameter so that means without advertising there is no way to work behind NAT? That is what I have understood after spending one week on forums. Thanks if somebody could confirm otherwise, which way I need to go to figure out my issue?* # … [View More]rtpproxy -v > Basic version: 20040107 > Extension 20050322: Support for multiple RTP streams and MOH > Extension 20060704: Support for extra parameter in the V command > Extension 20071116: Support for RTP re-packetization > Extension 20071218: Support for forking (copying) RTP stream > Extension 20080403: Support for RTP statistics querying > Extension 20081102: Support for setting codecs in the update/lookup command > Extension 20081224: Support for session timeout notifications > > # rtpproxy -help > rtpproxy: invalid option -- 'h' > usage: rtpproxy [-2fvFiPa] [-l addr1[/addr2]] [-6 addr1[/addr2]] [-s path] > [-t tos] [-r rdir [-S sdir]] [-T ttl] [-L nfiles] [-m port_min] > [-M port_max] [-u uname[:gname]] [-n timeout_socket] [-d > log_level[:log_facility]] > # > /etc/hosts 127.0.0.1 localhost > 127.0.1.1 sip.dom.xx sip > 192.168.1.19 sip.dom.xx sip > PUBLIC_IP sip.dom.xx sip > # The following lines are desirable for IPv6 capable hosts > ::1 localhost ip6-localhost ip6-loopback > ff02::1 ip6-allnodes > ff02::2 ip6-allrouters > */etc/kamailio/kamailio.cfg* kamailio.config > #!define PUBLIC_IP "xxx.xxx.xxx.xxx" > #!define PRIVATE_IP "192.168.1.19" > #!define PRIVATE_NET "192.168.1.0/24“ > listen=udp:PRIVATE_IP:5060 advertise PUBLIC_IP:5060 > > #!ifdef WITH_NAT > > # ----- rtpproxy params ----- > > modparam("rtpproxy", "rtpproxy_sock", "udp:PRIVATE_IP:7722") > > > # ----- nathelper params ----- > > modparam("nathelper", "natping_interval", 30) > > modparam("nathelper", "ping_nated_only", 1) > > modparam("nathelper", "sipping_bflag", FLB_NATSIPPING) > > modparam("nathelper", "sipping_from", "sip:pinger@kamailio.org") > *Etc/default/rtpproxy* PRIVATE_IP=192.168.1.19 > > PUBLIC_IP=xxx.xxx.xxx.xxx > > rtpport_min= 10000 > > rtpport_max=20000 > > syslog=DBUG:LOG_LOCAL5 > > #Defaults for rtpproxy > #The control socket. > #CONTROL_SOCK="unix:/var/run/rtpproxy/rtpproxy.sock" > #To listen on an UDP socket, uncomment this line: > #CONTROL_SOCK=udp:127.0.0.1:7722 > #Additional options that are passed to the daemon. > EXTRA_OPTS="-l $PRIVATE_IP/$PUBLIC_IP ="-s $PRIVATE_IP:7222 -m $ > rtpport_min -M $rtpport_max -d $syslog"` > Thanks if you could route me to the right way. Best regards Yboujraf Email: yboujraf(a)gmail.com [View Less]

3 6

Fail call from Webrct to PSTN SIP trunk
by Abdul Rahman Reza 01 Oct '21

01 Oct '21

Hi, good morning there is something I want to ask, I'm really stuck looking for a solution, haven't found it yet, So I want to make Webrct able to call SIP and PSTN numbers via SIP trunk, but it keeps failing For testing as follows: webrct => SIP OK webrct => PSTN NOK webrct => webrct OK SIP => webrct OK SIP => PSTN OK SIP => SIP OK Thank you very much in advance this is error log from kamailio webrct => PSTN gagal dan error muncul seperti ini : Aug 16 11:25:16 … [View More]

2 2

ACK not accepted
by Angelo Sipper 01 Oct '21

01 Oct '21

Hi, I am having a problem with some inbound calls that all have the below behavior. My setup has: Carrier(UDP) -> (UDP)Kamailio1(UDP) -> (UDP)Kamailio2(TLS) -> (TLS)UAC Kamailio1 has Topos Module. UAC is behind NAT with LAN IP 192.168.1.105 and Public 200.200.200.30 Carrier IP 50.50.50.19, Kamailio1 IP 100.100.100.243, Kamailio2 IP 100.100.100.210 The Carrier sends in a new call and the call is answered from the UAC with 200 OK SDP. Carrier sends ACK and it looks like it reaches the … [View More]UAC but, UAC still resends several times 200 OK and carrier sends server ACK that arrives or not ??? to UAC until finally UAC sends a BYE. On the SIP flow you can see that Kamailio2 sends the ACK to 192.168.1.105 and not to 200.200.200.30. Is this ok?? Another thing to mention is that Kamailio2 that has the UAC connected via TLS, can be used fine from the UAC to make an outbound call following the reverse path, but on the inbound we have the below. Any help will be much appreciated, ACK from Kamailio2 100.100.100.210 to UAC Session Initiation Protocol (ACK) Request-Line: ACK sip:btpsh-f3-6153392a-5fa-5@192.168.1.105:5061;transport=TLS SIP/2.0 Message Header Via: SIP/2.0/TLS 100.100.100.210:5061 ;branch=z9hG4bKfc5f.67a77810bcdafe811ea3672a027450d8.0 Via: SIP/2.0/UDP 100.100.100.243;rport=5060;branch=z9hG4bKfc5f.e2b515e9c8c33d2bd05682f26df24e39.0 Call-ID: isbcaqhye0rozjgeghorzav1vtytoqztkheq(a)B.5.108.ims.forthnet.gr [Generated Call-ID: isbcaqhye0rozjgeghorzav1vtytoqztkheq(a)B.5.108.ims.incarrier.com] From: <sip:987654321@ims.carrier.com ;user=phone>;tag=ZZ58CDf_CZ.Yj2U5 To: <sip:23456789@ims.carrier.com ;user=phone>;tag=0120779a-edf4-464a-9c43-2ddf54459083 CSeq: 1 ACK Max-Forwards: 64 Request-Disposition: no-fork Content-Length: 0 Contact: <sip:btpsh-f3-6153392a-5fa-5@100.100.100.243> |Time | 50.50.50.19 | 100.100.100.210 | 192.168.1.105 | | | | 100.100.100.243 | | 200.200.200.30 | |0.000000 | INVITE SDP (g711A te | | | |SIP INVITE From: < sip:987654321@ims.carrier.com;user=phone> To:<sip:123456789@ims.carrier.com;user=phone> Call-ID:isbcaqhye0rozjgeghorzav1vtytoqztkheq@B.5.108.ims.incarrier.gr CSeq:1 | |(5060) ------------------> (5060) | | | | |0.001737 | 100 trying -- your c | | | |SIP Status 100 trying -- your call is important to us | |(5060) <------------------ (5060) | | | | |0.074622 | | INVITE SDP (g711A te | | |SIP INVITE From: < sip:987654321@ims.carrier.com;user=phone> To:<sip:123456789@ims.carrier.com;user=phone> CSeq:1 | | |(5060) ------------------> (5060) | | | |0.074797 | | INVITE SDP (g711A te | | |SIP INVITE From: < sip:987654321@ims.carrier.com;user=phone> To:<sip:123456789@ims.carrier.com;user=phone> CSeq:1 | | |(5060) ------------------> (5060) | | | |0.081110 | | 100 trying -- your c | | |SIP Status 100 trying -- your call is important to us | | |(5060) <------------------ (5060) | | | |0.082070 | | 100 trying -- your c | | |SIP Status 100 trying -- your call is important to us | | |(5060) <------------------ (5060) | | | |0.082833 | | | INVITE SDP (g711A te | |SIP INVITE From: < sip:987654321@ims.carrier.com;user=phone> To:<sip:123456789@ims.carrier.com;user=phone> CSeq:1 | | | |(5061) ------------------> (37275) | | |0.163871 | | | 100 Trying| | |SIP Status 100 Trying | | | |(5061) <------------------ (37275) | | |0.447621 | | | 180 Ringing | |SIP Status 180 Ringing | | | |(5061) <------------------ (37275) | | |0.448004 | | 180 Ringing | | |SIP Status 180 Ringing | | |(5060) <------------------ (5060) | | | |0.448765 | | 180 Ringing | | |SIP Status 180 Ringing | | |(5060) <------------------ (5060) | | | |0.465033 | 180 Ringing | | | |SIP Status 180 Ringing | |(5060) <------------------ (5060) | | | | |2.529599 | | | 200 OK SDP (g711A) | |SIP Status 200 OK | | | |(5061) <------------------ (37275) | | |2.733556 | | 200 OK SDP (g711A) | | |SIP Status 200 OK | | |(5060) <------------------ (5060) | | | |2.734596 | | 200 OK SDP (g711A) | | |SIP Status 200 OK | | |(5060) <------------------ (5060) | | | |2.864311 | 200 OK SDP (g711A) | | | |SIP Status 200 OK | |(5060) <------------------ (5060) | | | | |3.024789 | | | 200 OK SDP (g711A) | |SIP Status 200 OK | | | |(5061) <------------------ (37275) | | |3.025005 | | 200 OK SDP (g711A) | | |SIP Status 200 OK | | |(5060) <------------------ (5060) | | | |3.025854 | | 200 OK SDP (g711A) | | |SIP Status 200 OK | | |(5060) <------------------ (5060) | | | |3.034979 | 200 OK SDP (g711A) | | | |SIP Status 200 OK | |(5060) <------------------ (5060) | | | | |3.106784 | ACK | | | | |SIP Request INVITE ACK 200 CSeq:1 | |(5060) ------------------> (5060) | | | | |3.126287 | | ACK | | | |SIP ACK From: < sip:987654321@ims.carrier.com;user=phone> To:<sip:123456789@ims.carrier.com;user=phone> CSeq:1 | | |(5060) ------------------> (5060) | | | |3.126542 | | ACK | | | |SIP ACK From: < sip:987654321@ims.carrier.com;user=phone> To:<sip:123456789@ims.carrier.com;user=phone> CSeq:1 | | |(5060) ------------------> (5060) | | | |3.145821 | | | ACK | | |SIP ACK From: < sip:987654321@ims.carrier.com;user=phone> To:<sip:123456789@ims.carrier.com;user=phone> CSeq:1 | | | |(5061) --------------------------------------> (5061) | |4.025449 | | | 200 OK SDP (g711A) | |SIP Status 200 OK | | | |(5061) <------------------ (37275) | | |4.025743 | | 200 OK SDP (g711A) | | |SIP Status 200 OK | | |(5060) <------------------ (5060) | | | |4.026548 | | 200 OK SDP (g711A) | | |SIP Status 200 OK | | |(5060) <------------------ (5060) | | | |4.033198 | 200 OK SDP (g711A) | | | |SIP Status 200 OK | |(5060) <------------------ (5060) | | | | |4.094832 | ACK | | | | |SIP ACK From: < sip:987654321@ims.carrier.com;user=phone> To:<sip:123456789@ims.carrier.com;user=phone> CSeq:1 | |(5060) ------------------> (5060) | | | | |4.102992 | | ACK | | | |SIP ACK From: < sip:987654321@ims.carrier.com;user=phone> To:<sip:123456789@ims.carrier.com;user=phone> CSeq:1 | | |(5060) ------------------> (5060) | | | |4.103316 | | ACK | | | |SIP ACK From: < sip:987654321@ims.carrier.com;user=phone> To:<sip:123456789@ims.carrier.com;user=phone> CSeq:1 | | |(5060) ------------------> (5060) | | | |4.106301 | | | ACK | | |SIP ACK From: < sip:987654321@ims.carrier.com;user=phone> To:<sip:123456789@ims.carrier.com;user=phone> CSeq:1 | | | |(5061) --------------------------------------> (5061) | |6.025167 | | | 200 OK SDP (g711A) | |SIP Status 200 OK | | | |(5061) <------------------ (37275) | | |6.025543 | | 200 OK SDP (g711A) | | |SIP Status 200 OK | | |(5060) <------------------ (5060) | | | |6.026377 | | 200 OK SDP (g711A) | | |SIP Status 200 OK | | |(5060) <------------------ (5060) | | | |6.034778 | 200 OK SDP (g711A) | | | |SIP Status 200 OK | |(5060) <------------------ (5060) | | | | |6.096896 | ACK | | | | |SIP ACK From: < sip:987654321@ims.carrier.com;user=phone> To:<sip:123456789@ims.carrier.com;user=phone> CSeq:1 | |(5060) ------------------> (5060) | | | | |6.104675 | | ACK | | | |SIP ACK From: < sip:987654321@ims.carrier.com;user=phone> To:<sip:123456789@ims.carrier.com;user=phone> CSeq:1 | | |(5060) ------------------> (5060) | | | |6.104910 | | ACK | | | |SIP ACK From: < sip:987654321@ims.carrier.com;user=phone> To:<sip:123456789@ims.carrier.com;user=phone> CSeq:1 | | |(5060) ------------------> (5060) | | | |6.108907 | | | ACK | | |SIP ACK From: < sip:987654321@ims.carrier.com;user=phone> To:<sip:123456789@ims.carrier.com;user=phone> CSeq:1 | | | |(5061) --------------------------------------> (5061) | |10.024538| | | 200 OK SDP (g711A) | |SIP Status 200 OK | | | |(5061) <------------------ (37275) | | |10.024866| | 200 OK SDP (g711A) | | |SIP Status 200 OK | | |(5060) <------------------ (5060) | | | |10.025750| | 200 OK SDP (g711A) | | |SIP Status 200 OK | | |(5060) <------------------ (5060) | | | |10.033461| 200 OK SDP (g711A) | | | |SIP Status 200 OK | |(5060) <------------------ (5060) | | | | |10.095387| ACK | | | | |SIP ACK From: < sip:987654321@ims.carrier.com;user=phone> To:<sip:123456789@ims.carrier.com;user=phone> CSeq:1 | |(5060) ------------------> (5060) | | | | |10.102265| | ACK | | | |SIP ACK From: < sip:987654321@ims.carrier.com;user=phone> To:<sip:123456789@ims.carrier.com;user=phone> CSeq:1 | | |(5060) ------------------> (5060) | | | |10.102449| | ACK | | | |SIP ACK From: < sip:987654321@ims.carrier.com;user=phone> To:<sip:123456789@ims.carrier.com;user=phone> CSeq:1 | | |(5060) ------------------> (5060) | | | |10.105760| | | ACK | | |SIP ACK From: < sip:987654321@ims.carrier.com;user=phone> To:<sip:123456789@ims.carrier.com;user=phone> CSeq:1 | | | |(5061) --------------------------------------> (5061) | |14.025310| | | 200 OK SDP (g711A) | |SIP Status 200 OK | | | |(5061) <------------------ (37275) | | |14.025585| | 200 OK SDP (g711A) | | |SIP Status 200 OK | | |(5060) <------------------ (5060) | | | |14.026528| | 200 OK SDP (g711A) | | |SIP Status 200 OK | | |(5060) <------------------ (5060) | | | |14.037027| 200 OK SDP (g711A) | | | |SIP Status 200 OK | |(5060) <------------------ (5060) | | | | |14.099479| ACK | | | | |SIP ACK From: < sip:987654321@ims.carrier.com;user=phone> To:<sip:123456789@ims.carrier.com;user=phone> CSeq:1 | |(5060) ------------------> (5060) | | | | |14.111540| | ACK | | | |SIP ACK From: < sip:987654321@ims.carrier.com;user=phone> To:<sip:123456789@ims.carrier.com;user=phone> CSeq:1 | | |(5060) ------------------> (5060) | | | |14.111708| | ACK | | | |SIP ACK From: < sip:987654321@ims.carrier.com;user=phone> To:<sip:123456789@ims.carrier.com;user=phone> CSeq:1 | | |(5060) ------------------> (5060) | | | |14.116089| | | ACK | | |SIP ACK From: < sip:987654321@ims.carrier.com;user=phone> To:<sip:123456789@ims.carrier.com;user=phone> CSeq:1 | | | |(5061) --------------------------------------> (5061) | |18.025311| | | 200 OK SDP (g711A) | |SIP Status 200 OK | | | |(5061) <------------------ (37275) | | |18.025659| | 200 OK SDP (g711A) | | |SIP Status 200 OK | | |(5060) <------------------ (5060) | | | |18.026572| | 200 OK SDP (g711A) | | |SIP Status 200 OK | | |(5060) <------------------ (5060) | | | |18.034736| 200 OK SDP (g711A) | | | |SIP Status 200 OK | |(5060) <------------------ (5060) | | | | |18.096101| ACK | | | | |SIP ACK From: < sip:987654321@ims.carrier.com;user=phone> To:<sip:123456789@ims.carrier.com;user=phone> CSeq:1 | |(5060) ------------------> (5060) | | | | |18.106560| | ACK | | | |SIP ACK From: < sip:987654321@ims.carrier.com;user=phone> To:<sip:123456789@ims.carrier.com;user=phone> CSeq:1 | | |(5060) ------------------> (5060) | | | |18.106687| | ACK | | | |SIP ACK From: < sip:987654321@ims.carrier.com;user=phone> To:<sip:123456789@ims.carrier.com;user=phone> CSeq:1 | | |(5060) ------------------> (5060) | | | |18.111007| | | ACK | | |SIP ACK From: < sip:987654321@ims.carrier.com;user=phone> To:<sip:123456789@ims.carrier.com;user=phone> CSeq:1 | | | |(5061) --------------------------------------> (5061) | |22.024673| | | 200 OK SDP (g711A) | |SIP Status 200 OK | | | |(5061) <------------------ (37275) | | |22.024953| | 200 OK SDP (g711A) | | |SIP Status 200 OK | | |(5060) <------------------ (5060) | | | |22.026120| | 200 OK SDP (g711A) | | |SIP Status 200 OK | | |(5060) <------------------ (5060) | | | |22.033514| 200 OK SDP (g711A) | | | |SIP Status 200 OK | |(5060) <------------------ (5060) | | | | |22.095104| ACK | | | | |SIP ACK From: < sip:987654321@ims.carrier.com;user=phone> To:<sip:123456789@ims.carrier.com;user=phone> CSeq:1 | |(5060) ------------------> (5060) | | | | |22.105921| | ACK | | | |SIP ACK From: < sip:987654321@ims.carrier.com;user=phone> To:<sip:123456789@ims.carrier.com;user=phone> CSeq:1 | | |(5060) ------------------> (5060) | | | |22.106043| | ACK | | | |SIP ACK From: < sip:987654321@ims.carrier.com;user=phone> To:<sip:123456789@ims.carrier.com;user=phone> CSeq:1 | | |(5060) ------------------> (5060) | | | |22.110298| | | ACK | | |SIP ACK From: < sip:987654321@ims.carrier.com;user=phone> To:<sip:123456789@ims.carrier.com;user=phone> CSeq:1 | | | |(5061) --------------------------------------> (5061) | |26.031501| | | 200 OK SDP (g711A) | |SIP Status 200 OK | | | |(5061) <------------------ (37275) | | |26.031903| | 200 OK SDP (g711A) | | |SIP Status 200 OK | | |(5060) <------------------ (5060) | | | |26.033136| | 200 OK SDP (g711A) | | |SIP Status 200 OK | | |(5060) <------------------ (5060) | | | |26.040343| 200 OK SDP (g711A) | | | |SIP Status 200 OK | |(5060) <------------------ (5060) | | | | |26.101967| ACK | | | | |SIP ACK From: < sip:987654321@ims.carrier.com;user=phone> To:<sip:123456789@ims.carrier.com;user=phone> CSeq:1 | |(5060) ------------------> (5060) | | | | |26.111938| | ACK | | | |SIP ACK From: < sip:987654321@ims.carrier.com;user=phone> To:<sip:123456789@ims.carrier.com;user=phone> CSeq:1 | | |(5060) ------------------> (5060) | | | |26.112432| | ACK | | | |SIP ACK From: < sip:987654321@ims.carrier.com;user=phone> To:<sip:123456789@ims.carrier.com;user=phone> CSeq:1 | | |(5060) ------------------> (5060) | | | |26.118306| | | ACK | | |SIP ACK From: < sip:987654321@ims.carrier.com;user=phone> To:<sip:123456789@ims.carrier.com;user=phone> CSeq:1 | | | |(5061) --------------------------------------> (5061) | |30.035446| | | 200 OK SDP (g711A) | |SIP Status 200 OK | | | |(5061) <------------------ (37275) | | |30.035693| | 200 OK SDP (g711A) | | |SIP Status 200 OK | | |(5060) <------------------ (5060) | | | |30.036501| | 200 OK SDP (g711A) | | |SIP Status 200 OK | | |(5060) <------------------ (5060) | | | |30.044170| 200 OK SDP (g711A) | | | |SIP Status 200 OK | |(5060) <------------------ (5060) | | | | |30.106395| ACK | | | | |SIP ACK From: < sip:987654321@ims.carrier.com;user=phone> To:<sip:123456789@ims.carrier.com;user=phone> CSeq:1 | |(5060) ------------------> (5060) | | | | |30.116960| | ACK | | | |SIP ACK From: < sip:987654321@ims.carrier.com;user=phone> To:<sip:123456789@ims.carrier.com;user=phone> CSeq:1 | | |(5060) ------------------> (5060) | | | |30.117412| | ACK | | | |SIP ACK From: < sip:987654321@ims.carrier.com;user=phone> To:<sip:123456789@ims.carrier.com;user=phone> CSeq:1 | | |(5060) ------------------> (5060) | | | |30.129913| | | ACK | | |SIP ACK From: < sip:987654321@ims.carrier.com;user=phone> To:<sip:123456789@ims.carrier.com;user=phone> CSeq:1 | | | |(5061) --------------------------------------> (5061) | |34.026492| | | 200 OK SDP (g711A) | |SIP Status 200 OK | | | |(5061) <------------------ (37275) | | |34.026807| | 200 OK SDP (g711A) | | |SIP Status 200 OK | | |(5060) <------------------ (5060) | | | |34.027775| | 200 OK SDP (g711A) | | |SIP Status 200 OK | | |(5060) <------------------ (5060) | | | |34.035453| 200 OK SDP (g711A) | | | |SIP Status 200 OK | |(5060) <------------------ (5060) | | | | |34.097385| ACK | | | | |SIP ACK From: < sip:987654321@ims.carrier.com;user=phone> To:<sip:123456789@ims.carrier.com;user=phone> CSeq:1 | |(5060) ------------------> (5060) | | | | |34.106319| | ACK | | | |SIP ACK From: < sip:987654321@ims.carrier.com;user=phone> To:<sip:123456789@ims.carrier.com;user=phone> CSeq:1 | | |(5060) ------------------> (5060) | | | |34.106681| | ACK | | | |SIP ACK From: < sip:987654321@ims.carrier.com;user=phone> To:<sip:123456789@ims.carrier.com;user=phone> CSeq:1 | | |(5060) ------------------> (5060) | | | |34.110714| | | ACK | | |SIP ACK From: < sip:987654321@ims.carrier.com;user=phone> To:<sip:123456789@ims.carrier.com;user=phone> CSeq:1 | | | |(5061) --------------------------------------> (5061) | |34.526688| | | BYE | | |SIP Request BYE CSeq:15322 | | | |(5061) <------------------ (37275) | | |34.528722| | BYE | | | |SIP Request BYE CSeq:15322 | | |(5060) <------------------ (5060) | | | |34.529704| | BYE | | | |SIP Request BYE CSeq:15322 | | |(5060) <------------------ (5060) | | | |34.668418| BYE | | | | |SIP Request BYE CSeq:15322 | |(5060) <------------------ (5060) | | | | |34.788963| 200 OK | | | | |SIP Status 200 OK | |(5060) ------------------> (5060) | | | | |34.796051| | 200 OK | | | |SIP Status 200 OK | | |(5060) ------------------> (5060) | | | |34.796205| | 200 OK | | | |SIP Status 200 OK | | |(5060) ------------------> (5060) | | | |34.796604| | | 200 OK | | |SIP Status 200 OK | | | |(5061) ------------------> (37275) | | Kind regards, Angelo [View Less]

1 3

Querying presence state from config file
by Igor Olhovskiy 01 Oct '21

01 Oct '21

Hello! Is there any method of querying presence (dialog) state for particular endpoint from config file other than that direct query to presence tables in database? Idea is to reflect server-side DND state as "confirmed" (talking) , so I need to skip certain PUBLISH messages not to reset this state. -- Best regards, Igor

2 2

kamailio 4.4 + RTPPROXY - virtualbox - setup - callee or caller sends INVITE during the conversation and at REGISTER EXPIRES stop the connection
by Youssef Boujraf 01 Oct '21

01 Oct '21

Dear Thanks for your quick reply and sorry for spamming your mailbox. I am very confused about the setup of kamailio.cfg and rtpproxy. I have an existing kamailio 4.4 - rtpproxy running and I get the config files from both and setup the new vm. Just private connection works but the idea is to have connection from outside too. I am sure there is a mismatch with public ip, natting and/or setup of the vm hosts file. - architecture: *- 1x virtualbox* + 1x vm with bridge mode for network (… [View More]get private ip address from the router). I suppose this is the PRIVATE_IP *+ 1x desktop (windows)* hosting a sipphone here Microsip ( https://www.microsip.org/) *- 1x modem/router* from the telecom provider - bbox-3V+ from PROXIMUS + forced in DMZ host the Kamailio server PRIVATE_IP [image: 211001 - kamailio architecture and settings.png] - the hosts file from Kamailio + rtpproxy is ( Maybe something is wrong or missing) /etc/hosts 127.0.0.1 localhost > 127.0.1.1 sipsecure.by-systems.be sipsecure > 192.168.1.19 sipsecure.by-systems.be sipsecure > xxx.XXX.xxx.XXX sipsecure.by-systems.be sipsecure > # The following lines are desirable for IPv6 capable hosts > ::1 localhost ip6-localhost ip6-loopback > ff02::1 ip6-allnodes > ff02::2 ip6-allrouters > */etc/kamailio/kamailio.cfg* kamailio.config > #!define PUBLIC_IP "xxx.xxx.xxx.xxx" > #!define PRIVATE_IP "192.168.1.19" > #!define PRIVATE_NET "192.168.1.0/24“ > > #!ifdef WITH_NAT > > # ----- rtpproxy params ----- > > modparam("rtpproxy", "rtpproxy_sock", "udp:PRIVATE_IP:7722") > > > # ----- nathelper params ----- > > modparam("nathelper", "natping_interval", 30) > > modparam("nathelper", "ping_nated_only", 1) > > modparam("nathelper", "sipping_bflag", FLB_NATSIPPING) > > modparam("nathelper", "sipping_from", "sip:pinger@kamailio.org") > *Etc/default/rtpproxy* PRIVATE_IP=192.168.1.19 > > PUBLIC_IP=xxx.xxx.xxx.xxx > > rtpport_min= 10000 > > rtpport_max=20000 > > syslog=DBUG:LOG_LOCAL5 > > #Defaults for rtpproxy > #The control socket. > #CONTROL_SOCK="unix:/var/run/rtpproxy/rtpproxy.sock" > #To listen on an UDP socket, uncomment this line: > #CONTROL_SOCK=udp:127.0.0.1:7722 > #Additional options that are passed to the daemon. > EXTRA_OPTS="-l $PRIVATE_IP/$PUBLIC_IP ="-s $PRIVATE_IP:7222 -m $ > rtpport_min -M $rtpport_max -d $syslog"` > - *Misconfiguring the VM* That means do I need to use setup 1 or 2 or another 1. 2x NIC interfaces (one with private ip, second from dmz ip + NAT1:1 public ip) 2. 1x NIC interface (one private ip and natted 1:1 with public address) - *test* 1. *use case 1 : *connect two (2x) sipphone from private network (included kamailio) = OK 2. *use case 2 :* connect one (1x) codec from private ip and one (1x) codec from public network (like mobile) = = issue - disconnect after 30 s (register expires) start a conversation with audio but the caller or the callee continues to send and INVITE message. 3. *use case 3 :* connect two (2x) sipphone from public network = issue - disconnect after 30 s (register expires) start a conversation with audio but the caller or the callee continue to send an INVITE message. Best Regards, Youssef BOUJRAF [View Less]

1 0

RTPEngine + Kamailio state question
by Alex Balashov 30 Sep '21

30 Sep '21

Hi, Sorry if I missed any developments on this, but: Kamailio does keep a runtime association of Call-ID+Ftag => RTPEngine instance, which is significant if an RTPEngine set with multiple members is used, or if a non-default set is used for a given call. When Kamailio is restarted, this runtime association goes away, so any subsequent offer/answer cycles or any other commands will (maybe) go to the wrong RTPEngine and/or the wrong set. Last time I checked a few years ago, there was no … [View More]

3 6

Sipwise SEMS
by David Villasmil 30 Sep '21

30 Sep '21

Hello guys, I know SEMS can provide conference, voicemail, and other services. In theory it’s also a B2BUA. Could I use a python script to provide a simple routing service? I.e.: receive an invite and send it somewhere else based on some routing logic? Thanks all David -- Regards, David Villasmil email: david.villasmil.work(a)gmail.com phone: +34669448337

10 22

using LDAP as database ?
by Volker Denneberg 28 Sep '21

28 Sep '21

Hi, I am searching for a setup where phones register at a central kamailio and kamailio shares these contact infos with multiple asterisks. So they all need to share a database. For redundancy reasons, the database should work across 2 datacenters. As far as 1 understood there are some options * use mysql - good chances to find example code, Siremis API, seems to be the standard solution * use redis - more performant than mysql * use ldap - good chances to integrate with existing … [View More]

2 1

siptrace & topos modules on 5.3
by Angelo Sipper 24 Sep '21

24 Sep '21

Hi, We are using kamailio 5.3 latest version with the topos module. We have added Homer 7 latest version to consolidate traces from all kamailios and we have enabled siptrace module on kamailio to send data to homer. What we have seen up today is that traces on homer have sip headers before topos changes. So if I look at the same call on sngrep on the kamailio machine, I see the correct topos changed headers. If I check the same call on Homer I see headers without topos changes. Also we get … [View More]

3 5

Info: APT Debian/Ubuntu Packages Archive
by Daniel-Constantin Mierla 24 Sep '21

24 Sep '21

Hello, a new server is available to offer APT repositories for each released version of Kamailio: * https://deb-archive.kamailio.org/ It aims to offer a way to downgrade to an older version, if someone wants it for various reasons. At this moment it offers dedicated APT repositories for Kamailio 5.3.8, 5.4.6, 5.4.7, 5.5.1 and 5.5.2. More details were posted in a news article at: * https://www.kamailio.org/w/2021/09/apt-debian-packages-archive/ Cheers, Daniel -- Daniel-… [View More]

1 0

PRACK with UDP to TCP translation send over wrong protocol
by Angelo Sipper 24 Sep '21

24 Sep '21

Hello, We have the following setup and I am having trouble passing the PRACK with correct protocol to the provider. UAC (OverTLS) ->(UDP)Kamailio1 (UDP)-> (UDP)Kamailio2 (TCP)-> (TCP)Provider UAC : 10.2.1.160 NATED to 100.100.100.61 <http://50.50.50.50:5065/> (TLS) Kamailio1 Sockets: 50.50.50.210:5061 <http://170.170.170.210:5061/> (TLS), 50.50.50.210:5060 <http://170.170.170.210:5060/> (UDP) Kamailio2 Sockets: 50.50.50.182:5060 <http://170.170.170.170:5060/> … [View More](UDP) 50.50.50.182:5080 <http://170.170.170.170:5060/> (TCP) Provider: 200.200.200.209:5060 <http://200.200.200.193:5060/> (TCP) We use dispatcher on Kamailio1 & Kamailio2 The invite goes fine from UCA up to the provider and the provider responses arrive to UAC fine. The PRACK from UAC to kamailio1 goes fine to Kamaili02 but, Kamailio2 uses the UDP socket to send to the provider so the PRACK does not arrive to the provider and the call is canceled. If the provider is on UDP everything works fine. Below I have the trace. What should I look for in the config to resolve this wrong protocol/socket on the PRACK? Kamailio2 Details: Sockets ====== listen=udp:50.50.50.182:5060 listen=tcp: 50.50.50.182:5080 On the rr module I have ================== modparam("rr", "enable_double_rr", 1) modparam("rr", "append_fromtag", 1) modparam("rr", "enable_full_lr", 1) CONFIG REQINIT & WITHINDLG PARTS ================================ route[REQINIT] { set_reply_no_connect(); force_rport(); if (!mf_process_maxfwd_header("10")) { xlog("L_ERROR","Too Many Hops Rejecting!"); sl_send_reply("483","Too Many Hops"); exit; } if(is_method("OPTIONS") && uri==myself && $rU==$null) { sl_send_reply("200","Keepalive"); exit; } if(!sanity_check("1511", "7")) { xlog("Malformed SIP message from $si:$sp sanity 1511\n"); exit; } if(!sanity_check("17895", "7")) { xlog("Malformed SIP request from $si:$sp sanity 17895\n"); exit; } } route[WITHINDLG] { if (!has_totag()) return; if (loose_route()) { if (is_method("BYE")) { rtpengine_query(); rtpengine_delete(); } route(RELAY_OUT); } if ( is_method("ACK") ) { #if (t_lookup_request()) { if (t_check_trans()) { route(RELAY_OUT); exit; } else { # ACK without matching transaction ... ignore and discard exit; } } sl_send_reply("404","Not Allowed"); exit; } TRACE ====== 50.50.50.210:5060 50.50.50.182:5060 50.50.50.182:32818 200.200.200.209:5060 qqqqqqqqqqwqqqqqqq qqqqqqqqqqwqqqqqqq qqqqqqqqqqwqqqqqqqq qqqqqqqqqqqwqqqqqqqqq a 15:31:11.787490 x INVITE (SDP) x x x a +0.003099 x qqqqqqqqqqqqqqqqqqqqqqqqqq> x x x a 15:31:11.790589 x 100 trying -- your call is x x x a +0.002220 x <qqqqqqqqqqqqqqqqqqqqqqqqqq x x x a 15:31:11.792809 x x x INVITE (SDP) x a +0.020725 x x x qqqqqqqqqqqqqqqqqqqqqqqqqq> x a 15:31:11.813534 x x x 100 Trying x a +2.628884 x x x <qqqqqqqqqqqqqqqqqqqqqqqqqq x a 15:31:14.442418 x x x 183 Session Progress (SDP) x a +0.001572 x x x <qqqqqqqqqqqqqqqqqqqqqqqqqq x a 15:31:14.443990 x 183 Session Progress (SDP) x x x a +0.299221 x <qqqqqqqqqqqqqqqqqqqqqqqqqq x x x a 15:31:14.743211 x PRACK x x x a +0.043114 x qqqqqqqqqqqqqqqqqqqqqqqqqq> x x x a 15:31:14.786325 x x PRACK x a +0.448104 x x qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqq> x a 15:31:15.234429 x PRACK x x x a +0.045697 x qqqqqqqqqqqqqqqqqqqqqqqq>>> x x x a 15:31:15.280126 x x PRACK x a +0.954153 x x qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqq>>> x a 15:31:16.234279 x PRACK x x x a +0.045832 x qqqqqqqqqqqqqqqqqqqqqqqq>>> x x x a 15:31:16.280111 x x PRACK x a +1.954170 x x qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqq>>> x a 15:31:18.234281 x PRACK x x x a +0.045839 x qqqqqqqqqqqqqqqqqqqqqqqq>>> x x x a 15:31:18.280120 x x PRACK x a +1.829676 x x qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqq>>> x a 15:31:20.109796 x x x 183 Session Progress (SDP) x a +0.001460 x x x <<<qqqqqqqqqqqqqqqqqqqqqqqq x a 15:31:20.111256 x 183 Session Progress (SDP) x x x a +2.123075 x <<<qqqqqqqqqqqqqqqqqqqqqqqq x x x a 15:31:22.234331 x PRACK x x x a +0.045825 x qqqqqqqqqqqqqqqqqqqqqqqq>>> x x x a 15:31:22.280156 x x PRACK x a +2.239640 x x qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqq>>> x a 15:31:24.519796 x x x 486 Busy Here x a +0.000555 x x x <qqqqqqqqqqqqqqqqqqqqqqqqqq x a 15:31:24.520351 x x x ACK x a +0.008965 x x x qqqqqqqqqqqqqqqqqqqqqqqqqq> x a 15:31:24.529316 x 486 Busy Here x x x a +0.000835 x <qqqqqqqqqqqqqqqqqqqqqqqqqq x x x a 15:31:24.530151 x ACK x x x a +1.704184 x qqqqqqqqqqqqqqqqqqqqqqqqqq> x x x a 15:31:26.234335 x PRACK x x x a +0.045856 x qqqqqqqqqqqqqqqqqqqqqqqqqq> x x x a 15:31:26.280191 x x PRACK x a +3.954734 x x qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqq>>> x a 15:31:30.234925 x PRACK x x x x +0.045279 x qqqqqqqqqqqqqqqqqqqqqqqq>>> x x x x 15:31:30.280204 x x PRACK x x +3.954116 x x qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqq>>> x x 15:31:34.234320 x PRACK x x x 2021/09/21 15:31:11.787490 50.50.50.210:5060 -> 50.50.50.182:5060 INVITE sip:123456789@sip.mydomain.com:5060 SIP/2.0 Record-Route: <sip:50.50.50.210;r2=on;lr;ftag=73622588a6084d8ba1bca54781e5094d;vsf=AAAAAFpUAgECBwAABnEBB3ZdWEIAQkVFS0BHX2ljZS5ldQ--;vst=AAAAAAAAAAAKCQ8ABAkHCAYKAgdxQFpGbkJCRktDREFYU1AAV0Qw;did=e8e.bb7;nat=yes> Record-Route: <sip:50.50.50.210:5061 ;transport=tls;r2=on;lr;ftag=73622588a6084d8ba1bca54781e5094d;vsf=AAAAAFpUAgECBwAABnEBB3ZdWEIAQkVFS0BHX2ljZS5ldQ--;vst=AAAAAAAAAAAKCQ8ABAkHCAYKAgdxQFpGbkJCRktDREFYU1AAV0Qw;did=e8e.bb7;nat=yes> Via: SIP/2.0/UDP 50.50.50.210;branch=z9hG4bK37fe.f05cee0feff15d488a12d3758cece7ae.0;i=baa3 Via: SIP/2.0/TLS 10.2.1.160:58568 ;received=100.100.100.61;rport=48572;branch=z9hG4bKPj472f07568b924214ada83ddfb0fb12b6;alias Max-Forwards: 69 From: 987654321 <sip:987654321@sip.mydomain.com >;tag=73622588a6084d8ba1bca54781e5094d To: <sip:123456789@sip.mydomain.com> Contact: "MyUserNAme" <sip:mycustomerid@10.2.1.160:58568 ;transport=TLS;ob;alias=100.100.100.61~48572~3> Call-ID: 846ffb2f076848c5b8edc876fa1c0d9b CSeq: 14320 INVITE Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, INFO, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS Supported: replaces, 100rel, timer, norefersub Session-Expires: 1800 Min-SE: 90 User-Agent: MicroSIP/3.20.5 Content-Type: application/sdp Content-Length: 326 P-Asserted-Identity: <sip:987654321@sip.mydomain.com> v=0 o=- 3841227071 3841227071 IN IP4 50.50.50.215 s=pjmedia b=AS:84 t=0 0 a=X-nat:0 m=audio 36448 RTP/AVP 8 0 101 c=IN IP4 50.50.50.215 b=TIAS:64000 a=ssrc:2024148033 cname:4f2468fd611910fa a=rtpmap:8 PCMA/8000 a=rtpmap:0 PCMU/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=sendrecv a=rtcp:36449 2021/09/21 15:31:11.790589 50.50.50.182:5060 -> 50.50.50.210:5060 SIP/2.0 100 trying -- your call is important to us Via: SIP/2.0/UDP 50.50.50.210;branch=z9hG4bK37fe.f05cee0feff15d488a12d3758cece7ae.0;i=baa3;rport=5060 Via: SIP/2.0/TLS 10.2.1.160:58568 ;received=100.100.100.61;rport=48572;branch=z9hG4bKPj472f07568b924214ada83ddfb0fb12b6;alias From: 987654321 <sip:987654321@sip.mydomain.com >;tag=73622588a6084d8ba1bca54781e5094d To: <sip:123456789@sip.mydomain.com> Call-ID: 846ffb2f076848c5b8edc876fa1c0d9b CSeq: 14320 INVITE Server: myserver Content-Length: 0 2021/09/21 15:31:11.792809 50.50.50.182:32818 -> 200.200.200.209:5060 INVITE sip:123456789@sip.mydomain.com:5060 SIP/2.0 Record-Route: <sip:50.50.50.182:5080 ;transport=tcp;r2=on;lr=on;ftag=73622588a6084d8ba1bca54781e5094d;did=e8e.c4d1> Record-Route: <sip:50.50.50.182;r2=on;lr=on;ftag=73622588a6084d8ba1bca54781e5094d;did=e8e.c4d1> Record-Route: <sip:50.50.50.210;r2=on;lr;ftag=73622588a6084d8ba1bca54781e5094d;vsf=AAAAAFpUAgECBwAABnEBB3ZdWEIAQkVFS0BHX2ljZS5ldQ--;vst=AAAAAAAAAAAKCQ8ABAkHCAYKAgdxQFpGbkJCRktDREFYU1AAV0Qw;did=e8e.bb7;nat=yes> Record-Route: <sip:50.50.50.210:5061 ;transport=tls;r2=on;lr;ftag=73622588a6084d8ba1bca54781e5094d;vsf=AAAAAFpUAgECBwAABnEBB3ZdWEIAQkVFS0BHX2ljZS5ldQ--;vst=AAAAAAAAAAAKCQ8ABAkHCAYKAgdxQFpGbkJCRktDREFYU1AAV0Qw;did=e8e.bb7;nat=yes> Via: SIP/2.0/TCP 50.50.50.182:5080 ;branch=z9hG4bK37fe.254ecab744d678154779037580c59731.0 Via: SIP/2.0/UDP 50.50.50.210;rport=5060;branch=z9hG4bK37fe.f05cee0feff15d488a12d3758cece7ae.0;i=baa3 Via: SIP/2.0/TLS 10.2.1.160:58568 ;received=100.100.100.61;rport=48572;branch=z9hG4bKPj472f07568b924214ada83ddfb0fb12b6;alias Max-Forwards: 68 From: 987654321 <sip:987654321@sip.mydomain.com >;tag=73622588a6084d8ba1bca54781e5094d To: <sip:123456789@sip.mydomain.com> Contact: "MyUserNAme" <sip:mycustomerid@10.2.1.160:58568 ;transport=TLS;ob;alias=100.100.100.61~48572~3> Call-ID: 846ffb2f076848c5b8edc876fa1c0d9b CSeq: 14320 INVITE Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, INFO, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS Supported: replaces, 100rel, timer, norefersub Session-Expires: 1800 Min-SE: 90 Content-Type: application/sdp Content-Length: 326 P-Asserted-Identity: <sip:987654321@sip.mydomain.com> v=0 o=- 3841227071 3841227071 IN IP4 50.50.50.183 s=pjmedia b=AS:84 t=0 0 a=X-nat:0 m=audio 29308 RTP/AVP 8 0 101 c=IN IP4 50.50.50.183 b=TIAS:64000 a=ssrc:2024148033 cname:4f2468fd611910fa a=rtpmap:8 PCMA/8000 a=rtpmap:0 PCMU/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=sendrecv a=rtcp:29309 2021/09/21 15:31:11.813534 200.200.200.209:5060 -> 50.50.50.182:32818 SIP/2.0 100 Trying Via: SIP/2.0/TCP 50.50.50.182:5080 ;branch=z9hG4bK37fe.254ecab744d678154779037580c59731.0 Via: SIP/2.0/UDP 50.50.50.210;rport=5060;branch=z9hG4bK37fe.f05cee0feff15d488a12d3758cece7ae.0;i=baa3 Via: SIP/2.0/TLS 10.2.1.160:58568 ;received=100.100.100.61;rport=48572;branch=z9hG4bKPj472f07568b924214ada83ddfb0fb12b6;alias From: 987654321 <sip:987654321@sip.mydomain.com >;tag=73622588a6084d8ba1bca54781e5094d To: <sip:123456789@sip.mydomain.com>;tag=gK0d8c9073 Call-ID: 846ffb2f076848c5b8edc876fa1c0d9b CSeq: 14320 INVITE Content-Length: 0 2021/09/21 15:31:14.442418 200.200.200.209:5060 -> 50.50.50.182:32818 SIP/2.0 183 Session Progress Via: SIP/2.0/TCP 50.50.50.182:5080 ;branch=z9hG4bK37fe.254ecab744d678154779037580c59731.0 Via: SIP/2.0/UDP 50.50.50.210;rport=5060;branch=z9hG4bK37fe.f05cee0feff15d488a12d3758cece7ae.0;i=baa3 Via: SIP/2.0/TLS 10.2.1.160:58568 ;received=100.100.100.61;rport=48572;branch=z9hG4bKPj472f07568b924214ada83ddfb0fb12b6;alias From: 987654321 <sip:987654321@sip.mydomain.com >;tag=73622588a6084d8ba1bca54781e5094d To: <sip:123456789@sip.mydomain.com>;tag=gK0d8c9073 Call-ID: 846ffb2f076848c5b8edc876fa1c0d9b CSeq: 14320 INVITE Record-Route: <sip:50.50.50.182:5080 ;transport=tcp;r2=on;lr=on;ftag=73622588a6084d8ba1bca54781e5094d;did=e8e.c4d1> Record-Route: <sip:50.50.50.182:5060 ;r2=on;lr=on;ftag=73622588a6084d8ba1bca54781e5094d;did=e8e.c4d1> Record-Route: <sip:50.50.50.210:5060 ;r2=on;lr;ftag=73622588a6084d8ba1bca54781e5094d;vsf=AAAAAFpUAgECBwAABnEBB3ZdWEIAQkVFS0BHX2ljZS5ldQ--;vst=AAAAAAAAAAAKCQ8ABAkHCAYKAgdxQFpGbkJCRktDREFYU1AAV0Qw;did=e8e.bb7;nat=yes> Record-Route: <sip:50.50.50.210:5061 ;transport=tls;r2=on;lr;ftag=73622588a6084d8ba1bca54781e5094d;vsf=AAAAAFpUAgECBwAABnEBB3ZdWEIAQkVFS0BHX2ljZS5ldQ--;vst=AAAAAAAAAAAKCQ8ABAkHCAYKAgdxQFpGbkJCRktDREFYU1AAV0Qw;did=e8e.bb7;nat=yes> Contact: <sip:123456789@200.200.200.209:5060> Allow: INVITE,ACK,CANCEL,BYE,INFO,PRACK,UPDATE,OPTIONS Require: 100rel RSeq: 1509 Content-Length: 241 Content-Disposition: session; handling=required Content-Type: application/sdp v=0 o=Sonus_UAC 12038 7929 IN IP4 200.200.200.209 s=SIP Media Capabilities c=IN IP4 200.200.200.212 t=0 0 m=audio 17366 RTP/AVP 8 101 a=rtpmap:8 PCMA/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=sendrecv a=maxptime:20 2021/09/21 15:31:14.443990 50.50.50.182:5060 -> 50.50.50.210:5060 SIP/2.0 183 Session Progress Via: SIP/2.0/UDP 50.50.50.210;rport=5060;branch=z9hG4bK37fe.f05cee0feff15d488a12d3758cece7ae.0;i=baa3 Via: SIP/2.0/TLS 10.2.1.160:58568 ;received=100.100.100.61;rport=48572;branch=z9hG4bKPj472f07568b924214ada83ddfb0fb12b6;alias From: 987654321 <sip:987654321@sip.mydomain.com >;tag=73622588a6084d8ba1bca54781e5094d To: <sip:123456789@sip.mydomain.com>;tag=gK0d8c9073 Call-ID: 846ffb2f076848c5b8edc876fa1c0d9b CSeq: 14320 INVITE Record-Route: <sip:50.50.50.182:5080 ;transport=tcp;r2=on;lr=on;ftag=73622588a6084d8ba1bca54781e5094d;did=e8e.c4d1> Record-Route: <sip:50.50.50.182:5060 ;r2=on;lr=on;ftag=73622588a6084d8ba1bca54781e5094d;did=e8e.c4d1> Record-Route: <sip:50.50.50.210:5060 ;r2=on;lr;ftag=73622588a6084d8ba1bca54781e5094d;vsf=AAAAAFpUAgECBwAABnEBB3ZdWEIAQkVFS0BHX2ljZS5ldQ--;vst=AAAAAAAAAAAKCQ8ABAkHCAYKAgdxQFpGbkJCRktDREFYU1AAV0Qw;did=e8e.bb7;nat=yes> Record-Route: <sip:50.50.50.210:5061 ;transport=tls;r2=on;lr;ftag=73622588a6084d8ba1bca54781e5094d;vsf=AAAAAFpUAgECBwAABnEBB3ZdWEIAQkVFS0BHX2ljZS5ldQ--;vst=AAAAAAAAAAAKCQ8ABAkHCAYKAgdxQFpGbkJCRktDREFYU1AAV0Qw;did=e8e.bb7;nat=yes> Contact: <sip:123456789@200.200.200.209:5060> Allow: INVITE,ACK,CANCEL,BYE,INFO,PRACK,UPDATE,OPTIONS Require: 100rel RSeq: 1509 Content-Length: 253 Content-Disposition: session; handling=required Content-Type: application/sdp v=0 o=Sonus_UAC 12038 7929 IN IP4 50.50.50.183 s=SIP Media Capabilities c=IN IP4 50.50.50.183 t=0 0 m=audio 29320 RTP/AVP 8 101 a=maxptime:20 a=rtpmap:8 PCMA/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=sendrecv a=rtcp:29321 2021/09/21 15:31:14.743211 50.50.50.210:5060 -> 50.50.50.182:5060 PRACK sip:123456789@200.200.200.209:5060 SIP/2.0 Via: SIP/2.0/UDP 50.50.50.210;branch=z9hG4bK47fe.067d9577e9ab3e30e01745a2cf73b7a4.0;i=baa3 Via: SIP/2.0/TLS 10.2.1.160:58568 ;received=100.100.100.61;rport=48572;branch=z9hG4bKPj9ab94c339144428bb7ada63b133f2c12;alias Max-Forwards: 69 From: "MyUserNAme" <sip:987654321@sip.mydomain.com >;tag=73622588a6084d8ba1bca54781e5094d To: <sip:123456789@sip.mydomain.com>;tag=gK0d8c9073 Call-ID: 846ffb2f076848c5b8edc876fa1c0d9b CSeq: 14321 PRACK Route: <sip:50.50.50.182:5060 ;lr;r2=on;ftag=73622588a6084d8ba1bca54781e5094d;did=e8e.c4d1> Route: <sip:50.50.50.182:5080 ;transport=tcp;lr;r2=on;ftag=73622588a6084d8ba1bca54781e5094d;did=e8e.c4d1> RAck: 1509 14320 INVITE Content-Length: 0 2021/09/21 15:31:14.786325 50.50.50.182:5060 -> 200.200.200.209:5060 PRACK sip:123456789transport=tcp@200.200.200.209:5060 SIP/2.0 Via: SIP/2.0/UDP 50.50.50.182;branch=z9hG4bK47fe.3406fe45bb75c3e955b6aa67e53aff58.0 Via: SIP/2.0/UDP 50.50.50.210;rport=5060;branch=z9hG4bK47fe.067d9577e9ab3e30e01745a2cf73b7a4.0;i=baa3 Via: SIP/2.0/TLS 10.2.1.160:58568 ;received=100.100.100.61;rport=48572;branch=z9hG4bKPj9ab94c339144428bb7ada63b133f2c12;alias Max-Forwards: 68 From: "MyUserNAme" <sip:987654321@sip.mydomain.com >;tag=73622588a6084d8ba1bca54781e5094d To: <sip:123456789@sip.mydomain.com>;tag=gK0d8c9073 Call-ID: 846ffb2f076848c5b8edc876fa1c0d9b CSeq: 14321 PRACK RAck: 1509 14320 INVITE Content-Length: 0 2021/09/21 15:31:15.234429 50.50.50.210:5060 -> 50.50.50.182:5060 PRACK sip:123456789@200.200.200.209:5060 SIP/2.0 Via: SIP/2.0/UDP 50.50.50.210;branch=z9hG4bK47fe.067d9577e9ab3e30e01745a2cf73b7a4.0;i=baa3 Via: SIP/2.0/TLS 10.2.1.160:58568 ;received=100.100.100.61;rport=48572;branch=z9hG4bKPj9ab94c339144428bb7ada63b133f2c12;alias Max-Forwards: 69 From: "MyUserNAme" <sip:987654321@sip.mydomain.com >;tag=73622588a6084d8ba1bca54781e5094d To: <sip:123456789@sip.mydomain.com>;tag=gK0d8c9073 Call-ID: 846ffb2f076848c5b8edc876fa1c0d9b CSeq: 14321 PRACK Route: <sip:50.50.50.182:5060 ;lr;r2=on;ftag=73622588a6084d8ba1bca54781e5094d;did=e8e.c4d1> Route: <sip:50.50.50.182:5080 ;transport=tcp;lr;r2=on;ftag=73622588a6084d8ba1bca54781e5094d;did=e8e.c4d1> RAck: 1509 14320 INVITE Content-Length: 0 2021/09/21 15:31:15.280126 50.50.50.182:5060 -> 200.200.200.209:5060 PRACK sip:123456789transport=tcp@200.200.200.209:5060 SIP/2.0 Via: SIP/2.0/UDP 50.50.50.182;branch=z9hG4bK47fe.3406fe45bb75c3e955b6aa67e53aff58.0 Via: SIP/2.0/UDP 50.50.50.210;rport=5060;branch=z9hG4bK47fe.067d9577e9ab3e30e01745a2cf73b7a4.0;i=baa3 Via: SIP/2.0/TLS 10.2.1.160:58568 ;received=100.100.100.61;rport=48572;branch=z9hG4bKPj9ab94c339144428bb7ada63b133f2c12;alias Max-Forwards: 68 From: "MyUserNAme" <sip:987654321@sip.mydomain.com >;tag=73622588a6084d8ba1bca54781e5094d To: <sip:123456789@sip.mydomain.com>;tag=gK0d8c9073 Call-ID: 846ffb2f076848c5b8edc876fa1c0d9b CSeq: 14321 PRACK RAck: 1509 14320 INVITE Content-Length: 0 2021/09/21 15:31:16.234279 50.50.50.210:5060 -> 50.50.50.182:5060 PRACK sip:123456789@200.200.200.209:5060 SIP/2.0 Via: SIP/2.0/UDP 50.50.50.210;branch=z9hG4bK47fe.067d9577e9ab3e30e01745a2cf73b7a4.0;i=baa3 Via: SIP/2.0/TLS 10.2.1.160:58568 ;received=100.100.100.61;rport=48572;branch=z9hG4bKPj9ab94c339144428bb7ada63b133f2c12;alias Max-Forwards: 69 From: "MyUserNAme" <sip:987654321@sip.mydomain.com >;tag=73622588a6084d8ba1bca54781e5094d To: <sip:123456789@sip.mydomain.com>;tag=gK0d8c9073 Call-ID: 846ffb2f076848c5b8edc876fa1c0d9b CSeq: 14321 PRACK Route: <sip:50.50.50.182:5060 ;lr;r2=on;ftag=73622588a6084d8ba1bca54781e5094d;did=e8e.c4d1> Route: <sip:50.50.50.182:5080 ;transport=tcp;lr;r2=on;ftag=73622588a6084d8ba1bca54781e5094d;did=e8e.c4d1> RAck: 1509 14320 INVITE Content-Length: 0 2021/09/21 15:31:16.280111 50.50.50.182:5060 -> 200.200.200.209:5060 PRACK sip:123456789transport=tcp@200.200.200.209:5060 SIP/2.0 Via: SIP/2.0/UDP 50.50.50.182;branch=z9hG4bK47fe.3406fe45bb75c3e955b6aa67e53aff58.0 Via: SIP/2.0/UDP 50.50.50.210;rport=5060;branch=z9hG4bK47fe.067d9577e9ab3e30e01745a2cf73b7a4.0;i=baa3 Via: SIP/2.0/TLS 10.2.1.160:58568 ;received=100.100.100.61;rport=48572;branch=z9hG4bKPj9ab94c339144428bb7ada63b133f2c12;alias Max-Forwards: 68 From: "MyUserNAme" <sip:987654321@sip.mydomain.com >;tag=73622588a6084d8ba1bca54781e5094d To: <sip:123456789@sip.mydomain.com>;tag=gK0d8c9073 Call-ID: 846ffb2f076848c5b8edc876fa1c0d9b CSeq: 14321 PRACK RAck: 1509 14320 INVITE Content-Length: 0 2021/09/21 15:31:18.234281 50.50.50.210:5060 -> 50.50.50.182:5060 PRACK sip:123456789@200.200.200.209:5060 SIP/2.0 Via: SIP/2.0/UDP 50.50.50.210;branch=z9hG4bK47fe.067d9577e9ab3e30e01745a2cf73b7a4.0;i=baa3 Via: SIP/2.0/TLS 10.2.1.160:58568 ;received=100.100.100.61;rport=48572;branch=z9hG4bKPj9ab94c339144428bb7ada63b133f2c12;alias Max-Forwards: 69 From: "MyUserNAme" <sip:987654321@sip.mydomain.com >;tag=73622588a6084d8ba1bca54781e5094d To: <sip:123456789@sip.mydomain.com>;tag=gK0d8c9073 Call-ID: 846ffb2f076848c5b8edc876fa1c0d9b CSeq: 14321 PRACK Route: <sip:50.50.50.182:5060 ;lr;r2=on;ftag=73622588a6084d8ba1bca54781e5094d;did=e8e.c4d1> Route: <sip:50.50.50.182:5080 ;transport=tcp;lr;r2=on;ftag=73622588a6084d8ba1bca54781e5094d;did=e8e.c4d1> RAck: 1509 14320 INVITE Content-Length: 0 Any help will be much appreciated. Kind regards, Angelo [View Less]

2 7

Releasing Kamailio 5.3.9
by Henning Westerholt 23 Sep '21

23 Sep '21

Hello, I am planning to release in two weeks (likely on Wednesday 7th October) the next minor version out of branch 5.3, version 5.3.9. Backports of fixed issues from other stable branches will be integrated as usual. If you are aware of new issues which were not yet reported on the issue tracker or are missing back-ports, report them. Please note that this will be the last minor release created from the 5.3.x stable branch. The stable branches are usually maintained from the Kamailio … [View More]

1 0

Kamailio v5.4.7 Released
by Daniel-Constantin Mierla 22 Sep '21

22 Sep '21

Hello, Kamailio SIP Server v5.4.7 stable release is out. This is a maintenance release of the latest stable branch, 5.4, that includes fixes since the release of v5.4.6. There is no change to database schema or configuration language structure that you have to do on previous installations of v5.4.x. Deployments running previous v5.4.x versions are strongly recommended to be upgraded to v5.4.7. Note that 5.4 is the second last stable branch, still officially maintained by Kamailio development … [View More]

1 0

Add a new trunk
by sondes boughdiri 22 Sep '21

22 Sep '21

Good morning , I have a question , how to add a trunk from operators in kamailio. Best regards .

1 0

Re: [SR-Users] How to get $fU and $tU from MSRP module?
by Henning Westerholt 22 Sep '21

22 Sep '21

(please keep the list in CC) Hello, I see – its kind of pseudo-SIP message that is presented in the cfg in this route. And it seems that you want to access the cpim body. You already checked that the $msrp(crhop), $msrp(nexthop) and $msrp(prevop) etc.. are not working for you? It’s probably not the best way, but what about using $msrp(body) to get the body and then using a regular expression (like a transformation) on this to get the From/To? Cheers, Henning -- Henning Westerholt – https:/… [View More]/skalatan.de/blog/ Kamailio services – https://gilawa.com<https://gilawa.com/> From: BOEINGNG <lihang567890(a)126.com> Sent: Wednesday, September 22, 2021 2:41 AM To: Henning Westerholt <hw(a)skalatan.de> Subject: Re: [SR-Users] How to get $fU and $tU from MSRP module? Yes, I logged, but only got <null> for both $fU and $tU. 2021年9月20日下午4:03，Henning Westerholt <hw(a)skalatan.de<mailto:hw@skalatan.de>> 写道： Hello, I am not that familiar with the MSRP module, but have you tried to just log/access the $fU and $tU in the event_route[msrp:frame-in]? Cheers, Henning -- Henning Westerholt – https://skalatan.de/blog/ Kamailio services – https://gilawa.com<https://gilawa.com/> From: sr-users <sr-users-bounces(a)lists.kamailio.org<mailto:sr-users-bounces@lists.kamailio.org>> On Behalf Of BOEINGNG Sent: Friday, September 17, 2021 10:57 AM To: sr-users(a)lists.kamailio.org<mailto:sr-users@lists.kamailio.org> Subject: [SR-Users] How to get $fU and $tU from MSRP module? Hello! I want to get $fU and $tU from event_route[msrp:frame-in] in order to filter out MSRP messages sent by a specific sender and received by a specific receiver, I know I can get message content from $msrp(buf), the message content is like this: MSRP 7a57f552155926c0 SEND To-Path: msrp://172.18.0.14:6060/9d8da4a34dc2102959e7;tcp msrp://172.18.0.12:5060/msrp-6142fc2b-84-1;tcp msrp://172.18.0.2:34862/2a67b54ae0750b7d82aa;tcp From-Path: msrp://172.18.0.14:6060/c71ae3675e114d08216b;tcp msrp://172.18.0.12:5060/msrp-6142fc2b-83-1;tcp msrp://172.18.0.2:34858/8baea7c52ba8755322fd;tcp Byte-Range: 1-197/197 Failure-Report: yes Success-Report: yes Message-ID: c792c94039b8a969 Content-Type: message/cpim From: sip:alice@ims.mnc001.mcc001.3gppnetwork.org To: sip:bob@ims.mnc001.mcc001.3gppnetwork.org DateTime: 2021-09-16T09:23:49.339805+00:00 MIME-Version: 1.0 Content-Type: text/plain hello -------7a57f552155926c0$ I want to get alice and bob from the content below： From: sip:alice@ims.mnc001.mcc001.3gppnetwork.org To: sip:bob@ims.mnc001.mcc001.3gppnetwork.org DateTime: 2021-09-16T09:23:49.339805+00:00 someone can suggest some method. In other route like request_route we can use $fU and $tU to access them. Regrads HANG LI [View Less]

1 0

Unable to pull enviornment variables
by Adarsh Chauhan 22 Sep '21

22 Sep '21

Hi Team, Need some help here. Want to pull environment variable however kamailio just doesnt pick it. I exported the environment variable *export STAGE="dev"* Then i tried following 1) *#!defenv DEVSTAGE* gives error 0(3809) ERROR: <core> [core/cfg.lex:2085]: pp_define_env(): env variable not defined [DEVSTAGE] 2) *#!substdef "/DEVSTAGE/$env(DEVSTAGE)/";* 0(3962) DEBUG: <core> [core/ppcfg.c:87]: pp_subst_add(): ### added subst expression: [/DEVSTAGE/$env(DEVSTAGE)/] 0(3962) … [View More]

3 4

Releasing Kamailio v.5.4.7
by Daniel-Constantin Mierla 22 Sep '21

22 Sep '21

Hello, I am planning to release a new version from branch 5.4, respectively 5.4.7, sometime next week, likely on Wednesday, Sep 22, 2021. If anyone is aware of issues not yet reported to bug tracker or missing backports, report them in order to try to get the fixes in this release. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda

1 1

JSONRPC ERROR in siremis GUI.
by 岩間理佐 22 Sep '21

22 Sep '21

Hi, I have a question regarding the jsonRPC commands in the siremis GUI. 【Environment】・Centos7 ・Kamailio 5.5.2 ・siremis 5.3 (installed by git clone https://github.com/asipto/siremis siremis-5.3.x) ・php php-mysqlnd-7.1.33-16.el7.remi.x86_64 php-json-7.1.33-16.el7.remi.x86_64 php-mbstring-7.1.33-16.el7.remi.x86_64 php-pdo-7.1.33-16.el7.remi.x86_64 php-gd-7.1.33-16.el7.remi.x86_64 php-xml-7.1.33-16.el7.remi.x86_64 php-pecl-zip-1.19.4-1.el7.remi.7.1.x86_64 php-xmlrpc-7.1.33-16.el7.remi.x86_64 … [View More]

2 1

Question regarding parser error for REGISTER request
by Floimair Florian 20 Sep '21

20 Sep '21

Hello List! We have a certain user agent that somehow triggers a parser error log entry, everytime this type of user agent registers. Sep 20 12:03:49 kamailio-dev-1 /usr/sbin/kamailio[1803]: ERROR: <core> [core/parser/parse_param.c:517]: parse_param2(): Invalid character, ; expected The odd thing now is that this register still succeeds. And we do not see that error for other methods like e.g. INVITE. The user agent in question is an Android app based on linphone which we develop … [View More]

2 1

Question on the SL Module
by Alessio Garzi 20 Sep '21

20 Sep '21

Hello Kama ML, today I stumbled on function "update_sl_stats()" inside sl_stats.c and noticed that some response codes are treated differently. For example here: https://github.com/kamailio/kamailio/blob/a9ef78b7f43616f2ceaa26df97eff68eb… since we have a "break;" statement, when a 500 code is received, the 5XX counter is not incremented even if a 500 code belongs to the 5XX family. We have the same behaviour for other response codes and it really seems that it's not a bug and the … [View More]

2 1

Kamilio Presence
by Jerry Kendall 20 Sep '21

20 Sep '21

Hey Bill, Just checking to see if you managed to get the BLFs to work on the Yealinks... I've Grandstream/Yealink/Polycom devices and can't get BLFs to work - the NOTIFY is not being sent. regards, Jerry __________________________________________________________ Kamailio - Users Mailing List - Non Commercial Discussions * sr-users(a)lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe: * https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

2 2

Kamailio - FreeSWITCH - RTPproxy
by Jerry Kendall 20 Sep '21

20 Sep '21

Hello all, I am new to the list but have been reading plenty. Loads of good tips and help. I am playing with Freeswitch and would like to put Kamailio/RTPProxy in front for the user endpoints. Freeswitch will talk directly with the service provider. I am wondering *if* i can do this... 1) have the endpoints register with kamailio 2) have the media proxy via RTPProxy as it is needed for NAT 3) have the actual work (voicemail/ring groups/ivr/conference/etc...) done on Freeswitch 4) have all … [View More]

3 3

How to get $fU and $tU from MSRP module?
by BOEINGNG 20 Sep '21

20 Sep '21

Hello! I want to get $fU and $tU from event_route[msrp:frame-in] in order to filter out MSRP messages sent by a specific sender and received by a specific receiver, I know I can get message content from $msrp(buf), the message content is like this: MSRP 7a57f552155926c0 SEND To-Path: msrp://172.18.0.14:6060/9d8da4a34dc2102959e7;tcp msrp://172.18.0.12:5060/msrp-6142fc2b-84-1;tcp msrp://172.18.0.2:34862/2a67b54ae0750b7d82aa;tcp From-Path: msrp://172.18.0.14:6060/c71ae3675e114d08216b;tcp msrp://… [View More]

2 1

Reinite breaks the call
by Angelo Sipper 20 Sep '21

20 Sep '21

Hello, I am trying to understand a problem we have with reinvites. When there is a reinvite on the call our provider refuses to receive the reinvite and the call is dropped. The setup is the bellow: UA-> Kamailio1 -> Kamailio2 -> Provider On Kamailio2 we have Topos enabled. Looking on the trace I can see that on the second invite, Kamailio does send out the original contact and not the one that was originally send out to the provider. Is this correct? Is this breaking the call? … [View More]Bellow the trace and the flow from Kamailio2 until the second reinvite. All reinvites are the same as per the last Thank you for your help! 2021/09/15 16:29:59.420162 50.50.50.181:5060 -> 200.200.200.193:5060 INVITE sip:1234567890@sip.mydomain.com:5060 SIP/2.0 Via: SIP/2.0/UDP 50.50.50.181;branch=z9hG4bK3db6.b5141bfea33b57c5223aff14ab3b5466.0 Max-Forwards: 67 From: 987654321 <sip:987654321@sip.mydomain.com>;tag=2QK2mpeH5Sy4g To: <sip:1234567890@sip.mydomain.com> Call-ID: dfb297d1-90cb-123a-d4a1-00155d01bf11 CSeq: 41302510 INVITE Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER, REFER, NOTIFY, PUBLISH, SUBSCRIBE Supported: timer, path, replaces Allow-Events: talk, hold, conference, presence, as-feature-event, dialog, line-seize, call-info, sla, include-session-description, presence.winfo, message-summary, refer Content-Type: application/sdp Content-Disposition: session Content-Length: 481 Contact: <sip:btpsh-b5-6141f513-11f69-4@50.50.50.181> v=0 o=FreeSWITCH 1631683257 1631683258 IN IP4 50.50.50.183 s=FreeSWITCH c=IN IP4 50.50.50.183 t=0 0 m=audio 26472 RTP/AVP 8 0 18 101 a=rtpmap:8 PCMA/8000 a=rtpmap:0 PCMU/8000 a=rtpmap:18 G729/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=sendrecv a=rtcp:26473 a=ptime:20 m=video 26510 RTP/AVP 103 b=AS:1024 a=rtpmap:103 H264/90000 a=rtcp-fb:103 ccm fir a=rtcp-fb:103 ccm tmmbr a=rtcp-fb:103 nack a=rtcp-fb:103 nack pli a=sendrecv a=rtcp:26511 ====================================================================================== 2021/09/15 16:29:59.439009 200.200.200.193:5060 -> 50.50.50.181:5060 SIP/2.0 100 Trying Via: SIP/2.0/UDP 50.50.50.181;branch=z9hG4bK3db6.b5141bfea33b57c5223aff14ab3b5466.0 From: 987654321 <sip:987654321@sip.mydomain.com>;tag=2QK2mpeH5Sy4g To: <sip:1234567890@sip.mydomain.com>;tag=gK0dc15c15 Call-ID: dfb297d1-90cb-123a-d4a1-00155d01bf11 CSeq: 41302510 INVITE Content-Length: 0 ====================================================================================== 2021/09/15 16:30:02.596613 200.200.200.193:5060 -> 50.50.50.181:5060 SIP/2.0 183 Session Progress Via: SIP/2.0/UDP 50.50.50.181;branch=z9hG4bK3db6.b5141bfea33b57c5223aff14ab3b5466.0 From: 987654321 <sip:987654321@sip.mydomain.com>;tag=2QK2mpeH5Sy4g To: <sip:1234567890@sip.mydomain.com>;tag=gK0dc15c15 Call-ID: dfb297d1-90cb-123a-d4a1-00155d01bf11 CSeq: 41302510 INVITE Contact: <sip:1234567890@200.200.200.193:5060> Allow: INVITE,ACK,CANCEL,BYE,INFO,PRACK,UPDATE,OPTIONS Content-Length: 313 Content-Disposition: session; handling=required Content-Type: application/sdp v=0 o=Sonus_UAC 27823 25478 IN IP4 200.200.200.193 s=SIP Media Capabilities c=IN IP4 200.200.200.196 t=0 0 m=audio 19958 RTP/AVP 8 101 a=rtpmap:8 PCMA/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=sendrecv a=maxptime:20 m=video 0 RTP/AVP 103 b=AS:1024 a=rtpmap:103 H264/90000 a=inactive ====================================================================================== 2021/09/15 16:30:06.163783 200.200.200.193:5060 -> 50.50.50.181:5060 SIP/2.0 200 OK Via: SIP/2.0/UDP 50.50.50.181;branch=z9hG4bK3db6.b5141bfea33b57c5223aff14ab3b5466.0 From: 987654321 <sip:987654321@sip.mydomain.com>;tag=2QK2mpeH5Sy4g To: <sip:1234567890@sip.mydomain.com>;tag=gK0dc15c15 Call-ID: dfb297d1-90cb-123a-d4a1-00155d01bf11 CSeq: 41302510 INVITE Accept: application/sdp, application/isup, application/dtmf, application/dtmf-relay, multipart/mixed Contact: <sip:1234567890@200.200.200.193:5060> Allow: INVITE,ACK,CANCEL,BYE,INFO,PRACK,UPDATE,OPTIONS P-Asserted-Identity: <sip:6979111336@MOBILE.MOBILEPROVIDER.COM;user=phone> Require: timer Supported: timer Session-Expires: 300;refresher=uac Content-Length: 313 Content-Disposition: session; handling=required Content-Type: application/sdp v=0 o=Sonus_UAC 27823 25478 IN IP4 200.200.200.193 s=SIP Media Capabilities c=IN IP4 200.200.200.196 t=0 0 m=audio 19958 RTP/AVP 8 101 a=rtpmap:8 PCMA/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=sendrecv a=maxptime:20 m=video 0 RTP/AVP 103 b=AS:1024 a=rtpmap:103 H264/90000 a=inactive ====================================================================================== 2021/09/15 16:30:06.405147 50.50.50.181:5060 -> 200.200.200.193:5060 ACK sip:1234567890@200.200.200.193:5060 SIP/2.0 Via: SIP/2.0/UDP 50.50.50.181;branch=z9hG4bK3db6.58e9d8820221b191b49fe0c91299e56f.0 Max-Forwards: 68 From: "987654321" <sip:987654321@sip.mydomain.com>;tag=2QK2mpeH5Sy4g To: <sip:1234567890@sip.mydomain.com>;tag=gK0dc15c15 Call-ID: dfb297d1-90cb-123a-d4a1-00155d01bf11 CSeq: 41302510 ACK Proxy-Authorization: Digest username="mycustomerid", realm=" sbc1.mydomain.com", nonce="YUH2g2FB9VcCxZ3l2WSvJCj7aUokLhAKksYQ1zfOfyQRWm90h2vJgH8I/B+A", algorithm=MD5, uri="sip:1234567890@sbc1.mydomain.com", response="dc4d3d7e9281c04ecc3e3 63ea162fb" Content-Length: 0 Contact: <sip:btpsh-b5-6141f513-11f69-4@50.50.50.181> ============================================= 2021/09/15 16:32:37.685497 50.50.50.181:5060 -> 200.200.200.193:5060 INVITE sip:1234567890@200.200.200.193:5060 SIP/2.0 Via: SIP/2.0/UDP 50.50.50.181;branch=z9hG4bK4db6.691137b194a14953af928c339e03d60e.0 Via: SIP/2.0/UDP 50.50.50.210;rport=5060;branch=z9hG4bK4db6.4619cd1b550ba7e45a3fbd0321a5c0b0.0 Via: SIP/2.0/UDP 62.1.2.62;received=62.1.2.62;rport=5060;branch=z9hG4bKXDZQF19XUj3QB Max-Forwards: 67 From: "987654321" <sip:987654321@sip.mydomain.com>;tag=2QK2mpeH5Sy4g To: <sip:1234567890@sip.mydomain.com>;tag=gK0dc15c15 Call-ID: dfb297d1-90cb-123a-d4a1-00155d01bf11 CSeq: 41302511 INVITE Contact: <sip:mycustomerid@62.1.2.62:5060 ;transport=udp;gw=1606bb6a-6563-43be-b4dd-4890d524d0e9> User-Agent: Supervoice VPBX Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER, REFER, NOTIFY, PUBLISH, SUBSCRIBE Supported: timer, path, replaces Proxy-Authorization: Digest username="mycustomerid", realm=" sbc1.mydomain.com", nonce="YUH2g2FB9VcCxZ3l2WSvJCj7aUokLhAKksYQ1zfOfyQRWm90h2vJgH8I/B+A", algorithm=MD5, uri="sip:atpsh-b5-6141f513-11f69-4@50.50.50.181", response="50ed75ca9002 ca76fbfa306fb8a599" Session-Expires: 300;refresher=uac Min-SE: 120 Content-Type: application/sdp Content-Disposition: session Content-Length: 348 Remote-Party-ID: "987654321" <sip:987654321@sbc1.mydomain.com >;party=calling;screen=yes;privacy=off v=0 o=FreeSWITCH 1631683257 1631683258 IN IP4 50.50.50.183 s=FreeSWITCH c=IN IP4 50.50.50.183 t=0 0 m=audio 26472 RTP/AVP 8 0 18 101 a=rtpmap:8 PCMA/8000 a=rtpmap:0 PCMU/8000 a=rtpmap:18 G729/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=sendrecv a=rtcp:26473 a=ptime:20 m=video 0 RTP/AVP 103 a=rtpmap:103 H264/90000 |Time | 50.50.50.210 | 200.200.200.193 | | | | 50.50.50.181 | |0.000024 | INVITE SDP (g711A g7 | |SIP INVITE From: 1234567890 <sip:1234567890@sip.mydomain.com> To:< sip:987654321@sip.mydomain.com> Call-ID:dfb297d1-90cb-123a-d4a1-00155d01bf11 CSeq:41302510 | |(5060) ------------------> (5060) | | |0.001523 | 100 trying -- your c | |SIP Status 100 trying -- your call is important to us | |(5060) <------------------ (5060) | | |0.011760 | | INVITE SDP (g711A g7 |SIP INVITE From: 1234567890 <sip:1234567890@sip.mydomain.com> To:< sip:987654321@sip.mydomain.com> CSeq:41302510 | | |(5060) ------------------> (5060) | |0.030607 | | 100 Trying| |SIP Status 100 Trying | | |(5060) <------------------ (5060) | |2.690501 | | 183 Session Progress |SIP Status 183 Session Progress | | |(5060) <------------------ (5060) | |2.708868 | 183 Session Progress | |SIP Status 183 Session Progress | |(5060) <------------------ (5060) | | |3.188211 | | 183 Session Progress |SIP Status 183 Session Progress | | |(5060) <------------------ (5060) | |3.199099 | 183 Session Progress | |SIP Status 183 Session Progress | |(5060) <------------------ (5060) | | |6.755381 | | 200 OK SDP (g711A te |SIP Status 200 OK | | |(5060) <------------------ (5060) | |6.819017 | 200 OK SDP (g711A te | |SIP Status 200 OK | |(5060) <------------------ (5060) | | |6.973845 | ACK | | |SIP Request INVITE ACK 200 CSeq:41302510 | |(5060) ------------------> (5060) | | |6.996745 | | ACK | |SIP ACK From: 1234567890 <sip:1234567890@sip.mydomain.com> To:< sip:987654321@sip.mydomain.com> CSeq:41302510 | | |(5060) ------------------> (5060) | |158.269723| INVITE SDP (g711A g7 | |SIP INVITE From: 1234567890 <sip:1234567890@sip.mydomain.com> To:< sip:987654321@sip.mydomain.com> Call-ID:dfb297d1-90cb-123a-d4a1-00155d01bf11 CSeq:41302511 | |(5060) ------------------> (5060) | | |158.275396| 100 trying -- your c | |SIP Status 100 trying -- your call is important to us | |(5060) <------------------ (5060) | | |158.277105| | INVITE SDP (g711A g7 |SIP INVITE From: 1234567890 <sip:1234567890@sip.mydomain.com> To:< sip:987654321@sip.mydomain.com> CSeq:41302511 | | |(5060) ------------------> (5060) | |158.753781| | INVITE SDP (g711A g7 |SIP INVITE From: 1234567890 <sip:1234567890@sip.mydomain.com> To:< sip:987654321@sip.mydomain.com> CSeq:41302511 | | |(5060) ------------------> (5060) | |159.753493| | INVITE SDP (g711A g7 |SIP INVITE From: 1234567890 <sip:1234567890@sip.mydomain.com> To:< sip:987654321@sip.mydomain.com> CSeq:41302511 | | |(5060) ------------------> (5060) | |161.753502| | INVITE SDP (g711A g7 |SIP INVITE From: 1234567890 <sip:1234567890@sip.mydomain.com> To:< sip:987654321@sip.mydomain.com> CSeq:41302511 | | |(5060) ------------------> (5060) | |165.753630| | INVITE SDP (g711A g7 |SIP INVITE From: 1234567890 <sip:1234567890@sip.mydomain.com> To:< sip:987654321@sip.mydomain.com> CSeq:41302511 | | |(5060) ------------------> (5060) | |169.754980| | INVITE SDP (g711A g7 |SIP INVITE From: 1234567890 <sip:1234567890@sip.mydomain.com> To:< sip:987654321@sip.mydomain.com> CSeq:41302511 | | |(5060) ------------------> (5060) | |173.753719| | INVITE SDP (g711A g7 |SIP INVITE From: 1234567890 <sip:1234567890@sip.mydomain.com> To:< sip:987654321@sip.mydomain.com> CSeq:41302511 | | |(5060) ------------------> (5060) | |177.753676| | INVITE SDP (g711A g7 |SIP INVITE From: 1234567890 <sip:1234567890@sip.mydomain.com> To:< sip:987654321@sip.mydomain.com> CSeq:41302511 | | |(5060) ------------------> (5060) | |181.753657| | INVITE SDP (g711A g7 |SIP INVITE From: 1234567890 <sip:1234567890@sip.mydomain.com> To:< sip:987654321@sip.mydomain.com> CSeq:41302511 | | |(5060) ------------------> (5060) | |185.753503| | INVITE SDP (g711A g7 |SIP INVITE From: 1234567890 <sip:1234567890@sip.mydomain.com> To:< sip:987654321@sip.mydomain.com> CSeq:41302511 | | |(5060) ------------------> (5060) | |188.254337| 503 Service not avai | |SIP Status 503 Service not available | |(5060) <------------------ (5060) | | |188.255085| ACK | | |SIP Request INVITE ACK 200 CSeq:41302511 | |(5060) ------------------> (5060) | | |188.326552| BYE | | |SIP Request BYE CSeq:41302512 | |(5060) ------------------> (5060) | | |188.342106| | BYE | |SIP Request BYE CSeq:41302512 | | |(5060) ------------------> (5060) | |188.373697| | 200 OK | |SIP Status 200 OK | | |(5060) <------------------ (5060) | |188.379670| 200 OK | | |SIP Status 200 OK | |(5060) <------------------ (5060) | | Kind Regards, Angelo [View Less]

4 4

Re: [SR-Users] Error in ul_insert_ucontact() function of usrloc module
by hamed r 20 Sep '21

20 Sep '21

hello Ben I was using development functions and the C code of this function did not exist. I needed to manually add a contact to kamailio but this does not work and I used the HTable module to solve the problem. Thanks for the tips

1 0

Slack channel
by Sergio Carvalho 20 Sep '21

20 Sep '21

Hi everyone, How can I join the Kamailio slack channel? Is it open to the community? Best regards, Sergio Carvalho

3 2

Error in ul_insert_ucontact() function of usrloc module
by hamed r 18 Sep '21

18 Sep '21

The user is not added using the ul_insert_ucontact() function : ul_insert_ucontact("sip:900@192.168.51.138:1234", "< sip:900@192.168.51.138:1234>", "303", -1, "a2ecd821d4464d75851b73c35442b6ad", 2222, "0", "1", "MicroSIP/3.20.6", "udp: 192.168.51.106:5060"); And the following error is displayed in the syslog: Sep 18 14:36:48 srv139937 kamailio: CRITICAL: <core> [core/cfg.y:3686]: yyerror_at(): parse error in config file /usr/local/etc/kamailio//kamailio.cfg, line 838, column 148: … [View More]

2 1

Re: [SR-Users] problem with LRKProxy module
by hamed r 18 Sep '21

18 Sep '21

Thanks Mojtaba, problem was solved. I performed LRKProxy first, then Kamailio.

1 0

BLF when phone boots up
by Jerry Kendall 17 Sep '21

17 Sep '21

Hi, I have looked at lots of postings but can't seem to find the answer I seek. I have 6 phones (Grandstream GXP2170, etc) connected to Kamailio 5.2.1 running default config file with changes per https://kb.asipto.com/kamailio:presence:k43-blf On x301, I have the 3 BLFs setup to monitor x302, x303 and x304. If I dial 303 from 301, the BLFs work (flash, red, then green) as expected. But, when the phone initially boots up, the BLFs are all dead - until the first PUBLISH event. So, the … [View More]

1 0

listen directive during runtime
by Tihomir Culjaga 17 Sep '21

17 Sep '21

Hi, is it possible to add a listen directive during kamailio runtime ? The reason I'm asking this is in a situation when I add a new peering trunk (from a different network segment), I need to add a network interface to the kamailio server and then add a specific listen directive for that interface to reference the socket by name. listen=udp:10.1.1.11 name "mySN1" so i can further reference to a specific socket name when routing SIP messages. Please advise, Regards, Tihomir.

2 1

Re: [SR-Users] DMQ module issues
by Zé Santos 17 Sep '21

17 Sep '21

I don't think you understood. The issue is in v5.2.5, and I tried to update kamailio but it still remains. I honestly think this is a machine problem, since I can't even send the notifications to 0.0.0.0:5090. It is very weird. Best Regards, José Santos

2 3

xmlrpc always returns NO RESULT
by 岩間理佐 17 Sep '21

17 Sep '21

Hi, I have a question regarding the XMLRPC commands in the siremis GUI. 【Environment】・Centos7 ・kamailio 5.5.2 ・siremis 5.3 （installed by git clone https://github.com/asipto/siremis siremis-5.3.x）・php: $ rpm -qa | grep php php-process-5.4.16-48.el7.x86_64 php-common-5.4.16-48.el7.x86_64 php-mysqlnd-5.4.16-48.el7.x86_64 php-pdo-5.4.16-48.el7.x86_64 php-xml-5.4.16-48.el7.x86_64 php-cli-5.4.16-48.el7.x86_64 php-5.4.16-48.el7.x86_64 php-pear-1.9.4-22.el7.noarch ・apache 2.4.6 … [View More]When I execute commands in command service → XMLPRC from siremis GUI, it always shows no result. It looks like the command is not being executed. I also executed these commands on server, and there are no problem. There is no error in apache log and kamailio is also working. This is what I have in /etc/kamailio/kamailio.cfg #!KAMAILIO #!define WITH_XMLRPC #!define WITH_DEBUG #!define DBURL "mysql://kamailio:kamailiorw@localhost/kamailio" # - flags #FLT_ - per transaction (message) flags #FLB_ - per branch flags #!define FLT_ACC 1 #!define FLT_ACCMISSED 2 #!define FLT_ACCFAILED 3 #!define WITH_MYSQL #!define WITH_NAT ####### Global Parameters ######### #!ifdef WITH_DEBUG debug=4 log_stderror=yes #!else debug=2 log_stderror=no #!endif #!ifdef WITH_MYSQL loadmodule "db_mysql.so" #!endif #!ifdef WITH_NAT loadmodule "nathelper.so" #!ifdef WITH_RTPENGINE loadmodule "rtpengine.so" #!else loadmodule "rtpproxy.so" #!endif #!endif #!ifdef WITH_JSONRPC loadmodule "xhttp.so" #!endif memdbg=5 memlog=5 log_facility=LOG_LOCAL0 fork=yes children=4 disable_tcp=yes auto_aliases=no port=5060 listen=udp:172.23.0.246:5060 advertise 52.69.75.254:5060 sip_warning=no ####### Modules Section ######## # set module path #mpath="/usr/local/lib/kamailio/modules/" #loadmodule "db_mysql.so" loadmodule "tm.so" loadmodule "tmx.so" loadmodule "sl.so" loadmodule "rr.so" loadmodule "pv.so" loadmodule "maxfwd.so" loadmodule "textops.so" loadmodule "siputils.so" loadmodule "xlog.so" loadmodule "sanity.so" loadmodule "ctl.so" loadmodule "acc.so" loadmodule "dispatcher.so" loadmodule "uac.so" loadmodule "sqlops" loadmodule "rtimer" loadmodule "jsonrpcs.so" loadmodule "kex.so" loadmodule "corex.so" # ----- jsonrpcs params ----- modparam("jsonrpcs", "pretty_format", 1) modparam("jsonrpcs", "dgram_socket", "/var/run/kamailio/kamailio_rpc.sock") modparam("jsonrpcs", "dgram_mode", 0666) modparam("jsonrpcs", "dgram_user", "kamailio") modparam("jsonrpcs", "dgram_group", "kamailio") modparam("jsonrpcs", "transport", 0) # ----- xmlrpc params ----- #modparam("xmlrpc", "route", "XMLRPC") #modparam("xmlrpc", "url_match", "^/RPC") # ----- rr params ----- modparam("rr", "append_fromtag", 1) # ----- R Timer ----- modparam("rtimer", "timer", "name=cdr;interval=300;mode=1;") modparam("rtimer", "exec", "timer=cdr;route=CDRS") # ----- acc params ----- modparam("acc", "log_flag", FLT_ACC) modparam("acc", "failed_transaction_flag", FLT_ACCFAILED) modparam("acc", "log_extra", "src_user=$fU;src_domain=$fd;dst_ouser=$tU;dst_user=$rU;dst_domain=$rd;src_ip=$si") # ----- tm params ----- modparam("tm", "fr_timer", 2000) modparam("tm", "fr_inv_timer", 40000) modparam("tm", "auto_inv_100_reason", "Trying") # ----- dispatcher params ----- modparam("dispatcher", "db_url", DBURL) modparam("dispatcher", "table_name", "dispatcher") modparam("dispatcher", "flags", 2) modparam("dispatcher", "xavp_dst", "_dsdst_") modparam("dispatcher", "xavp_ctx", "_dsctx_") modparam("dispatcher", "ds_ping_from", "sip:proxy@52.69.75.254") modparam("dispatcher", "ds_ping_interval", 60) modparam("dispatcher", "ds_probing_mode", 1) modparam("dispatcher", "ds_timer_mode", 1) modparam("dispatcher", "xavp_dst_mode", 0) modparam("dispatcher", "ds_ping_latency_stats", 1) modparam("dispatcher", "ds_ping_method", "OPTIONS") modparam("dispatcher", "ds_probing_threshold", 10) modparam("dispatcher", "ds_inactive_threshold", 10) modparam("dispatcher", "ds_ping_reply_codes","class=2;code=403;code=404;code=484;class=3") # ----- uac params ----- modparam("uac", "reg_db_url", DBURL) modparam("uac", "reg_contact_addr", "52.69.75.254") modparam("uac", "reg_db_table", "uacreg") # ----- mysql ----- modparam("sqlops", "sqlcon","cb=>mysql://kamailio:kamailiorw@localhost/kamailio") ####### Routing Logic ######## # main request routing logic request_route { # per request initial checks route(REQINIT); # 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) # 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 } # 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 route(DISPATCH); } route[RELAY] { if (!t_relay()) { sl_reply_error(); } exit; } # Per SIP request initial checks route[REQINIT] { if (!mf_process_maxfwd_header("10")) { sl_send_reply("483","Too Many Hops"); exit; } if(!sanity_check("1511", "7")) { xlog("Malformed SIP message from $si:$sp\n"); exit; } } # Handle requests within SIP dialogs route[WITHINDLG] { if (!has_totag()) { return; } # sequential request withing a dialog should # take the path determined by record-routing if (loose_route()) { if (is_method("BYE")) { setflag(FLT_ACC); # do accounting ... setflag(FLT_ACCFAILED); # ... even if the transaction fails } route(RELAY); } if (is_method("SUBSCRIBE") && uri == myself) { # in-dialog subscribe requests route(PRESENCE); } if ( is_method("ACK") ) { if ( t_check_trans() ) { t_relay(); exit; } else { exit; } } sl_send_reply("404","Not here"); exit; } # Handle SIP registrations route[REGISTRAR] { if(!is_method("REGISTER")) return; sl_send_reply("404", "No registrar"); exit; } # Presence server route route[PRESENCE] { if(!is_method("PUBLISH|SUBSCRIBE")) return; sl_send_reply("404", "Not here"); exit; } # Dispatch requests route[DISPATCH] { # round robin dispatching on gateways group '1' if(!ds_select_dst("1", "11")) { send_reply("404", "No destination"); exit; } xdbg("--- SCRIPT: going to <$ru> via <$du> (attrs: $xavp(_dsdst_=>attrs))\n"); t_on_failure("RTF_DISPATCH"); route(RELAY); exit; } # Try next destionations in failure route failure_route[RTF_DISPATCH] { if (t_is_canceled()) { exit; } # next DST - only for 500 or local timeout if (t_check_status("500|486") or (t_branch_timeout() and !t_branch_replied())) { if(ds_next_dst()) { xdbg("--- SCRIPT: retrying to <$ru> via <$du> (attrs: $xavp(_dsdst_=>attrs))\n"); t_on_failure("RTF_DISPATCH"); route(RELAY); exit; } } } I have tried my best to do some researches about it, but still stuck. Any help is appreciated. Thank you! [View Less]

2 1

problem with LRKProxy module
by hamed r 16 Sep '21

16 Sep '21

Hello I have problem with lrkproxy module. First, I installed the packages from the link below : https://github.com/mojtabaesfandiari/pylrkproxy And the service was properly listened to the local ip (192.168.51.106:22333 ). In the next step, the parameters were added to the kamalio.cfg file : loadmodule "lrkproxy.so" modparam("lrkproxy", "lrkproxy_sock", "udp:192.168.51.106:22333") I also changed the /etc/pylrkproxy/pylrkproxy.ini to set local ip. But when I make a call, the ip inside the … [View More]

2 1

DMQ module issues
by Zé Santos 16 Sep '21

16 Sep '21

Hi guys, I am currently using kamailio v5.2.5 and running it inside a container. I already attempted to upgrade the kamailio to the latest version however the problem persists. This is the core dump that I got from using gdb: Core was generated by `/usr/sbin/kamailio -f > /etc/kazoo/kamailio/kamailio.cfg -m 512 -M 64 -x tlsf -w'. > Program terminated with signal 11, Segmentation fault. > #0 0x000000000071c63c in select_cfg_var (res=0x7ffd57d49b10, > s=0x7f2649395040, msg=… [View More]

3 3

Best practice for Kamailio "cluster" front for many TLS connections
by Angelo Sipper 15 Sep '21

15 Sep '21

Hello, We are thinking to use kamailio to fully support our current voip service. I would like to know what is the best practice to use kamailio for several thousands for clients that connect to us via TLS. We would like to have a front "cluster" to be able to handle all these connections in balanced way. All clients register to us and the do calls that we statefully forward to the provider. On our test we have already created a single kamailio that successfully accepts and handles … [View More]

7 12

Fwd: Catching an overall timeout after dropping replies
by Marrold 15 Sep '21

15 Sep '21

Hi, This is partially related to a previous thread - https://lists.kamailio.org/pipermail/sr-users/2021-August/113128.html We are using the TSILO module to suspend transactions whilst we wait for mobile app users to register after receiving a push notification. In the time we are waiting for the app to register, other UAs might reject the call (DND, Busy, etc). To avoid this failure response being relayed to the caller, we use t_drop_replies in the failure_route. Eventually if all devices … [View More]

1 0

Re: [SR-Users] Empty Subnets in Permissions Module
by Henning Westerholt 14 Sep '21

14 Sep '21

Hello, please keep the list in CC. Let’s look into the two issues one by one: 1) I had to explicitly configure the parameter: modparam("permissions", "mask_col", "mask") Although the documentation suggests "mask" is the default - the JSON output from "kamctl address dump" did not output this value on K5.5. (On K5.3 it outputted properly) Do you get an error if you do not specify the mask_col like this, or something else? From the source code the default should be “mask”. When I run the "… [View More]kamcmd permissions.subnetDump" on Kamailio 5.3, it returns everything as expected - including the 0.0.0.0/0<http://0.0.0.0/0> subnets. However, when running the same commands on Kamailio 5.5, it only returns a small subset (of only 20) subnets/groups - and the selection does not appear to follow a logical selection criteria. Additionally, it does not return any groups with a 0.0.0.0/0<http://0.0.0.0/0> subnet either. It seems that the behaviour has changed regarding the “0” subnet, checkout the docs: https://kamailio.org/docs/modules/devel/modules/permissions.html#permission… It will convert them to 32/128 respectively. Can you see a 0.0.0./32 in your dump? This was changed in commit f376c82a9f8 during an extension for text files. Maybe Daniel can comment here if this was done by purpose. Otherwise, you can open an issue on our tracker about it. Cheers, Henning -- Henning Westerholt – https://skalatan.de/blog/ Kamailio services – https://gilawa.com<https://gilawa.com/> From: Tom Dworakowski <dworakowski.tom(a)gmail.com> Sent: Tuesday, September 14, 2021 5:00 PM To: Henning Westerholt <hw(a)skalatan.de> Subject: Re: [SR-Users] Empty Subnets in Permissions Module Hello Henning, Thank you for looking into this for me. I made two interesting discoveries this morning: 1) I had to explicitly configure the parameter: modparam("permissions", "mask_col", "mask") Although the documentation suggests "mask" is the default - the JSON output from "kamctl address dump" did not output this value on K5.5. (On K5.3 it outputted properly) 2) When I run the "kamcmd permissions.subnetDump" on Kamailio 5.3, it returns everything as expected - including the 0.0.0.0/0<http://0.0.0.0/0> subnets. However, when running the same commands on Kamailio 5.5, it only returns a small subset (of only 20) subnets/groups - and the selection does not appear to follow a logical selection criteria. Additionally, it does not return any groups with a 0.0.0.0/0<http://0.0.0.0/0> subnet either. From my logs - I have noted this: Sep 14 03:07:25 webrtc kamailio[5407]: 0(5407) DEBUG: permissions [address.c:118]: reload_address_insert(): Tuple <4353, 0.0.0.0, 0> inserted into address hash table Sep 14 03:07:25 webrtc kamailio[5407]: 0(5407) DEBUG: permissions [address.c:118]: reload_address_insert(): Tuple <3769, 0.0.0.0, 0> inserted into address hash table Sep 14 03:07:25 webrtc kamailio[5407]: 0(5407) DEBUG: permissions [address.c:118]: reload_address_insert(): Tuple <4355, 0.0.0.0, 0> inserted into address hash table Sep 14 03:07:25 webrtc kamailio[5407]: 0(5407) DEBUG: permissions [address.c:118]: reload_address_insert(): Tuple <4359, 0.0.0.0, 0> inserted into address hash table Sep 14 03:07:25 webrtc kamailio[5407]: 0(5407) DEBUG: permissions [address.c:118]: reload_address_insert(): Tuple <1955, 84.XX.XX.66, 0> inserted into address hash table Sep 14 03:07:25 webrtc kamailio[5407]: 0(5407) DEBUG: permissions [address.c:118]: reload_address_insert(): Tuple <4361, 91.X.X.231, 0> inserted into address hash table Sep 14 03:07:25 webrtc kamailio[5407]: 0(5407) DEBUG: permissions [address.c:118]: reload_address_insert(): Tuple <4361, 91.X.X.33, 0> inserted into address hash table Sep 14 03:07:25 webrtc kamailio[5407]: 0(5407) DEBUG: permissions [address.c:118]: reload_address_insert(): Tuple <4361, 91.X.X.34, 0> inserted into address hash table Sep 14 03:07:25 webrtc kamailio[5407]: 0(5407) DEBUG: permissions [address.c:118]: reload_address_insert(): Tuple <4363, 80.X.X.25, 0> inserted into address hash table Sep 14 03:07:25 webrtc kamailio[5407]: 0(5407) DEBUG: permissions [address.c:118]: reload_address_insert(): Tuple <4363, 85.X.X.124, 0> inserted into address hash table Sep 14 03:07:25 webrtc kamailio[5407]: 0(5407) DEBUG: permissions [address.c:118]: reload_address_insert(): Tuple <4363, 212.X.X.19, 0> inserted into address hash table Sep 14 03:07:25 webrtc kamailio[5407]: 0(5407) DEBUG: permissions [address.c:118]: reload_address_insert(): Tuple <4365, 0.0.0.0, 0> inserted into address hash table Sep 14 03:07:25 webrtc kamailio[5407]: 0(5407) DEBUG: permissions [address.c:118]: reload_address_insert(): Tuple <4367, 0.0.0.0, 0> inserted into address hash table Sep 14 03:07:25 webrtc kamailio[5407]: 0(5407) DEBUG: permissions [address.c:118]: reload_address_insert(): Tuple <4371, 0.0.0.0, 0> inserted into address hash table Sep 14 03:07:25 webrtc kamailio[5407]: 0(5407) DEBUG: permissions [address.c:118]: reload_address_insert(): Tuple <3991, 0.0.0.0, 0> inserted into address hash table At the moment of querying group id 3983 (where there is only 0.0.0.0/0<http://0.0.0.0/0>), the function returns false: DEBUG: permissions [address.c:671]: allow_source_address(): looking for <3983, [IPv4 in hex, reversed octet order], 62281> However, None of those addresses appear in the "kamcmd permissions.subnetDump" output. Moreover, if "my" group has the address 0.0.0.0/0<http://0.0.0.0/0> listed as an approved address - it will fail the test; but if I register 0.0.0.0/1<http://0.0.0.0/1> it will let me through (as my IP is < 128.0.0.0), kamcmd permissions.subnetDump will display this address. My thoughts are that there might be another table that is not being populated - or there is a filter during the import that either drops 0.0.0.0/0<http://0.0.0.0/0> or filters it out completely? Regards, Tom On Tue, Sep 14, 2021 at 4:10 AM Henning Westerholt <hw(a)skalatan.de<mailto:hw@skalatan.de>> wrote: Hello Tom, I’ve done a quick comparison of the main function and the called function. On a first view it looked identically, but I looked only a few levels deep. Do you have maybe some means to reproduce this on a test system? Then it would be probably interesting to look to the DEBUG logging of this cases. Maybe you can compare if you spot some obvious differences from the logic. Cheers, Henning From: sr-users <sr-users-bounces(a)lists.kamailio.org<mailto:sr-users-bounces@lists.kamailio.org>> On Behalf Of Tom Dworakowski Sent: Tuesday, September 14, 2021 4:10 AM To: sr-users(a)lists.kamailio.org<mailto:sr-users@lists.kamailio.org> Subject: [SR-Users] Empty Subnets in Permissions Module Greetings all! I have two deployments of Kamailio: one running version 5.3 and one 5.5 with practically identical configurations, same (MySQL and REDIS) data sources. We have customers that we assign an ACL "group" to, where the ID of this group resolves to records in the "address" table in our MySQL database - using the "grp" field. On the box running Kamailio 5.5, we have noticed that if a group has ip_addr=0.0.0.0, mask=0, port=0 - and we try to run the allow_source_address() - it will return false, thus failing this phase of the authentication process. However, on Kamailio 5.3 we are not seeing this issue, i.e. if a customer is assigned a group where the ACL is 0.0.0.0/0<http://0.0.0.0/0> - it will let him through. Has something changed that I'm not aware of? Any suggestions on how to resolve this? My best, Tom [View Less]

2 1

Capturing response from uac_reg module
by Ross McKillop 14 Sep '21

14 Sep '21

Hi, What's the best way to capture the response from REGISTER requests automatically initiated by the uac_reg module? I was looking to use event_route[uac:reply] {} but that is only triggered if the evroute flag is set on the initial call made to uac_req_send() Is there a way to set this globally so that uac:reply is called for all requests initiated for peers in the uacreg table or a better way to capture the response? Best, Ross

3 4

Kamailio 5.4.3 crash at SSL error
by Igor Olhovskiy 14 Sep '21

14 Sep '21

Hello. Kamailio 5.4.3 crashes at CentOS 7 with following error logs Sep 13 13:15:11 /usr/local/sbin/kamailio[44592]: ERROR: <core> [core/tcp_read.c:1500]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f3b93734cf8 r: 0x7f3b93734e20 (-1) Sep 13 13:15:12 /usr/local/sbin/kamailio[44594]: NOTICE: tls [tls_domain.c:747]: sr_ssl_ctx_info_callback(): SSL handshake started Sep 13 13:15:12 kernel: traps: kamailio[44594] general protection ip:7f3ba8fb3c09 sp:7ffe2c3aff70 error:0 … [View More]

2 3

Manage blacklisting on network errors
by Marat Gareev 14 Sep '21

14 Sep '21

Hello! I have a simple config for routing requests with failover and blacklisting on 408, 480 and 503 codes from servers. This is a part of config: # Wrapper for relaying requests route[RELAY] { # the base event routes t_on_branch("MANAGE_BRANCH"); t_on_reply("MANAGE_REPLY"); t_on_failure("MANAGE_FAILURE"); if (!t_relay()) { sl_reply_error(); } exit; } # Manage incoming replies onreply_route[MANAGE_REPLY] { xlog("L_NOTICE", "$rr ($rs) [$cs] ($ci) $si:$sp - $ua\n"); if ( t_check_status("(… [View More]

2 2

Question about suspected memory leak presence module
by Albert Petit 14 Sep '21

14 Sep '21

Hi, I am suspecitng presence module might be having a memory leak on a production server used by an end user (not have access to it). The output of command kamcmd mod.stats presence shm is Module: presence { mem_copy_subs(148): 25720 mem_copy_subs_noc(214): 1672201904 mem_copy_subs_noc(251): 678406560 add_event(181): 88 shm_copy_event(57): 40 shm_copy_event(50): 312 add_event(156): 40 add_event(149): 456 … [View More]

2 3

Empty Subnets in Permissions Module
by Tom Dworakowski 14 Sep '21

14 Sep '21

Greetings all! I have two deployments of Kamailio: one running version 5.3 and one 5.5 with practically identical configurations, same (MySQL and REDIS) data sources. We have customers that we assign an ACL "group" to, where the ID of this group resolves to records in the "address" table in our MySQL database - using the "grp" field. On the box running Kamailio 5.5, we have noticed that if a group has ip_addr=0.0.0.0, mask=0, port=0 - and we try to run the allow_source_address() - it will … [View More]

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