sr-users December 2020

sr-users@lists.kamailio.org

67 participants
87 discussions

by Chaigneau, Nicolas

Hello, I'd like to use a < select > as described here: http://www.kamailio.org/wiki/cookbooks/5.4.x/selects#contactparams_s I'm trying to extract a parameter from the Contact URI. What I've tried to do: xlog("L_INFO", "contact.uri: $sel(contact.uri)\n"); # OK xlog("L_INFO", "contact.uri.params: $sel(contact.uri.params)\n"); # null ?? This does not seem to work... see output here : 3(10316) INFO: {1 INVITE r8wEHsAgxNIS5OJL} <script>: contact.uri: sip:+33145678901;tgrp=YC031;trunk-context=YC90@10.31.22.2:5099 3(10316) INFO: {1 INVITE r8wEHsAgxNIS5OJL} <script>: contact.uri.params: <null> What am I doing wrong ? Maybe this is the wrong approach for what I'm trying to do ? Regards, Nicolas. This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.

3 years, 10 months

Releasing Kamailio 5.3.8

by Henning Westerholt

Hello, I am planning to release next week (likely on Monday 21st December) the next minor version out of branch 5.3, version 5.3.8. Backports of fixed issues from git master will be integrated as usual. If you are aware of new issues which were not yet reported, let us know (by creating an issue on the tracker). Cheers, Henning -- Henning Westerholt - https://skalatan.de/blog/ Kamailio services - https://gilawa.com<https://gilawa.com/>

3 years, 10 months

send MESSAGE to other sessions of same user

by Syed Shahryar

What's the best way of sending a message to all other sessions (and the receiver) of the same sender? For example: If user1(a)example.com is logged in to Kamailio from multiple devices and from one of the devices user1 sends a SIP message to user2(a)example.com. I want the message forwarded not only to user2(a)example.com but also to all other user1(a)example.com sessions. What's the easiest way to achieve this? -- -- This message contains confidential information and is intended only for the individual named. If you are not the named addressee, you should not disseminate, distribute or copy this email. Please notify the sender immediately by email if you have received this email by mistake and delete this email from your system. Email transmission cannot be guaranteed to be secure or error-free, as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender, therefore, does not accept liability for any errors or omissions in the contents of this message which arise as a result of email transmission. If verification is required, please request a hard-copy version.

3 years, 10 months

Kamailio not updating CSeq after uac_auth() for ACK

by Terry Tailor

