sr-users March 2020

sr-users@lists.kamailio.org

64 participants
80 discussions

doubt about xflags
by David Escartin 22 Apr '20

22 Apr '20

Dear all one quick question, reading the module corex doc, seems that xflag are message(transaction) flags. But I made a test and seems for some reason the flag is not seeing activated at the onreply_route, when it's activated on the request route. Seemed more like a script flag behaviour. Maybe I'm missing something? thanks a lot and regards david

2 8

[kamailio][webrtc issue]
by Bilal Abbasi 07 Apr '20

07 Apr '20

Hi Users, I am new to kamailio, and trying to implement webrtc on kamailio, i am getting following error when i try to login from tryjssip page. Mar 29 21:11:15 kamailio kamailio[20570]: ERROR: <core> [core/tcp_read.c:1535]: tcp_read_req(): bad request, state=7, error=4 buf:#012GET / HTTP/1.1#015#012Host: kamailio..com:7443#015#012Connection: Upgrade#015#012Pragma: no-cache#015#012Cache-Control: no-cache#015#012User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.149 Safari/537.36#015#012Upgrade: websocket#015#012Origin: https://tryit.jssip.net#015#012Sec-WebSocket-Version: 13#015#012Accept-Encoding: gzip, deflate, br#015#012Accept-Language: en-US,en;q=0.9,ur;q=0.8#015#012Sec-WebSocket-Key: 88fVCzdsvQPCrwV7gMrWaA==#015#012Sec-WebSocket-Extensions: permessage-deflate; client_max_window_bits#015#012Sec-WebSocket-Protocol: sip#015#012#015#012#012parsed:#012GET / HTTP/1.1#015#012Host: kamailio..com:7443#015#012Connection: Upgrade#015#012Pragma: no-cache#015#012Cache-Control: no-cache#015#012User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.149 Safari/537.36#015#012Upgrade: websocket#015#012Origin: https://tryit.jssip.net#015#012Sec-WebSocket-Version: 13#015#012Accept-Encoding: gzip, deflate, br#015#012Accept-Language: en-US,en;q=0.9,ur;q=0.8#015#012Sec-WebSocket-Key: 88fVCzdsvQPCrwV7gMrWaA==#015#012Sec-WebSocket-Extensions: permessage-deflate; client_max_window_bits#015#012Sec-WebSocket-Protocol: sip I can see following error on chrome console. WebSocket connection to 'wss://kamailio..com:7443/' failed: Connection closed before receiving a handshake response I tried to set tcp_accept_no_cl to value 'no' and this did not helped me either. Can someone please help me with the issue Regards Bilal Abbasi

3 7

Problem with max tcp connections
by Jose Fco. Irles Durá 06 Apr '20

06 Apr '20

Hi I have a kamailio 5.1.2 as load balancer and registration offloading, but I have a problem with the max tcp connections that it can handle. I suspect that is a linux limit, but I don't find the reason or config. When that limit arrives, I can't connect to kamailio and I receive "Connection reset by peer", but I can't view any error message in the logs. If I check the connections in kamailio, I view that it have "free" connections: # kamctl kamcmd core.tcp_info { readers: 8 max_connections: 4096 max_tls_connections: 2048 opened_connections: 2655 opened_tls_connections: 0 write_queued_bytes: 0 } I have this configs in kamailio.conf (related to tcp) disable_tcp=no tcp_connection_lifetime=3610 tcp_connect_timeout=5 tcp_crlf_ping=yes tcp_accept_aliases=no tcp_keepalive=yes tcp_keepidle=5 tcp_rd_buf_size=65536 tcp_conn_wq_max=131072 mlock_pages=yes shm_force_alloc=yes tcp_max_connections=4096 The shm memory to 256 and the pkg memory to 32. And, following this doc: https://github.com/kamailio/kamailio/blob/master/doc/tutorials/tcp_tunning.… I have setted this values: net.ipv4.ip_local_port_range = 1024 65535 net.core.somaxconn = 65535 net.core.netdev_max_backlog = 182757 Also, I had checked the limits for the main process pid: Limit Soft Limit Hard Limit Units Max cpu time unlimited unlimited seconds Max file size unlimited unlimited bytes Max data size unlimited unlimited bytes Max stack size 8388608 unlimited bytes Max core file size unlimited unlimited bytes Max resident set unlimited unlimited bytes Max processes unlimited unlimited processes Max open files 1048576 1048576 files Max locked memory 16777216 16777216 bytes Max address space unlimited unlimited bytes Max file locks unlimited unlimited locks Max pending signals 386297 386297 signals Max msgqueue size 819200 819200 bytes Max nice priority 0 0 Max realtime priority 0 0 Max realtime timeout unlimited unlimited us The service is running inside a lxc container, without any resource limit, connected to the outside word throught macvlan interface. Where can I find problem source? Best regards

4 13

need help with RTPProxy in bridged mode
by Grant Bagdasarian 04 Apr '20

04 Apr '20

Hello, I'm using RTPproxy for the first time in bridged mode and I can't get kamailio/rtpproxy to rewrite the c parameter to the correct public ip address of kamailio. The setup is as following: Carrier ------[fiber]------ Kamailio ---------[lan]--------- Freeswitch Kamailio is listening on two interfaces: 1) Private: 172.0.0.1 2) Public: 192.168.0.1 (since we have a dedicated fiber with our carrier, this is its public address) Freeswitch is listening on: 1) 172.0.0.2 Carrier is on: 1) 10.0.0.1 I've started an rtpproxy instance on the Kamailio box using: rtpproxy -s udp:127.0.0.1:7721 -u rtpproxy rtpproxy -p /var/run/rtpproxy/rtpproxy.pid -l 192.168.0.1 172.0.0.1 I've played around with rtpproxy_manage() and the various flags (ie, ei), but I can't get kamailio to set the correct public IP when the 200 OK has to be sent back to the carrier. It always sets it to its private address, instead of its public address. I'm using Kamailio 4.2 with sippy/rtpproxy 2.0. Could someone please point me into the right direction? Thanks! Grant

4 8

[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

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

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 March 2020