sr-users

sr-users@lists.kamailio.org

42 participants
37519 discussions

Start a nNew thread

Kamailio release
by Virgílio Cunha 03 Apr '20

03 Apr '20

Hi, When is the scheduled release date of kamailio-5.3.4? Best Regards, Virgílio Cunha

1 0

[ot] lightweight sip app for auto-answering with play file and echo mode
by Daniel-Constantin Mierla 01 Apr '20

01 Apr '20

Hello, wondering if anyone here is aware of a lightweight sip app that can answer a call, play some file and/or do echo mode, mainly targeted at using it for basic sip routing and call testing. Of course I know that Asterisk and FreeSwitch (or even SEMS) can do that, but they have many dependencies, requiring quite some resources to run them, so I thought maybe someone here figured out different solutions, eventually cli based apps like pjsua or baresip. GUI apps for Linux are also fine if they can be configured for such behaviour. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda

7 18

Invite transaction lifetime
by Duarte Rocha 01 Apr '20

01 Apr '20

Greetings, I have a strange call with a client in which he sends me an INVITE and i do the usual "100", "183" and "200 - OK" but the client never gets my provisional or final responses and, as such keeps retransmitting the first INVITE. For the first retransmissions Kamailio doesn't relay the INVITE which i think is the correct behaviour. However, after around 30s, a retransmission is processed and is relayed to a different destination, using "ds_select_dst()" from the DISPATCH module. For this to happen it had to fail the "t_check_trans()" function from TM module which tells me that the transaction from the first INVITE was gone. I went to search timers and lifetime definitions on TM module and found one "max_inv_lifetime" which tells me that "An INVITE transaction will be kept in memory for maximum: max_inv_lifetime+fr_timer(from the ACK to the final reply wait)+wt_timer". In this case : max_inv_lifetime is 180 seconds, fr_timer is 30 seconds and wt_timer is 5 seconds. It's sum is 215seconds and from what i can see, my transaction only had a lifetime of 30s. fr_timer is configured with 30s but it's definition is "Timer which hits if no final reply for a request or ACK for a negative INVITE reply arrives (in milliseconds)." and it mentions ACK, but in my case it's an ACK for a final reply that is missing and not an ACK for a negative reply. What other reasons might have caused this transaction to be terminated ? Best Regards

1 0

Re: [SR-Users] Use topos module to hide contact in OPTIONS request
by Enzo 01 Apr '20

01 Apr '20

2 1

Dialog: dlg_var and multi-branch call
by SamyGo 31 Mar '20

31 Mar '20

Hi All, Just curious to ask as how to save $dlg_var for a multi-leg/branched call. When I call a subscriber with multiple Contacts, and one branch answer while rest are CANCEL'd from that point onward I've seen that the dialog and its variables disappear from Kamailio memory and DB.Is this how its intended to be ? Here are the relevant debug line: DEBUG: dialog [dlg_hash.c:1266]: next_state_dlg(): dialog 0x7f7c1461e2e8 changed from state 2 to state 5, due event 4 (ref 2) DEBUG: dialog [dlg_handlers.c:574]: dlg_onreply(): dialog 0x7f7c1461e2e8 failed (negative reply) DEBUG: dialog [dlg_cb.c:271]: run_dlg_callbacks(): dialog=0x7f7c1461e2e8, type=4 DEBUG: dialog [dlg_handlers.c:1050]: dlg_set_tm_waitack(): registering TMCB to wait for negative ACK Best Regard, Sammy

1 0

Can MSRP module relay to multiple destinations?
by Sefa Cebe 31 Mar '20

31 Mar '20

Hello, I'm using Kamailio MSRP module as a MSRP relay, It works successfully when I send one-to-one MSRP messages. I am having trouble while sending msrp messages to multiple receivers. My question is that can I use this module to forward msrp messages not just one receiver, but multiple receivers? Can this module be used like MSRP switch? Thanks in advance.

2 3

Kamailio breaks RFC's 'Contact Header'
by Edward Romanenco 31 Mar '20

31 Mar '20