Hi, Here is setup details Kamailio Proxy a <-----> Kamailio Proxy b <-----> Asterisk Kamailio proxy b auth based on IP Kamailio Proxy a 1. Kamailio proxy sends an Invite request to Kamailio proxy b with CSeq: 102 INVITE 2. Kamailio proxy b check again IP auth and sends invite request to asterisk with CSeq: 102 INVITE 4 asterisk response with 401 Unauthorized with CSeq: 102 5. Kamailio proxy b sends ACK request with CSeq: 102 ACK 6. Kamailio proxy b sends INVITE request with CSeq: 103 INVITE 7. Asterisk sends 100 trying and 180 ringing with CSeq: 103 INVITE 8. Kamailio proxy b relay 180 ringing with CSeq: 102 INVITE 9. Asterisk send 200 Ok with CSeq: 103 INVITE and proxy b relay it to proxy a with CSeq: 102 INVITE 10. Now Proxy a send an ACK with CSeq: 102 ACK and proxy b relay ACK to asterisk with CSeq: 102 ACK Now asterisk is retransmitting 200 ok with CSeq: 103 INVITE and proxy a is sending ACK with Cseq: 102 ACK Same happing in case of 487 Request Terminated Here is my config modparam("dialog", "default_timeout", 10800) # 3h modparam("dialog", "dlg_match_mode", 1) modparam("dialog", "db_mode", 0) modparam("dialog", "send_bye", 1) modparam("dialog", "track_cseq_updates", 1) modparam("uac","auth_username_avp","$avp(auser)") modparam("uac","auth_password_avp","$avp(apass)") modparam("uac","auth_realm_avp","$avp(arealm)") modparam("tm", "failure_reply_mode", 3) # default retransmission timeout: 3 sec modparam("tm", "fr_timer", 2000) modparam("tm", "retr_timer1", 250) modparam("tm", "retr_timer2", 500) # default invite retransmission timeout after 1xx: 60 sec modparam("tm", "fr_inv_timer", 60000) modparam("tm", "reparse_on_dns_failover", 0) if (is_method("INVITE") && !has_totag()) { dlg_setflag(FLD_RTPPROXY); dlg_manage(); } route(RELAY); route[RELAY] { # At this point all checks are passed t_on_branch("MANAGE_BRANCH"); t_on_reply("MANAGE_REPLY"); t_on_failure("MANAGE_FAILURE"); if(is_method("INVITE") && isflagset(FLT_FROMDID)) { #$fd = "sip.comms.kuflink.com"; t_on_failure("RELAY_AUTH"); } if (!t_relay()) { send_reply("500", "Cannot relay to $du/$ru"); } exit; } failure_route[RELAY_AUTH] { t_on_branch("MANAGE_BRANCH"); t_on_reply("MANAGE_REPLY"); if (t_is_canceled()) { exit; } if(t_check_status("401|407")) { #$fd = "sip.comms.kuflink.com"; $avp(auser) = "DID_UA_USERNAME"; $avp(apass) = "DID_UA_PASSWORD"; if (uac_auth()) { t_relay(); } exit; } } route[WITHINDLG] { if (!has_totag()) { return; } if (is_method("BYE")) { rtpengine_delete(); } # sequential request withing a dialog should # take the path determined by record-routing if (loose_route()) { route(DLGURI); if (is_method("ACK")) { # ACK is forwarded statelessly route(NATMANAGE); } else if (is_method("NOTIFY")) { # Add Record-Route for in-dialog NOTIFY as per RFC 6665. record_route(); } route(RELAY); exit; } if (is_method("SUBSCRIBE") && uri == myself) { # in-dialog subscribe requests route(PRESENCE); exit; } if (is_method("ACK") ) { if (t_check_trans()) { # no loose-route, but stateful ACK; # must be an ACK after a 487 # or e.g. 404 from upstream server route(RELAY); exit; } else { # ACK without matching transaction ... ignore and discard exit; } } send_reply("404","Not here"); exit; } kamailio -v version: kamailio 5.3.7 (x86_64/linux) flags: USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MMAP, PKG_MALLOC, Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLACKLIST, HAVE_RESOLV_RES, TLS_PTHREAD_MUTEX_SHARED ADAPTIVE_WAIT_LOOPS 1024, MAX_RECV_BUFFER_SIZE 262144, MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. id: unknown compiled with gcc 6.3.0 uname -a Linux example.com 4.15.0-124-generic #127-Ubuntu SMP Fri Nov 6 10:54:43 UTC 2020 x86_64 GNU/Linux SIP logs 2020/12/17 10:08:18.483907 proxy-a.com:5060 -> 10.0.14.118:5060 INVITE sip:123456@proxy-a.com SIP/2.0 Record-Route: <sip:proxy-a.com;lr> Via: SIP/2.0/UDP proxy-a.com:5060 ;branch=z9hG4bKbe6d.10c4c5f001c66b8976214d4aef9f635c.1 Via: SIP/2.0/UDP did.com:5060;received=did.com ;branch=z9hG4bK45f94ed9;rport=5060 Max-Forwards: 70 From: "7654321" <sip:7654321@did.com>;tag=as55c522e1 To: <sip:123456@proxy-a.com> Contact: <sip:7654321@did.com:5060> Call-ID: 67675c7e636d6e773860255316e54779(a)did.com User-Agent: ProxyA CSeq: 102 INVITE User-Agent: proxy Date: Thu, 17 Dec 2020 10:08:18 GMT Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE Supported: replaces, timer Remote-Party-ID: "7654321" <sip:7654321@did.com >;party=calling;privacy=off;screen=no Content-Type: application/sdp Content-Length: 885 2020/12/17 10:08:18.485063 10.0.14.118:5060 -> proxy-a.com:5060 SIP/2.0 100 trying -- your call is important to us Via: SIP/2.0/UDP proxy-a.com:5060 ;branch=z9hG4bKbe6d.10c4c5f001c66b8976214d4aef9f635c.1;rport=5060 Via: SIP/2.0/UDP did.com:5060;received=did.com ;branch=z9hG4bK45f94ed9;rport=5060 From: "7654321" <sip:7654321@did.com>;tag=as55c522e1 To: <sip:123456@proxy-a.com> Call-ID: 67675c7e636d6e773860255316e54779(a)did.com CSeq: 102 INVITE Server: kamailio (5.3.7 (x86_64/linux)) Content-Length: 0 2020/12/17 10:08:18.485576 10.0.14.118:5060 -> 10.0.14.118:6000 INVITE sip:123456@proxy-a.com SIP/2.0 Record-Route: <sip:proxy-b.com;lr;did=d18.7a9> Record-Route: <sip:proxy-a.com;lr> Via: SIP/2.0/UDP proxy-b.com:5060 ;branch=z9hG4bKbe6d.619fd995c3fc8764ce5cd9c7be7efeef.0 Via: SIP/2.0/UDP proxy-a.com:5060 ;rport=5060;branch=z9hG4bKbe6d.10c4c5f001c66b8976214d4aef9f635c.1 Via: SIP/2.0/UDP did.com:5060;received=did.com ;branch=z9hG4bK45f94ed9;rport=5060 Max-Forwards: 70 From: "7654321" <sip:7654321@did.com>;tag=as55c522e1 To: <sip:123456@proxy-a.com> Contact: <sip:7654321@did.com:5060> Call-ID: 67675c7e636d6e773860255316e54779(a)did.com User-Agent: ProxyA CSeq: 102 INVITE User-Agent: proxy Date: Thu, 17 Dec 2020 10:08:18 GMT Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE Supported: replaces, timer Remote-Party-ID: "7654321" <sip:7654321@did.com >;party=calling;privacy=off;screen=no Content-Type: application/sdp Content-Length: 885 2020/12/17 10:08:18.622867 10.0.14.118:6000 -> 10.0.14.118:5060 SIP/2.0 401 Unauthorized Via: SIP/2.0/UDP proxy-b.com:5060 ;branch=z9hG4bKbe6d.619fd995c3fc8764ce5cd9c7be7efeef.0;received=10.0.14.118;rport=5060 Via: SIP/2.0/UDP proxy-a.com:5060 ;rport=5060;branch=z9hG4bKbe6d.10c4c5f001c66b8976214d4aef9f635c.1 Via: SIP/2.0/UDP did.com:5060;received=did.com ;branch=z9hG4bK45f94ed9;rport=5060 From: "7654321" <sip:7654321@did.com>;tag=as55c522e1 To: <sip:123456@proxy-a.com>;tag=as4107645c Call-ID: 67675c7e636d6e773860255316e54779(a)did.com CSeq: 102 INVITE Server: proxy Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE Supported: replaces, timer WWW-Authenticate: Digest algorithm=MD5, realm="sip1.comms.kuflink.com", nonce="11139d33" Content-Length: 0 2020/12/17 10:08:18.624034 10.0.14.118:5060 -> 10.0.14.118:6000 ACK sip:123456@proxy-a.com SIP/2.0 Via: SIP/2.0/UDP proxy-b.com:5060 ;branch=z9hG4bKbe6d.619fd995c3fc8764ce5cd9c7be7efeef.0 Max-Forwards: 70 From: "7654321" <sip:7654321@did.com>;tag=as55c522e1 To: <sip:123456@proxy-a.com>;tag=as4107645c Call-ID: 67675c7e636d6e773860255316e54779(a)did.com CSeq: 102 ACK Content-Length: 0 2020/12/17 10:08:18.625557 10.0.14.118:5060 -> 10.0.14.118:6000 INVITE sip:123456@proxy-a.com SIP/2.0 Record-Route: <sip:proxy-b.com;lr;did=d18.7a9> Record-Route: <sip:proxy-a.com;lr> Via: SIP/2.0/UDP proxy-b.com:5060 ;branch=z9hG4bKbe6d.619fd995c3fc8764ce5cd9c7be7efeef.1.cs102 Via: SIP/2.0/UDP proxy-a.com:5060 ;rport=5060;branch=z9hG4bKbe6d.10c4c5f001c66b8976214d4aef9f635c.1 Via: SIP/2.0/UDP did.com:5060;received=did.com ;branch=z9hG4bK45f94ed9;rport=5060 Max-Forwards: 70 From: "7654321" <sip:7654321@did.com>;tag=as55c522e1 To: <sip:123456@proxy-a.com> Contact: <sip:7654321@did.com:5060> Call-ID: 67675c7e636d6e773860255316e54779(a)did.com User-Agent: ProxyA CSeq: 103 INVITE User-Agent: proxy Date: Thu, 17 Dec 2020 10:08:18 GMT Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE Supported: replaces, timer Remote-Party-ID: "7654321" <sip:7654321@did.com >;party=calling;privacy=off;screen=no Content-Type: application/sdp Content-Length: 885 Authorization: Digest username="xxxxx", realm="xxxx", nonce="11139d33", uri="sip:123456@proxy-a.com", response="qwewqeqwe", algorithm=MD5 2020/12/17 10:08:18.779483 10.0.14.118:6000 -> 10.0.14.118:5060 SIP/2.0 100 Trying Via: SIP/2.0/UDP proxy-b.com:5060 ;branch=z9hG4bKbe6d.619fd995c3fc8764ce5cd9c7be7efeef.1.cs102;received=10.0.14.118;rport=5060 Via: SIP/2.0/UDP proxy-a.com:5060 ;rport=5060;branch=z9hG4bKbe6d.10c4c5f001c66b8976214d4aef9f635c.1 Via: SIP/2.0/UDP did.com:5060;received=did.com ;branch=z9hG4bK45f94ed9;rport=5060 Record-Route: <sip:proxy-b.com;lr;did=d18.7a9> Record-Route: <sip:proxy-a.com;lr> From: "7654321" <sip:7654321@did.com>;tag=as55c522e1 To: <sip:123456@proxy-a.com> Call-ID: 67675c7e636d6e773860255316e54779(a)did.com CSeq: 103 INVITE Server: proxy Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE Supported: replaces, timer Session-Expires: 1800;refresher=uas Contact: <sip:123456@10.0.14.118:6000> Content-Length: 0 2020/12/17 10:08:20.937756 10.0.14.118:6000 -> 10.0.14.118:5060 SIP/2.0 180 Ringing Via: SIP/2.0/UDP proxy-b.com:5060 ;branch=z9hG4bKbe6d.619fd995c3fc8764ce5cd9c7be7efeef.1.cs102;received=10.0.14.118;rport=5060 Via: SIP/2.0/UDP proxy-a.com:5060 ;rport=5060;branch=z9hG4bKbe6d.10c4c5f001c66b8976214d4aef9f635c.1 Via: SIP/2.0/UDP did.com:5060;received=did.com ;branch=z9hG4bK45f94ed9;rport=5060 Record-Route: <sip:proxy-b.com;lr;did=d18.7a9> Record-Route: <sip:proxy-a.com;lr> From: "7654321" <sip:7654321@did.com>;tag=as55c522e1 To: <sip:123456@proxy-a.com>;tag=as147bfa3e Call-ID: 67675c7e636d6e773860255316e54779(a)did.com CSeq: 103 INVITE Server: proxy Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE Supported: replaces, timer Session-Expires: 1800;refresher=uas Contact: <sip:123456@10.0.14.118:6000> Content-Length: 0 2020/12/17 10:08:20.938593 10.0.14.118:5060 -> proxy-a.com:5060 SIP/2.0 180 Ringing Via: SIP/2.0/UDP proxy-a.com:5060 ;rport=5060;branch=z9hG4bKbe6d.10c4c5f001c66b8976214d4aef9f635c.1 Via: SIP/2.0/UDP did.com:5060;received=did.com ;branch=z9hG4bK45f94ed9;rport=5060 Record-Route: <sip:proxy-b.com;lr;did=d18.7a9> Record-Route: <sip:proxy-a.com;lr> From: "7654321" <sip:7654321@did.com>;tag=as55c522e1 To: <sip:123456@proxy-a.com>;tag=as147bfa3e Call-ID: 67675c7e636d6e773860255316e54779(a)did.com CSeq: 102 INVITE Server: proxy Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE Supported: replaces, timer Session-Expires: 1800;refresher=uas Contact: <sip:123456@10.0.14.118:6000;alias=10.0.14.118~6000~1> Content-Length: 0 2020/12/17 10:08:22.075814 10.0.14.118:6000 -> 10.0.14.118:5060 SIP/2.0 200 OK Via: SIP/2.0/UDP proxy-b.com:5060 ;branch=z9hG4bKbe6d.619fd995c3fc8764ce5cd9c7be7efeef.1.cs102;received=10.0.14.118;rport=5060 Via: SIP/2.0/UDP proxy-a.com:5060 ;rport=5060;branch=z9hG4bKbe6d.10c4c5f001c66b8976214d4aef9f635c.1 Via: SIP/2.0/UDP did.com:5060;received=did.com ;branch=z9hG4bK45f94ed9;rport=5060 Record-Route: <sip:proxy-b.com;lr;did=d18.7a9> Record-Route: <sip:proxy-a.com;lr> From: "7654321" <sip:7654321@did.com>;tag=as55c522e1 To: <sip:123456@proxy-a.com>;tag=as147bfa3e Call-ID: 67675c7e636d6e773860255316e54779(a)did.com CSeq: 103 INVITE Server: proxy Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE Supported: replaces, timer Session-Expires: 1800;refresher=uas Contact: <sip:123456@10.0.14.118:6000> Content-Type: application/sdp Require: timer Content-Length: 296 2020/12/17 10:08:22.077049 10.0.14.118:5060 -> proxy-a.com:5060 SIP/2.0 200 OK Via: SIP/2.0/UDP proxy-a.com:5060 ;rport=5060;branch=z9hG4bKbe6d.10c4c5f001c66b8976214d4aef9f635c.1 Via: SIP/2.0/UDP did.com:5060;received=did.com ;branch=z9hG4bK45f94ed9;rport=5060 Record-Route: <sip:proxy-b.com;lr;did=d18.7a9> Record-Route: <sip:proxy-a.com;lr> From: "7654321" <sip:7654321@did.com>;tag=as55c522e1 To: <sip:123456@proxy-a.com>;tag=as147bfa3e Call-ID: 67675c7e636d6e773860255316e54779(a)did.com CSeq: 102 INVITE Server: proxy Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE Supported: replaces, timer Session-Expires: 1800;refresher=uas Contact: <sip:123456@10.0.14.118:6000;alias=10.0.14.118~6000~1> Content-Type: application/sdp Require: timer Content-Length: 316 2020/12/17 10:08:22.103365 proxy-a.com:5060 -> 10.0.14.118:5060 ACK sip:123456@10.0.14.118:6000;alias=10.0.14.118~6000~1;alias=109.72.216.251~5060~1 SIP/2.0 Via: SIP/2.0/UDP proxy-a.com:5060 ;branch=z9hG4bKbe6d.0fc1940efc770391762d7d67094c24f8.0 Via: SIP/2.0/UDP did.com:5060;received=did.com ;branch=z9hG4bK2a5fae72;rport=5060 Route: <sip:proxy-b.com;lr;did=d18.7a9> Max-Forwards: 70 From: "7654321" <sip:7654321@did.com>;tag=as55c522e1 To: <sip:123456@proxy-a.com>;tag=as147bfa3e Contact: <sip:7654321@did.com:5060> Call-ID: 67675c7e636d6e773860255316e54779(a)did.com CSeq: 102 ACK User-Agent: proxy Content-Length: 0 2020/12/17 10:08:22.103877 10.0.14.118:5060 -> 10.0.14.118:6000 ACK sip:123456@10.0.14.118:6000;alias=109.72.216.251~5060~1 SIP/2.0 Via: SIP/2.0/UDP proxy-b.com:5060 ;branch=z9hG4bKbe6d.79f351d031912aae585207d2f26d5650.0 Via: SIP/2.0/UDP proxy-a.com:5060 ;rport=5060;branch=z9hG4bKbe6d.0fc1940efc770391762d7d67094c24f8.0 Via: SIP/2.0/UDP did.com:5060;received=did.com ;branch=z9hG4bK2a5fae72;rport=5060 Max-Forwards: 70 From: "7654321" <sip:7654321@did.com>;tag=as55c522e1 To: <sip:123456@proxy-a.com>;tag=as147bfa3e Contact: <sip:7654321@did.com:5060> Call-ID: 67675c7e636d6e773860255316e54779(a)did.com CSeq: 102 ACK User-Agent: proxy Content-Length: 0 P-K-CSeq-Refresh: 103 2020/12/17 10:08:22.575533 10.0.14.118:6000 -> 10.0.14.118:5060 SIP/2.0 200 OK Via: SIP/2.0/UDP proxy-b.com:5060 ;branch=z9hG4bKbe6d.619fd995c3fc8764ce5cd9c7be7efeef.1.cs102;received=10.0.14.118;rport=5060 Via: SIP/2.0/UDP proxy-a.com:5060 ;rport=5060;branch=z9hG4bKbe6d.10c4c5f001c66b8976214d4aef9f635c.1 Via: SIP/2.0/UDP did.com:5060;received=did.com ;branch=z9hG4bK45f94ed9;rport=5060 Record-Route: <sip:proxy-b.com;lr;did=d18.7a9> Record-Route: <sip:proxy-a.com;lr> From: "7654321" <sip:7654321@did.com>;tag=as55c522e1 To: <sip:123456@proxy-a.com>;tag=as147bfa3e Call-ID: 67675c7e636d6e773860255316e54779(a)did.com CSeq: 103 INVITE Server: proxy Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE Supported: replaces, timer Session-Expires: 1800;refresher=uas Contact: <sip:123456@10.0.14.118:6000> Content-Type: application/sdp Require: timer Content-Length: 296 2020/12/17 10:08:22.576777 10.0.14.118:5060 -> proxy-a.com:5060 SIP/2.0 200 OK Via: SIP/2.0/UDP proxy-a.com:5060 ;rport=5060;branch=z9hG4bKbe6d.10c4c5f001c66b8976214d4aef9f635c.1 Via: SIP/2.0/UDP did.com:5060;received=did.com ;branch=z9hG4bK45f94ed9;rport=5060 Record-Route: <sip:proxy-b.com;lr;did=d18.7a9> Record-Route: <sip:proxy-a.com;lr> From: "7654321" <sip:7654321@did.com>;tag=as55c522e1 To: <sip:123456@proxy-a.com>;tag=as147bfa3e Call-ID: 67675c7e636d6e773860255316e54779(a)did.com CSeq: 102 INVITE Server: proxy Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE Supported: replaces, timer Session-Expires: 1800;refresher=uas Contact: <sip:123456@10.0.14.118:6000;alias=10.0.14.118~6000~1> Content-Type: application/sdp Require: timer Content-Length: 316 2020/12/17 10:08:22.581649 proxy-a.com:5060 -> 10.0.14.118:5060 ACK sip:123456@10.0.14.118:6000;alias=10.0.14.118~6000~1;alias=109.72.216.251~5060~1 SIP/2.0 Via: SIP/2.0/UDP proxy-a.com:5060 ;branch=z9hG4bKbe6d.b9c7eeccd4cd7b44f05b173308dbaf0a.0 Via: SIP/2.0/UDP did.com:5060;received=did.com ;branch=z9hG4bK219933f6;rport=5060 Route: <sip:proxy-b.com;lr;did=d18.7a9> Max-Forwards: 70 From: "7654321" <sip:7654321@did.com>;tag=as55c522e1 To: <sip:123456@proxy-a.com>;tag=as147bfa3e Contact: <sip:7654321@did.com:5060> Call-ID: 67675c7e636d6e773860255316e54779(a)did.com CSeq: 102 ACK User-Agent: proxy Content-Length: 0 2020/12/17 10:08:22.582313 10.0.14.118:5060 -> 10.0.14.118:6000 ACK sip:123456@10.0.14.118:6000;alias=109.72.216.251~5060~1 SIP/2.0 Via: SIP/2.0/UDP proxy-b.com:5060 ;branch=z9hG4bKbe6d.33626b5695ad4648ba393bc62bed6a8c.0 Via: SIP/2.0/UDP proxy-a.com:5060 ;rport=5060;branch=z9hG4bKbe6d.b9c7eeccd4cd7b44f05b173308dbaf0a.0 Via: SIP/2.0/UDP did.com:5060;received=did.com ;branch=z9hG4bK219933f6;rport=5060 Max-Forwards: 70 From: "7654321" <sip:7654321@did.com>;tag=as55c522e1 To: <sip:123456@proxy-a.com>;tag=as147bfa3e Contact: <sip:7654321@did.com:5060> Call-ID: 67675c7e636d6e773860255316e54779(a)did.com CSeq: 102 ACK User-Agent: proxy Content-Length: 0 P-K-CSeq-Refresh: 103 2020/12/17 10:08:23.575828 10.0.14.118:6000 -> 10.0.14.118:5060 SIP/2.0 200 OK Via: SIP/2.0/UDP proxy-b.com:5060 ;branch=z9hG4bKbe6d.619fd995c3fc8764ce5cd9c7be7efeef.1.cs102;received=10.0.14.118;rport=5060 Via: SIP/2.0/UDP proxy-a.com:5060 ;rport=5060;branch=z9hG4bKbe6d.10c4c5f001c66b8976214d4aef9f635c.1 Via: SIP/2.0/UDP did.com:5060;received=did.com ;branch=z9hG4bK45f94ed9;rport=5060 Record-Route: <sip:proxy-b.com;lr;did=d18.7a9> Record-Route: <sip:proxy-a.com;lr> From: "7654321" <sip:7654321@did.com>;tag=as55c522e1 To: <sip:123456@proxy-a.com>;tag=as147bfa3e Call-ID: 67675c7e636d6e773860255316e54779(a)did.com CSeq: 103 INVITE Server: proxy Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE Supported: replaces, timer Session-Expires: 1800;refresher=uas Contact: <sip:123456@10.0.14.118:6000> Content-Type: application/sdp Require: timer Content-Length: 296 2020/12/17 10:08:23.577863 10.0.14.118:5060 -> proxy-a.com:5060 SIP/2.0 200 OK Via: SIP/2.0/UDP proxy-a.com:5060 ;rport=5060;branch=z9hG4bKbe6d.10c4c5f001c66b8976214d4aef9f635c.1 Via: SIP/2.0/UDP did.com:5060;received=did.com ;branch=z9hG4bK45f94ed9;rport=5060 Record-Route: <sip:proxy-b.com;lr;did=d18.7a9> Record-Route: <sip:proxy-a.com;lr> From: "7654321" <sip:7654321@did.com>;tag=as55c522e1 To: <sip:123456@proxy-a.com>;tag=as147bfa3e Call-ID: 67675c7e636d6e773860255316e54779(a)did.com CSeq: 102 INVITE Server: proxy Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE Supported: replaces, timer Session-Expires: 1800;refresher=uas Contact: <sip:123456@10.0.14.118:6000;alias=10.0.14.118~6000~1> Content-Type: application/sdp Require: timer Content-Length: 316

3 years, 10 months

Kamailio RTP proxy require?

by Mihai Cezar

Hi, Can't figure it out when to use RTPproxy, i am forwarding everything to asterisk in seem to work without RTPproxy. The scenario is like this: Softphone -> INTERNET -> Kamailio - > Asterisk (private ip) Now it seems to work without any rtpproxy but is it ok?

3 years, 10 months

DLGLOAD stuck in Dispatcher Module(HA Mode)

by harneet singh

Hi All, I am using Kamailio in HA mode with Keepalived providing the VIP(Virtual IP) functionality, and have run into a rather peculiar issue. *Setup:* Caller ------------ KamailioVIP(*Primary *and *Secondary* Kamailio)------- Callee HA provided by Keepalived DMQ is used between the Primary and Secondary Kamailio for dialog sync *Issue Seen:* *Suppose the Primary Kamailio has been brought down* and the Secondary one is actually active and tied to the VIP. When a call is fired from the Caller, it traverses through the Secondary Kamailio and lands onto the callee. The dialogs are updated properly. At this point, the Primary Kamailio is brought up, and dialog state is synced due to the DMQ module. The Keepalived will now attach the VIP to the Primary Instance. If the caller hangs up the phone at this point, the BYE sip message traverses through the Primary Kamailio instance to the callee and the call is cleared, but there are two issues here. 1. The Primary Kamailio throws an error in *ds_load_remove() *saying that it cannot find the load for the specific call id. This is apparently due to the fact that the dispatcher data is not synced between the two modules but dialog data is. So dialog wise, things are fine. Can this be fixed somehow? 2. The above is still as grave a problem as the dialogs are cleared. BUT, if we check the '*kamcmd dispatcher.list*' on the *SECONDARY* kamailio even well after the call is cleared, the *DLGLOAD* shows 1. Since we are using the *Call Load based distribution* for the dispatching, this is effectively one call stuck on the dispatcher, which leads to resource leak. Is this a known issue, and if so, do we have a way to circumvent this? Regards, Harneet Singh -- "Once you eliminate the impossible, whatever remains, no matter how improbable, must be the truth" - Sir Arthur Conan Doyle