Description I'm running Kamailio 5.2.0, whenever I relay an invite via Kamailio, my original contact header is changed from the original: sip:+XXXXXXXXX@YYY.YYY.YYY.YYYY:5060;transport=udp;gw=netvision To sip:YYY.YYY.YYY.YYY;line=sr-.n274i0TMfsHMcCAlVyAMV5IlgCXvV8n4edQlgIUlgKQ4Vk74gI1LmZ69NM79FZAR3JC.cDNLfHUj3Wnp3MP9nd*. Even when I set it correctly on my route, using: remove_hf("Contact"); append_hf("Contact: sip:$tU@YYY.YYY.YYY.YYY:5060;transport=udp;gw=netvision\r\n", "Contact"); It still ends up being modified. What can I do to keep the contact header as it is? SIP Traffic U YYY.YYY.YYY.YYY:5060 -> 81.24.193.248:5060 INVITE sip:+442033202609@81.24.193.248:5060 SIP/2.0. Record-Route: <sip:YYY.YYY.YYY.YYY;r2=on;lr=on;ftag=mp0S9yH11vryH;vsf=AAAAAAAAAAAAAAAAAAAAAAADCAEACRgPGB8AAy4xNjM->. Record-Route: <sip:2YYY.YYY.YYY.YYY;line=sr-.n274V8TlidQMVyUlg87vV8nlfDXlVHB9VD0.VHB9VDoLGtNRbH7ltlTEkyQl3jXEky1LNMoRkt5ukt5ukt5ukt5ukt5ukt5ukt5ukt5W8M5WktckoLuWAsduktTMm64pCAD>. Via: SIP/2.0/UDP YYY.YYY.YYY.YYY;branch=z9hG4bK53e9.308596b23ed683368534c9d609dce0f6.0. Via: SIP/2.0/UDP YYY.YYY.YYY.YYY;branch=z9hG4bKsr-kA2uvfsUlerJWtIylgCXvV8n4edQlgIUlgKQ4Vk74gI1.oJVjb2njburlgCXvV8n4edQlgIUlgKQ4HWsRbWPLVDX.GrXLcAHlcC74nZXKbTVpcHh4b6mMGZvJgLsLcJTkgtGu2PGgy**. Max-Forwards: 67. From: +18702935016 <sip:+18702935016@YYY.YYY.YYY.YYY>;tag=mp0S9yH11vryH. To: <sip:+442033202609@81.24.193.248>. Call-ID: !!:jbkfMgyHjbsDjblfjqAQlVldvgyHKolDlcIHlcknKVIdjcIT. CSeq: 18182498 INVITE. Contact: <sip:YYY.YYY.YYY.YYY;line=sr-.n274i0TMfsHMcCAlVyAMV5IlgCXvV8n4edQlgIUlgKQ4Vk74gI1LmZ69NM79FZAR3JC.cDNLfHUj3Wnp3MP9nd*>. User-Agent: FreeSWITCH-mod_sofia/1.9.0+git~20180706T160334Z~de3df8dc0e~64bit. Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER, REFER, NOTIFY. Supported: timer, path, replaces. Allow-Events: talk, hold, conference, refer. Content-Type: application/sdp. Content-Disposition: session. Content-Length: 224. Remote-Party-ID: "+18702935016" <sip:+18702935016@YYY.YYY.YYY.YYY>;party=calling;screen=yes;privacy=off. . v=0. o=FreeSWITCH 1585439298 1585439299 IN IP4 ZZZ.ZZZ.ZZZ.ZZZ. s=FreeSWITCH. c=IN IP4 ZZZ.ZZZ

2 3

Re: [SR-Users] How to correctly answer a PnP-SUBSCRIBE message
by Jan-Hendrik Dörner 31 Mar '20

31 Mar '20