3 years, 10 months

INFO: RTC Devroom Fosdem 2021 - Online Event

by Daniel-Constantin Mierla

Hello, (cross-posting to kamailio public groups, a few may get this message duplicated). Fosdem 2021 is going to be online, meaning that it opens the possibility for everyone to do a presentation on the RTC Devroom, no longer being required to travel to Brussels. Therefore I am sending here the link to CFP in case someone would be interested to present about Kamailio or something else RTC-related: * https://github.com/FreeRTC/fosdem/blob/master/2021/cfp.md New speakers are always welcome! Only have in mind that the event is targeting developers and source code development, therefore your proposals have to be made from this perspective. Note also that submission deadline is 20th of December, very short time frame from now. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda

3 years, 10 months

ERROR: dmq [notification_peer.c:337]: add_server_and_notify(): error adding notification node

by Syed Shahryar

Here is my setting: modparam("dmq", "server_address", "sip:0.0.0.0:5090" ) modparam("dmq", "notification_address", "sip:0.0.0.0:5090") modparam("dmq", "multi_notify", 1) modparam("dmq", "num_workers", 2) modparam("dmq", "worker_usleep", 0) modparam("dmq", "ping_interval", 90) I have tried localhost and I believe other options but to no avail. I also get the following message: ERROR: dmq [dmq_funcs.c:516]: ping_servers(): cannot retrieve initial nodelist from sip:0.0.0.0:5090 How do I set up DMQ for adding and removing any Kamailio instance to/from the cluster and any Kamailio instance could serve any request coming from any client? ie. all Kamailio instances keep the current state in DMQ. I also have dmq_usrloc enabled. -- -- This message contains confidential information and is intended only for the individual named. If you are not the named addressee, you should not disseminate, distribute or copy this email. Please notify the sender immediately by email if you have received this email by mistake and delete this email from your system. Email transmission cannot be guaranteed to be secure or error-free, as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender, therefore, does not accept liability for any errors or omissions in the contents of this message which arise as a result of email transmission. If verification is required, please request a hard-copy version.