Hello Daniel, thank you for your reply. I changed the line mentioned to t_uac_send("NOTIFY", "$(ct{s.substr,1,0}{s.striptail,1})", "$su", "192.168.1.156","Call-ID: $hdr(Call-ID)\r\nSubscription-State: terminated;reason=timeout\r\nEvent: $hdr(Event)\r\nContent-Type: application/url\r\nFrom: $fU\r\nTo: $hdr(From)", "http://server.conf/settings-{mac} <http://server.conf/settings-%7Bmac%7D>"); the result is: 3) Call-ID is fine now ; Problem solved :-) 1) The Via IP is now changed to the IP and port of the server, but not to the IP of the phone. 2) The sending interface / IP is not correct: It now sends _only_ from the wrong IP !! As a result, it repeats sending the NOTIFY-message over and over again since the message does not get to the phone ... Please see the starting of the SIP-traffic below U 192.168.1.152:57283 -> 224.0.1.75:5060 #53 SUBSCRIBE sip:MAC%3a0004137120D8@lan <sip:MAC%3a0004137120D8@lan> SIP/2.0. Via: SIP/2.0/UDP 192.168.1.152:57283;rport. From: <sip:MAC%3a0004137120D8@lan <sip:MAC%3a0004137120D8@lan>>;tag=176419003. To: <sip:MAC%3a0004137120D8@lan <sip:MAC%3a0004137120D8@lan>>. Call-ID: 277773303(a)192.168.1.152 <mailto:277773303@192.168.1.152>. CSeq: 1 SUBSCRIBE. Event: ua-profile;profile-type="device";vendor="snom";model="snom760";version="8.9.3.80". Expires: 0. Accept: application/url. Contact: <sip:192.168.1.152:57283 <sip:192.168.1.152:57283>>. User-Agent: snom760/8.9.3.80. Content-Length: 0. . # U 192.168.1.156:5060 -> 192.168.1.152:57283 #54 SIP/2.0 200 OK. Via: SIP/2.0/UDP 192.168.1.152:57283;rport=57283;received=192.168.1.152. From: <sip:MAC%3a0004137120D8@lan <sip:MAC%3a0004137120D8@lan>>;tag=176419003. To: <sip:MAC%3a0004137120D8@lan <sip:MAC%3a0004137120D8@lan>>;tag=fb721cde02dffb6bb099728401306798.1182. Call-ID: 277773303(a)192.168.1.152 <mailto:277773303@192.168.1.152>. CSeq: 1 SUBSCRIBE. Server: kamailio (5.2.5 (x86_64/linux)). Content-Length: 0. . # U 172.23.56.1:5060 -> 192.168.1.152:57283 #55 NOTIFY sip:192.168.1.152:57283 <sip:192.168.1.152:57283> SIP/2.0. Via: SIP/2.0/UDP 192.168.1.156:5060;branch=z9hG4bKee8f.0ea476a1000000000000000000000000.0. To: <sip:MAC%3a0004137120D8@lan <sip:MAC%3a0004137120D8@lan>>;tag=176419003. From: <MAC%3a0004137120D8>;tag=da567df9df3ac234e43969a051db4641-9700. CSeq: 10 NOTIFY. Call-ID: 277773303(a)192.168.1.152 <mailto:277773303@192.168.1.152>. Max-Forwards: 70. Content-Length: 33. User-Agent: kamailio (5.2.5 (x86_64/linux)). Subscription-State: terminated;reason=timeout. Event: ua-profile;profile-type="device";vendor="snom";model="snom760";version="8.9.3.80". Content-Type: application/url. . http://server.conf/settings-{mac} <http://server.conf/settings-%7Bmac%7D> # U 172.23.56.1:5060 -> 192.168.1.152:57283 #56 NOTIFY sip:192.168.1.152:57283 <sip:192.168.1.152:57283> SIP/2.0. Via: SIP/2.0/UDP 192.168.1.156:5060;branch=z9hG4bKee8f.0ea476a1000000000000000000000000.0. To: <sip:MAC%3a0004137120D8@lan <sip:MAC%3a0004137120D8@lan>>;tag=176419003. From: <MAC%3a0004137120D8>;tag=da567df9df3ac234e43969a051db4641-9700. CSeq: 10 NOTIFY. Call-ID: 277773303(a)192.168.1.152 <mailto:277773303@192.168.1.152>. Max-Forwards: 70. Content-Length: 33. User-Agent: kamailio (5.2.5 (x86_64/linux)). Subscription-State: terminated;reason=timeout. Event: ua-profile;profile-type="device";vendor="snom";model="snom760";version="8.9.3.80". Content-Type: application/url. . http://server.conf/settings-{mac} <http://server.conf/settings-%7Bmac%7D> # U 172.23.56.1:5060 -> 192.168.1.152:57283 #57 NOTIFY sip:192.168.1.152:57283 <sip:192.168.1.152:57283> SIP/2.0. Via: SIP/2.0/UDP 192.168.1.156:5060;branch=z9hG4bKee8f.0ea476a1000000000000000000000000.0. To: <sip:MAC%3a0004137120D8@lan <sip:MAC%3a0004137120D8@lan>>;tag=176419003. From: <MAC%3a0004137120D8>;tag=da567df9df3ac234e43969a051db4641-9700. CSeq: 10 NOTIFY. Call-ID: 277773303(a)192.168.1.152 <mailto:277773303@192.168.1.152>. Max-Forwards: 70. Content-Length: 33. User-Agent: kamailio (5.2.5 (x86_64/linux)). Subscription-State: terminated;reason=timeout. Event: ua-profile;profile-type="device";vendor="snom";model="snom760";version="8.9.3.80". Content-Type: application/url. . http://server.conf/settings-{mac} <http://server.conf/settings-%7Bmac%7D> # U 192.168.1.152:57283 -> 224.0.1.75:5060 #58 SUBSCRIBE sip:MAC%3a0004137120D8@lan <sip:MAC%3a0004137120D8@lan> SIP/2.0. Via: SIP/2.0/UDP 192.168.1.152:57283;rport. From: <sip:MAC%3a0004137120D8@lan <sip:MAC%3a0004137120D8@lan>>;tag=1472545741. To: <sip:MAC%3a0004137120D8@lan <sip:MAC%3a0004137120D8@lan>>. Call-ID: 1886698335(a)192.168.1.152 <mailto:1886698335@192.168.1.152>. CSeq: 1 SUBSCRIBE. Event: ua-profile;profile-type="device";vendor="snom";model="snom760";version="8.9.3.80". Expires: 0. Accept: application/url. Contact: <sip:192.168.1.152:57283 <sip:192.168.1.152:57283>>. User-Agent: snom760/8.9.3.80. Content-Length: 0. . # U 192.168.1.156:5060 -> 192.168.1.152:57283 #59 SIP/2.0 200 OK. Via: SIP/2.0/UDP 192.168.1.152:57283;rport=57283;received=192.168.1.152. From: <sip:MAC%3a0004137120D8@lan <sip:MAC%3a0004137120D8@lan>>;tag=1472545741. To: <sip:MAC%3a0004137120D8@lan <sip:MAC%3a0004137120D8@lan>>;tag=fb721cde02dffb6bb099728401306798.1182. Call-ID: 1886698335(a)192.168.1.152 <mailto:1886698335@192.168.1.152>. CSeq: 1 SUBSCRIBE. Server: kamailio (5.2.5 (x86_64/linux)). Content-Length: 0. . # U 172.23.56.1:5060 -> 192.168.1.152:57283 #60 NOTIFY sip:192.168.1.152:57283 <sip:192.168.1.152:57283> SIP/2.0. Via: SIP/2.0/UDP 192.168.1.156:5060;branch=z9hG4bKa0df.967a0433000000000000000000000000.0. To: <sip:MAC%3a0004137120D8@lan <sip:MAC%3a0004137120D8@lan>>;tag=1472545741. From: <MAC%3a0004137120D8>;tag=da567df9df3ac234e43969a051db4641-d106. CSeq: 10 NOTIFY. Call-ID: 1886698335(a)192.168.1.152 <mailto:1886698335@192.168.1.152>. Max-Forwards: 70. Content-Length: 33. User-Agent: kamailio (5.2.5 (x86_64/linux)). Subscription-State: terminated;reason=timeout. Event: ua-profile;profile-type="device";vendor="snom";model="snom760";version="8.9.3.80". Content-Type: application/url. . http://server.conf/settings-{mac} <http://server.conf/settings-%7Bmac%7D> # U 172.23.56.1:5060 -> 192.168.1.152:57283 #61 NOTIFY sip:192.168.1.152:57283 <sip:192.168.1.152:57283> SIP/2.0. Via: SIP/2.0/UDP 192.168.1.156:5060;branch=z9hG4bKa0df.967a0433000000000000000000000000.0. To: <sip:MAC%3a0004137120D8@lan <sip:MAC%3a0004137120D8@lan>>;tag=1472545741. From: <MAC%3a0004137120D8>;tag=da567df9df3ac234e43969a051db4641-d106. CSeq: 10 NOTIFY. Call-ID: 1886698335(a)192.168.1.152 <mailto:1886698335@192.168.1.152>. Max-Forwards: 70. Content-Length: 33. User-Agent: kamailio (5.2.5 (x86_64/linux)). Subscription-State: terminated;reason=timeout. Event: ua-profile;profile-type="device";vendor="snom";model="snom760";version="8.9.3.80". Content-Type: application/url. . http://server.conf/settings-{mac} <http://server.conf/settings-%7Bmac%7D> # (If I change the IP-parameter to "172.23.56.1" the resulting sending IP is unchanged!) > Am 30.03.2020 um 16:17 schrieb Daniel-Constantin Mierla <miconda(a)gmail.com <mailto:miconda@gmail.com>>: > > Hello, > > On 30.03.20 12:07, Jan-Hendrik Dörner wrote: >> Hallo, >> >> several telephones send a SIP-multicast SUBSCRIBE message to address 224.0.1.75 if they have no settings-URL configured and receive none over DHCP. >> >> So I configure my kamailio server, to respond to that multicast-request. >> But: Although mine is working, I do feel it could be improved, since the NOTIFY packet send out is not quite as it should be … >> >> Here is what I did (the 172.23.56.1 is my voip-vlan-address) >> >> listen=udp:172.23.56.1:5060 advertise 192.168.1.156:5060 >> listen=udp:192.168.1.156:5060 advertise 192.168.1.156:5060 >> listen=tcp:127.0.0.1:5060 >> >> mcast="eth0" >> listen=udp:224.0.1.75:5060 >> >> …. >> >> if ($Ri == "224.0.1.75"){ >> if(is_method("SUBSCRIBE")){ >> xlog("L_INFO", "Received pnp-event from IP $si from User-Agent $hdr(User-Agent) und User $fU\r\n" ); >> sl_send_reply("200", "OK"); >> t_uac_send("NOTIFY", "$(ct{s.substr,1,0}{s.striptail,1})", "", "","Subscription-State: terminated;reason=timeout\r\nEvent: $hdr(Event)\r\nContent-Type: application/url\r\nFrom: $fU\r\nTo: $hdr(From)", "http://server.conf/settings-{mac} <http://server.conf/settings-%7Bmac%7D>"); >> }else { >> xlog("L_INFO", "Drop message $rm from pnp-Interface \r\n" ); >> } >> exit; >> } >> >> >> And here are the SIP-packets I see on my server (192.168.1.156) coming from my snom-phone (192.168.1.152). >> My problems with the NOTIFY -packets are: >> 1) How do I set the Via parameters to be the same as in the OK-reply? > > Try to set the next hop address to "$su" and combined with 2) maybe it > results in what you want to get. > > >> 2) How do I send out the NOTIFY only via the 192.168.1.156 network interface? > > Set the local socket parameter from where to send the NOTIFY. > > >> 3) May I send out the NOTIFY with the Call-ID from the SUBSCRIBE message? How? > > > Provide the Call-Id haeder as part of the headers parameter: > > - > https://www.kamailio.org/docs/modules/stable/modules/tm.html#tm.f.t_uac_send <https://www.kamailio.org/docs/modules/stable/modules/tm.html#tm.f.t_uac_send> > > Cheers, > Daniel > > >> >> Any help is highly appreciated >> Jan-Hendrik >> >> # >> U 192.168.1.152:58714 -> 224.0.1.75:5060 #258 >> SUBSCRIBE sip:MAC%3a0004137120D8@lan <sip:MAC%3a0004137120D8@lan> SIP/2.0. >> Via: SIP/2.0/UDP 192.168.1.152:58714;rport. >> From: <sip:MAC%3a0004137120D8@lan <sip:MAC%3a0004137120D8@lan>>;tag=1750588964. >> To: <sip:MAC%3a0004137120D8@lan <sip:MAC%3a0004137120D8@lan>>. >> Call-ID: 1395386659(a)192.168.1.152 <mailto:1395386659@192.168.1.152>. >> CSeq: 1 SUBSCRIBE. >> Event: ua-profile;profile-type="device";vendor="snom";model="snom760";version="8.9.3.80". >> Expires: 0. >> Accept: application/url. >> Contact: <sip:192.168.1.152:58714 <sip:192.168.1.152:58714>>. >> User-Agent: snom760/8.9.3.80. >> Content-Length: 0. >> . >> >> # >> U 192.168.1.156:5060 -> 192.168.1.152:58714 #259 >> SIP/2.0 200 OK. >> Via: SIP/2.0/UDP 192.168.1.152:58714;rport=58714;received=192.168.1.152. >> From: <sip:MAC%3a0004137120D8@lan <sip:MAC%3a0004137120D8@lan>>;tag=1750588964. >> To: <sip:MAC%3a0004137120D8@lan <sip:MAC%3a0004137120D8@lan>>;tag=fb721cde02dffb6bb099728401306798.2f00. >> Call-ID: 1395386659(a)192.168.1.152 <mailto:1395386659@192.168.1.152>. >> CSeq: 1 SUBSCRIBE. >> Server: kamailio (5.2.5 (x86_64/linux)). >> Content-Length: 0. >> . >> >> # >> U 192.168.1.156:5060 -> 192.168.1.152:58714 #260 >> NOTIFY sip:192.168.1.152:58714 <sip:192.168.1.152:58714> SIP/2.0. >> Via: SIP/2.0/UDP 224.0.1.75;branch=z9hG4bKf21c.917eaf36000000000000000000000000.0. >> To: <sip:MAC%3a0004137120D8@lan <sip:MAC%3a0004137120D8@lan>>;tag=1750588964. >> From: <MAC%3a0004137120D8>;tag=da567df9df3ac234e43969a051db4641-8cfb. >> CSeq: 10 NOTIFY. >> Call-ID: 24eaa8de01be1768-70960(a)172.23.56.1 <mailto:24eaa8de01be1768-70960@172.23.56.1>. >> Max-Forwards: 70. >> Content-Length: 33. >> User-Agent: kamailio (5.2.5 (x86_64/linux)). >> Subscription-State: terminated;reason=timeout. >> Event: ua-profile;profile-type="device";vendor="snom";model="snom760";version="8.9.3.80". >> Content-Type: application/url. >> . >> http://server.conf/settings-{mac} <http://server.conf/settings-%7Bmac%7D> >> # >> U 172.23.56.1:5060 -> 192.168.1.152:58714 #261 >> NOTIFY sip:192.168.1.152:58714 SIP/2.0. >> Via: SIP/2.0/UDP 224.0.1.75;branch=z9hG4bKf21c.917eaf36000000000000000000000000.0. >> To: <sip:MAC%3a0004137120D8@lan>;tag=1750588964. >> From: <MAC%3a0004137120D8>;tag=da567df9df3ac234e43969a051db4641-8cfb. >> CSeq: 10 NOTIFY. >> Call-ID: 24eaa8de01be1768-70960(a)172.23.56.1. >> Max-Forwards: 70. >> Content-Length: 33. >> User-Agent: kamailio (5.2.5 (x86_64/linux)). >> Subscription-State: terminated;reason=timeout. >> Event: ua-profile;profile-type="device";vendor="snom";model="snom760";version="8.9.3.80". >> Content-Type: application/url. >> . >> http://server.conf/settings-{mac} >> # >> U 172.23.56.1:5060 -> 192.168.1.152:58714 #262 >> NOTIFY sip:192.168.1.152:58714 SIP/2.0. >> Via: SIP/2.0/UDP 224.0.1.75;branch=z9hG4bKf21c.917eaf36000000000000000000000000.0. >> To: <sip:MAC%3a0004137120D8@lan>;tag=1750588964. >> From: <MAC%3a0004137120D8>;tag=da567df9df3ac234e43969a051db4641-8cfb. >> CSeq: 10 NOTIFY. >> Call-ID: 24eaa8de01be1768-70960(a)172.23.56.1. >> Max-Forwards: 70. >> Content-Length: 33. >> User-Agent: kamailio (5.2.5 (x86_64/linux)). >> Subscription-State: terminated;reason=timeout. >> Event: ua-profile;profile-type="device";vendor="snom";model="snom760";version="8.9.3.80". >> Content-Type: application/url. >> . >> http://server.conf/settings-{mac} >> # >> U 192.168.1.152:58714 -> 224.0.1.75:5060 #263 >> SUBSCRIBE sip:MAC%3a0004137120D8@lan SIP/2.0. >> Via: SIP/2.0/UDP 192.168.1.152:58714;rport. >> From: <sip:MAC%3a0004137120D8@lan>;tag=1971605806. >> To: <sip:MAC%3a0004137120D8@lan>. >> Call-ID: 1846532696(a)192.168.1.152. >> CSeq: 1 SUBSCRIBE. >> Event: ua-profile;profile-type="device";vendor="snom";model="snom760";version="8.9.3.80". >> Expires: 0. >> Accept: application/url. >> Contact: <sip:192.168.1.152:58714>. >> User-Agent: snom760/8.9.3.80. >> Content-Length: 0. >> . >> >> # >> U 192.168.1.156:5060 -> 192.168.1.152:58714 #264 >> SIP/2.0 200 OK. >> Via: SIP/2.0/UDP 192.168.1.152:58714;rport=58714;received=192.168.1.152. >> From: <sip:MAC%3a0004137120D8@lan>;tag=1971605806. >> To: <sip:MAC%3a0004137120D8@lan>;tag=fb721cde02dffb6bb099728401306798.2f00. >> Call-ID: 1846532696(a)192.168.1.152. >> CSeq: 1 SUBSCRIBE. >> Server: kamailio (5.2.5 (x86_64/linux)). >> Content-Length: 0. >> . >> >> # >> U 192.168.1.156:5060 -> 192.168.1.152:58714 #265 >> NOTIFY sip:192.168.1.152:58714 SIP/2.0. >> Via: SIP/2.0/UDP 224.0.1.75;branch=z9hG4bK201a.063839a4000000000000000000000000.0. >> To: <sip:MAC%3a0004137120D8@lan>;tag=1971605806. >> From: <MAC%3a0004137120D8>;tag=da567df9df3ac234e43969a051db4641-f31b. >> CSeq: 10 NOTIFY. >> Call-ID: 24eaa8de01be1768-70963(a)172.23.56.1. >> Max-Forwards: 70. >> Content-Length: 33. >> User-Agent: kamailio (5.2.5 (x86_64/linux)). >> Subscription-State: terminated;reason=timeout. >> Event: ua-profile;profile-type="device";vendor="snom";model="snom760";version="8.9.3.80". >> Content-Type: application/url. >> . >> http://server.conf/settings-{mac} >> # >> U 192.168.1.152:58714 -> 192.168.1.156:5060 #266 >> SIP/2.0 200 Ok. >> Via: SIP/2.0/UDP 224.0.1.75;branch=z9hG4bKf21c.917eaf36000000000000000000000000.0;received=192.168.1.156. >> From: <MAC:0004137120D8>;tag=da567df9df3ac234e43969a051db4641-8cfb. >> To: <sip:MAC%3A0004137120D8@lan>;tag=1750588964. >> Call-ID: 24eaa8de01be1768-70960(a)172.23.56.1. >> CSeq: 10 NOTIFY. >> User-Agent: snom760/8.9.3.80. >> Content-Length: 0. >> . >> >> # >> U 192.168.1.152:58714 -> 192.168.1.156:5060 #267 >> SIP/2.0 200 Ok. >> Via: SIP/2.0/UDP 224.0.1.75;branch=z9hG4bKf21c.917eaf36000000000000000000000000.0;received=192.168.1.156. >> From: <MAC:0004137120D8>;tag=da567df9df3ac234e43969a051db4641-8cfb. >> To: <sip:MAC%3A0004137120D8@lan>;tag=1750588964. >> Call-ID: 24eaa8de01be1768-70960(a)172.23.56.1. >> CSeq: 10 NOTIFY. >> User-Agent: snom760/8.9.3.80. >> Content-Length: 0. >> . >> >> # >> U 192.168.1.152:58714 -> 192.168.1.156:5060 #268 >> SIP/2.0 200 Ok. >> Via: SIP/2.0/UDP 224.0.1.75;branch=z9hG4bK201a.063839a4000000000000000000000000.0;received=192.168.1.156. >> From: <MAC:0004137120D8>;tag=da567df9df3ac234e43969a051db4641-f31b. >> To: <sip:MAC%3A0004137120D8@lan>;tag=1971605806. >> Call-ID: 24eaa8de01be1768-70963(a)172.23.56.1. >> CSeq: 10 NOTIFY. >> User-Agent: snom760/8.9.3.80. >> Content-Length: 0. >> . >> >> >> _______________________________________________ >> Kamailio (SER) - Users Mailing List >> sr-users(a)lists.kamailio.org <mailto:sr-users@lists.kamailio.org> >> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users <https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users> > > -- > Daniel-Constantin Mierla -- www.asipto.com <http://www.asipto.com/> > www.twitter.com/miconda <http://www.twitter.com/miconda> -- www.linkedin.com/in/miconda <http://www.linkedin.com/in/miconda>