3 years, 10 months

Kamailio dtmf signaling

by Amit Pal

Dear Team, I am using kamailio + rtpengine, how can I processed dtmf from cfg scripts. even thought I can able to see dtmf over syslog. but can not able to capture in kamailio.cfg. how can I prepared ivr using kamalio? Please find the attached syslog. Regards Amit Pal

3 years, 10 months

ERROR: <core> [core/parser/parse_uri.c:1326]: _parse_ruri(): bad uri </sip?jwt=..

by Syed Shahryar

I am sending JWT tokens via SIP URL through JSSIP for authentication before websocket connection is made. However, I am getting errors like: ERROR: <core> [core/parser/parse_uri.c:1326]: _parse_ruri(): bad uri < */sip?jwt=..* I have the following setting in kamailio config: modparam("xhttp", "url_match", "^/sip") // only match this path Is this a bug or some configuration issue? How do I resolve it? -- -- This message contains confidential information and is intended only for the individual named. If you are not the named addressee, you should not disseminate, distribute or copy this email. Please notify the sender immediately by email if you have received this email by mistake and delete this email from your system. Email transmission cannot be guaranteed to be secure or error-free, as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender, therefore, does not accept liability for any errors or omissions in the contents of this message which arise as a result of email transmission. If verification is required, please request a hard-copy version.

3 years, 10 months

← Newer
1
2
3
4
5
6
7
8
9
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

sr-users December 2020