2 4

P-CSCF Error - help required asap
by Pavithra N M 30 Mar '20

30 Mar '20

Hi, I am facing the below error in my P-CSCF module as i am running P-CSCF, I-CSCF, S-CSCF, HSS in separate VMs. 0(3512) INFO: <core> [core/udp_server.c:206]: probe_max_receive_buffer(): SO_RCVBUF is finally 425984 0(3512) ERROR: <script>: event_route[htable:mod-init] { 1(3513) ERROR: rtpengine [rtpengine.c:2839]: send_rtpp_command(): can't send command "ping" to RTP proxy <udp:localhost:9910> 1(3513) ERROR: rtpengine [rtpengine.c:2740]: rtpp_test(): proxy did not respond to ping 1(3513) ERROR: rtpengine [rtpengine.c:2839]: send_rtpp_command(): can't send command "ping" to RTP proxy <udp:localhost:9911> 1(3513) ERROR: rtpengine [rtpengine.c:2740]: rtpp_test(): proxy did not respond to ping 68(3637) INFO: ctl [io_listener.c:214]: io_listen_loop(): io_listen_loop: using epoll_lt io watch method (config) 72(3644) WARNING: ims_usrloc_pcscf [usrloc_db.c:67]: connect_db(): DB connection already open... continuing 73(3645) WARNING: ims_usrloc_pcscf [usrloc_db.c:67]: connect_db(): DB connection already open... continuing 69(3641) WARNING: ims_usrloc_pcscf [usrloc_db.c:67]: connect_db(): DB connection already open... continuing 75(3653) WARNING: ims_usrloc_pcscf [usrloc_db.c:67]: connect_db(): DB connection already open... continuing 71(3643) INFO: jsonrpcs [jsonrpcs_sock.c:443]: jsonrpc_dgram_process(): a new child 0/3643 77(3655) WARNING: ims_usrloc_pcscf [usrloc_db.c:67]: connect_db(): DB connection already open... continuing 76(3654) WARNING: ims_usrloc_pcscf [usrloc_db.c:67]: connect_db(): DB connection already open... continuing 74(3652) WARNING: ims_usrloc_pcscf [usrloc_db.c:67]: connect_db(): DB connection already open... continuing 79(3657) WARNING: ims_usrloc_pcscf [usrloc_db.c:67]: connect_db(): DB connection already open... continuing root@tel-VirtualBox:/etc/kamailio/pcscf# 78(3656) WARNING: ims_usrloc_pcscf [usrloc_db.c:67]: connect_db(): DB connection already open... continuing 69(3641) ERROR: *** cfgtrace:request_route=[NATPING] c=[/etc/kamailio/pcscf/kamailio.cfg] l=836 a=5 n=route 69(3641) ERROR: *** cfgtrace:request_route=[preload_pcscf] c=[/etc/kamailio/pcscf/kamailio.cfg] l=895 a=16 n=if 69(3641) ERROR: *** cfgtrace:request_route=[preload_pcscf] c=[/etc/kamailio/pcscf/kamailio.cfg] l=895 a=63 n=assign 69(3641) ERROR: *** cfgtrace:request_route=[preload_pcscf] c=[/etc/kamailio/pcscf/kamailio.cfg] l=897 a=27 n=sql_query 69(3641) ERROR: *** cfgtrace:request_route=[preload_pcscf] c=[/etc/kamailio/pcscf/kamailio.cfg] l=898 a=25 n=xlog 69(3641) ERROR: <script>: Preloading NAT-PING. Rows: 0 69(3641) ERROR: *** cfgtrace:request_route=[preload_pcscf] c=[/etc/kamailio/pcscf/kamailio.cfg] kindly help me in this issue of how to configure the rtp proxy or even if it is not required for basic configuration,let me know the procedure to comment this part or the procedure to take it forward to run P-CSCF without any errors. Kindly help me in this regard. Thanks Best Regards Pavithra M Tata Elxsi [cid:7ca5c450-5bb2-4d74-85ab-1c3e16346e2e] ________________________________ Disclaimer: This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you are not the intended recipient of this message , or if this message has been addressed to you in error, please immediately alert the sender by reply email and then delete this message and any attachments. If you are not the intended recipient, you are hereby notified that any use, dissemination, copying, or storage of this message or its attachments is strictly prohibited. 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, omissions or contaminations in the contents of this message which might have occurred as a result of email transmission. If verification is required, please request for a hard-copy version. ________________________________

1 0

How to correctly answer a PnP-SUBSCRIBE message
by Jan-Hendrik Dörner 30 Mar '20

30 Mar '20

Hallo, several telephones send a SIP-multicast SUBSCRIBE message to address 224.0.1.75 if they have no settings-URL configured and receive none over DHCP. So I configure my kamailio server, to respond to that multicast-request. But: Although mine is working, I do feel it could be improved, since the NOTIFY packet send out is not quite as it should be … Here is what I did (the 172.23.56.1 is my voip-vlan-address) listen=udp:172.23.56.1:5060 advertise 192.168.1.156:5060 listen=udp:192.168.1.156:5060 advertise 192.168.1.156:5060 listen=tcp:127.0.0.1:5060 mcast="eth0" listen=udp:224.0.1.75:5060 …. if ($Ri == "224.0.1.75"){ if(is_method("SUBSCRIBE")){ xlog("L_INFO", "Received pnp-event from IP $si from User-Agent $hdr(User-Agent) und User $fU\r\n" ); sl_send_reply("200", "OK"); t_uac_send("NOTIFY", "$(ct{s.substr,1,0}{s.striptail,1})", "", "","Subscription-State: terminated;reason=timeout\r\nEvent: $hdr(Event)\r\nContent-Type: application/url\r\nFrom: $fU\r\nTo: $hdr(From)", "http://server.conf/settings-{mac}"); }else { xlog("L_INFO", "Drop message $rm from pnp-Interface \r\n" ); } exit; } And here are the SIP-packets I see on my server (192.168.1.156) coming from my snom-phone (192.168.1.152). My problems with the NOTIFY -packets are: 1) How do I set the Via parameters to be the same as in the OK-reply? 2) How do I send out the NOTIFY only via the 192.168.1.156 network interface? 3) May I send out the NOTIFY with the Call-ID from the SUBSCRIBE message? How? Any help is highly appreciated Jan-Hendrik # U 192.168.1.152:58714 -> 224.0.1.75:5060 #258 SUBSCRIBE sip:MAC%3a0004137120D8@lan SIP/2.0. Via: SIP/2.0/UDP 192.168.1.152:58714;rport. From: <sip:MAC%3a0004137120D8@lan>;tag=1750588964. To: <sip:MAC%3a0004137120D8@lan>. Call-ID: 1395386659(a)192.168.1.152. CSeq: 1 SUBSCRIBE. Event: ua-profile;profile-type="device";vendor="snom";model="snom760";version="8.9.3.80". Expires: 0. Accept: application/url. Contact: <sip:192.168.1.152:58714>. User-Agent: snom760/8.9.3.80. Content-Length: 0. . # U 192.168.1.156:5060 -> 192.168.1.152:58714 #259 SIP/2.0 200 OK. Via: SIP/2.0/UDP 192.168.1.152:58714;rport=58714;received=192.168.1.152. From: <sip:MAC%3a0004137120D8@lan>;tag=1750588964. To: <sip:MAC%3a0004137120D8@lan>;tag=fb721cde02dffb6bb099728401306798.2f00. Call-ID: 1395386659(a)192.168.1.152. CSeq: 1 SUBSCRIBE. Server: kamailio (5.2.5 (x86_64/linux)). Content-Length: 0. . # U 192.168.1.156:5060 -> 192.168.1.152:58714 #260 NOTIFY sip:192.168.1.152:58714 SIP/2.0. Via: SIP/2.0/UDP 224.0.1.75;branch=z9hG4bKf21c.917eaf36000000000000000000000000.0. To: <sip:MAC%3a0004137120D8@lan>;tag=1750588964. From: <MAC%3a0004137120D8>;tag=da567df9df3ac234e43969a051db4641-8cfb. CSeq: 10 NOTIFY. Call-ID: 24eaa8de01be1768-70960(a)172.23.56.1. Max-Forwards: 70. Content-Length: 33. User-Agent: kamailio (5.2.5 (x86_64/linux)). Subscription-State: terminated;reason=timeout. Event: ua-profile;profile-type="device";vendor="snom";model="snom760";version="8.9.3.80". Content-Type: application/url. . http://server.conf/settings-{mac} # U 172.23.56.1:5060 -> 192.168.1.152:58714 #261 NOTIFY sip:192.168.1.152:58714 SIP/2.0. Via: SIP/2.0/UDP 224.0.1.75;branch=z9hG4bKf21c.917eaf36000000000000000000000000.0. To: <sip:MAC%3a0004137120D8@lan>;tag=1750588964. From: <MAC%3a0004137120D8>;tag=da567df9df3ac234e43969a051db4641-8cfb. CSeq: 10 NOTIFY. Call-ID: 24eaa8de01be1768-70960(a)172.23.56.1. Max-Forwards: 70. Content-Length: 33. User-Agent: kamailio (5.2.5 (x86_64/linux)). Subscription-State: terminated;reason=timeout. Event: ua-profile;profile-type="device";vendor="snom";model="snom760";version="8.9.3.80". Content-Type: application/url. . http://server.conf/settings-{mac} # U 172.23.56.1:5060 -> 192.168.1.152:58714 #262 NOTIFY sip:192.168.1.152:58714 SIP/2.0. Via: SIP/2.0/UDP 224.0.1.75;branch=z9hG4bKf21c.917eaf36000000000000000000000000.0. To: <sip:MAC%3a0004137120D8@lan>;tag=1750588964. From: <MAC%3a0004137120D8>;tag=da567df9df3ac234e43969a051db4641-8cfb. CSeq: 10 NOTIFY. Call-ID: 24eaa8de01be1768-70960(a)172.23.56.1. Max-Forwards: 70. Content-Length: 33. User-Agent: kamailio (5.2.5 (x86_64/linux)). Subscription-State: terminated;reason=timeout. Event: ua-profile;profile-type="device";vendor="snom";model="snom760";version="8.9.3.80". Content-Type: application/url. . http://server.conf/settings-{mac} # U 192.168.1.152:58714 -> 224.0.1.75:5060 #263 SUBSCRIBE sip:MAC%3a0004137120D8@lan SIP/2.0. Via: SIP/2.0/UDP 192.168.1.152:58714;rport. From: <sip:MAC%3a0004137120D8@lan>;tag=1971605806. To: <sip:MAC%3a0004137120D8@lan>. Call-ID: 1846532696(a)192.168.1.152. CSeq: 1 SUBSCRIBE. Event: ua-profile;profile-type="device";vendor="snom";model="snom760";version="8.9.3.80". Expires: 0. Accept: application/url. Contact: <sip:192.168.1.152:58714>. User-Agent: snom760/8.9.3.80. Content-Length: 0. . # U 192.168.1.156:5060 -> 192.168.1.152:58714 #264 SIP/2.0 200 OK. Via: SIP/2.0/UDP 192.168.1.152:58714;rport=58714;received=192.168.1.152. From: <sip:MAC%3a0004137120D8@lan>;tag=1971605806. To: <sip:MAC%3a0004137120D8@lan>;tag=fb721cde02dffb6bb099728401306798.2f00. Call-ID: 1846532696(a)192.168.1.152. CSeq: 1 SUBSCRIBE. Server: kamailio (5.2.5 (x86_64/linux)). Content-Length: 0. . # U 192.168.1.156:5060 -> 192.168.1.152:58714 #265 NOTIFY sip:192.168.1.152:58714 SIP/2.0. Via: SIP/2.0/UDP 224.0.1.75;branch=z9hG4bK201a.063839a4000000000000000000000000.0. To: <sip:MAC%3a0004137120D8@lan>;tag=1971605806. From: <MAC%3a0004137120D8>;tag=da567df9df3ac234e43969a051db4641-f31b. CSeq: 10 NOTIFY. Call-ID: 24eaa8de01be1768-70963(a)172.23.56.1. Max-Forwards: 70. Content-Length: 33. User-Agent: kamailio (5.2.5 (x86_64/linux)). Subscription-State: terminated;reason=timeout. Event: ua-profile;profile-type="device";vendor="snom";model="snom760";version="8.9.3.80". Content-Type: application/url. . http://server.conf/settings-{mac} # U 192.168.1.152:58714 -> 192.168.1.156:5060 #266 SIP/2.0 200 Ok. Via: SIP/2.0/UDP 224.0.1.75;branch=z9hG4bKf21c.917eaf36000000000000000000000000.0;received=192.168.1.156. From: <MAC:0004137120D8>;tag=da567df9df3ac234e43969a051db4641-8cfb. To: <sip:MAC%3A0004137120D8@lan>;tag=1750588964. Call-ID: 24eaa8de01be1768-70960(a)172.23.56.1. CSeq: 10 NOTIFY. User-Agent: snom760/8.9.3.80. Content-Length: 0. . # U 192.168.1.152:58714 -> 192.168.1.156:5060 #267 SIP/2.0 200 Ok. Via: SIP/2.0/UDP 224.0.1.75;branch=z9hG4bKf21c.917eaf36000000000000000000000000.0;received=192.168.1.156. From: <MAC:0004137120D8>;tag=da567df9df3ac234e43969a051db4641-8cfb. To: <sip:MAC%3A0004137120D8@lan>;tag=1750588964. Call-ID: 24eaa8de01be1768-70960(a)172.23.56.1. CSeq: 10 NOTIFY. User-Agent: snom760/8.9.3.80. Content-Length: 0. . # U 192.168.1.152:58714 -> 192.168.1.156:5060 #268 SIP/2.0 200 Ok. Via: SIP/2.0/UDP 224.0.1.75;branch=z9hG4bK201a.063839a4000000000000000000000000.0;received=192.168.1.156. From: <MAC:0004137120D8>;tag=da567df9df3ac234e43969a051db4641-f31b. To: <sip:MAC%3A0004137120D8@lan>;tag=1971605806. Call-ID: 24eaa8de01be1768-70963(a)172.23.56.1. CSeq: 10 NOTIFY. User-Agent: snom760/8.9.3.80. Content-Length: 0. .

2 1

Jump to page:

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