- sr-users - kamailio.org

Job Offering: Software Engineer & Dev-Ops for VoIP & IMS
by Carsten Bock 22 Mar '19

22 Mar '19

Hi everyone, due to our ongoing growth in the area of mobile network infrastructure, we are currently looking into expanding our team. We are especially looking for: - Software Engineer VoIP & IMS ( https://www.ng-voice.com/software-engineer-voip-ims) - Dev-Ops (VoIP & IMS) (https://www.ng-voice.com/dev-ops-voip-ims) About us ng-voice was founded by a team of leading open-source and VoIP pioneers and passionate coders to develop software for mobile network operators. Our virtualized, cloud native solutions allow entrepreneurial-thinking mobile network operators to become software-centric and offer voice services on any 4G, 5G, WiFi or any other data network – from regular mobile network operators to private networks in remote areas. We are growing the team both in Hamburg and Berlin and are looking for new colleagues to join us. Your responsibilities • Help us deploying and integrating our software solutions • Have fun testing, validating and optimizing our solutions • Enjoy building things and solving complex problems • Proactively identify ways to unlock operational efficiency • Take care of your teammates and have fun growing a company Our requirements We are more interested in your experience and knowledge than in formal degrees: • Strong interest in telephony • Experience with signalling standards (e.g. SIP, DIAMETER) • Fluent in English • Efficient at driving deadlines and keeping yourself and others on topic Our technology stack • Docker; experience with Docker Swarm and Kubernetes is beneficial • Kamailio, RTPEngine, FreeSwitch • Redis, MySQL and RabbitMQ • SIP, RTP, DIAMETER What we offer • Flexible working hours and great office locations (Berlin and Hamburg) • Entrepreneurial culture and flat hierarchies • High degree of autonomy and no dress code • Competitive salary Please send your application to jobs(a)ng-voice.com. Let us know how your profile fits our requirements. And please let us know the earliest date you could join us plus your salary expectations. We look forward to getting to know you! Thanks, Carsten -- Carsten Bock I Managing Director ng-voice GmbH Millerntorplatz 1 I 20359 Hamburg I Germany www.ng-voice.com Mobile +49 (0)179-20 21 244 I Direct +49 (0)40-52 47 593-40 I Fax +49 (0)40-52 47 593-99 Sitz der Gesellschaft: Hamburg Registergericht: Amtsgericht Hamburg, HRB 120189 Geschäftsführer: Carsten Bock, Dr. David Bachmann Ust-ID: DE279344284 Hier finden Sie unsere handelsrechtlichen Pflichtangaben: http://www.ng-voice.com/imprint/

1 0

How can one change acc table name in Kamailio.cfg
by Z 22 Mar '19

22 Mar '19

For some reason these two modparams are always ignored. The table name used is always acc which is default name. How can I change the table name? loadmodule "acc.so" modparam("acc", "db_table_acc", "*acc_$time(year)_$time(mon)*") modparam("acc", "db_table_missed_calls", "*acc_$time(year)_$time(mon)*") Accounting works as expected otherwise. Appreciate any help. Thanks.

3 6

Re: [SR-Users] Problem at Rx Interface - kamailio P-CSCF 5.1.6
by Valentin Christoph 20 Mar '19

20 Mar '19

Hi all, Remember this question from 23.1. It's solved now, thanks for help:-) All the best Christoph Von meinem Samsung Galaxy Smartphone gesendet. -------- Ursprüngliche Nachricht -------- Von: Valentin Christoph <Christoph.Valentin(a)kapsch.net> Datum: 23.01.19 15:06 (GMT+01:00) An: sr-users(a)lists.sip-router.org Cc: Scherney Theodor <Theodor.Scherney(a)kapsch.net>, Onic Roman <Roman.Onic(a)kapsch.net> Betreff: [SR-Users] Problem at Rx Interface - kamailio P-CSCF 5.1.6 Hi all, We are using kamailio 5.1.6, configured as P-CSCF, facing following problem. Please indicate, if you need further information – e.g. I could provide a tshark trace. If during call setup (by simulated UAs) at the terminating P-CSCF the simulated PCRF rejects the Diameter AAR message, then the kamailio P-CSCF runs into a questionable behaviour. By calling the Rx_AAR() function in configuration, the processing of the 200 OK is suspended (by the ims_qos module) and then resumed with the receipt of the AAA message. Now the ims_dialog module is called with the dlg_terminate(“all”, “reason”) function, but the 200 OK has not yet been sent. The ims_dialog sends CANCEL downstream and 488 upstream. However, the 200 OK is sent additionally. We would rather have expected the ims_dialog module should send BYE in both directions. When we respond the CANCEL with 481 Call/Transaction does not exist (which we MUST according to RFC 3261), then we would expect the ims_dialog module at least now to react with BYE in both directions. Could you help? What’s our misunderstanding? How could we proceed to get this issue fixed? Kind regards Christoph P.S.: This is a retransmission, because the original message did not pass moderator approval due to the attached tshark trace The information contained in this e-mail message is privileged and confidential and is for the exclusive use of the addressee. The person who receives this message and who is not the addressee, one of his employees or an agent entitled to hand it over to the addressee, is informed that he may not use, disclose or reproduce the contents thereof, and is kindly asked to notify the sender and delete the e-mail immediately.

1 0

IMS: ims_isc, ims_registrar_scscf: some additions for 3rd party registration
by Valentin Christoph 20 Mar '19

20 Mar '19

Dear all, Dear Daniel, We had implemented a few additions for third party registration, based on kamailio 5.1.0 IMS modules. * either service info OR original REGISTER request or original 200 OK can be added as body to the 3rd party Registration Request, if indicated by the HSS in the user data * change: S-CSCF does not check for TEL URI, before it sends P-Associated URI to AS (SIP URIs are also sent) We would like to provide a pull request within the next days or week to have the changes as basis for a change in release 5.3.x. Drawback: probably our solution would need to be slightly modified, because we removed the check for TEL URI, if the S-CSCF sends the P-Associated-URI header to the AS in the 3rd party register request (maybe introduce a module parameter?). Any comments? Would it be reviewed and maybe taken for 5.3? All the best Christoph ____ Christoph VALENTIN Software Developer | R&D Core / SIP Core P +43 50 811 3785 | M +43 664 628 3785 christoph.valentin(a)kapsch.net<mailto:christoph.valentin@kapsch.net> Kapsch CarrierCom AG | Lehrbachgasse 11 | 1120 Vienna | Austria Company Register at: Commercial Court Vienna FN 223804 z | Registered Office Vienna | www.kapsch.net<http://www.kapsch.net/> [Kapsch Logo]<https://www.kapsch.net/> The information contained in this e-mail message is privileged and confidential and is for the exclusive use of the addressee. The person who receives this message and who is not the addressee, one of his employees or an agent entitled to hand it over to the addressee, is informed that he may not use, disclose or reproduce the contents thereof, and is kindly asked to notify the sender and delete the e-mail immediately.

2 1

event_route tm:branch-failure and onreply_route shared variables
by Володимир Іванець 20 Mar '19

20 Mar '19

Hello! I have Kamailio setup with registrar configured to allow multiple registrations. *branch_route[MANAGE_BRANCH]* contains *t_on_reply("REPLY")* and *t_on_branch_failure("FAILURE")*. *event_route[tm:branch-failure:FAILURE]* is used to do some logic, store information in htable and in the end it calls *t_relay* function. This creates new branch. Replies for this branch go to* onreply_route[REPLY]*. The problem is that I can not find appropriate variable that would be available in both *event_route tm:branch-failure* and *onreply_route*. I need it to get saved data from htable. $T_reply_ruid is available in first one but not in second. $T_branch_idx obviously changes so it can not be used. Some registrations do not have *Received* value so source IP address and ports can not be used. *Address* value can be compared with *Contact* header from responce tacket but it is so long that it looks like it's not optimal way to do. What interesting is that $T_reply_ruid is accessible in original replies for branches that have not failed. Does anyone know what variable can be used in this case or how to make sure that $T_reply_ruid will be set? Thanks a lot!

3 6

Pseudo-Variable {$au} is NULL
by Daniel Meyer-Wendt 20 Mar '19

20 Mar '19

Hi All, I am updating our Kamailio from 4.0.6 to the latest 5.2.2, we use kamailio as LB in front of two asterisk server. My problem is that during registration forward to the asterisk servers {$au} is NULL This is the code we have, which is the one you find in most documentations $uac_req(furi)="sip:" + $au + "@" + $var(rip); I logged some Pseudo-Variable to see their contents: {$au} NULL {$aU} NULL {$Au} username(a)domain.com {$fU} username {$oU} NULL {$ru} rU: {sip:domain.com;transport=UDP and ended up doing this which works $uac_req(furi)="sip:" + $fU + "@" + $var(rip); Any idea what could be wrong? Thanks, Daniel

2 2

Kamailio books
by Kevin Olbrich 20 Mar '19

20 Mar '19

Hi! Are there any Kamailio books? I am still struggling with Kamailio on scenarios that need more then REGISTER-offloading (like Kamailio cluster with BLF, custom NOTIFY, DMQ, etc.). Online docs are very limited or use Kamailio as a single tenant PBX. What I need is a high available and high performance proxy in front of asterisk, capable of handling thousands of tenants (each with BLF working). I am perfectly fine with building a solution for several months but I am still unable to understand everything from the docs. Where do the PROs and service companies get their knowledge from? Kind regards Kevin

4 4

Kamailio crashing and infinite-looping when trying to free memory
by Enrico Bandiera 19 Mar '19

19 Mar '19

Hi guys, recently we had some issues with kamailio in production, a proxy at the edge of the infrastructure was crashing seemingly randomly, it happened a couple of times in a timespan of 4-5 days until a point where we found it in an endless loop, unable to process SIP packets anymore and printing in loop messages like these: 50(60) CRITICAL: <core> [core/mem/q_malloc.c:512]: qm_free(): BUG: freeing already freed pointer (0x7ff40a359450), called from core: core/usr_avp.c: destroy_avp_list_unsafe(626), first free core: core/usr_avp.c: destroy_avp_list_unsafe(626) - ignoring 50(60) CRITICAL: <core> [core/mem/q_malloc.c:512]: qm_free(): BUG: freeing already freed pointer (0x7ff409c4fa58), called from core: core/usr_avp.c: destroy_avp_list_unsafe(626), first free core: core/usr_avp.c: destroy_avp_list_unsafe(626) - ignoring We managed to replicate the crash and the loop in a dev environment with a lot of difficulties. It seems not related to the peak load, but to the growing number of processed calls The kamailio version is: version: kamailio 5.2.2 (x86_64/linux) flags: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, 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 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 5.3.1 Every time this happened it was the timer pid that was crashing or looping, we managed to get 2 core dumps of the crash and 1 of the loop (got it after killing the timer with SIGQUIT). The timer process crashes after attempting to free memory that it's not correctly managed. In particular we saw that it happens inside destroy_avp_list_unsafe() called by the tm timer, when uri_avps_from points to an invalid memory address. We don't use dialog, uac, http_async_client, but we do use topos. In the crash dumps it seems that there's something wrong inside free_cell_helper(), when trying to clean the dead_cell something goes wrong while freeing uri_avps_from, here's the crash log: 61(76) CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 66 0(15) ALERT: <core> [main.c:740]: handle_sigs(): child process 65 exited by a signal 11 0(15) ALERT: <core> [main.c:743]: handle_sigs(): core was generated 0(15) INFO: <core> [main.c:766]: handle_sigs(): terminating due to SIGCHLD <childs getting the SIGTERM signal> 0(15) CRITICAL: <core> [core/mem/q_malloc.c:512]: qm_free(): BUG: freeing already freed pointer (0x7f4d60a2e168), called from htable: ht_api.c: ht_cell_free(217), first free core: core/usr_avp.c: destroy_avp_list_unsafe(626) - ignoring 0(15) INFO: <core> [core/sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized Before the crash we have no warnings on errors about shared memory allocation backtrace: (gdb) bt full #0 0x00000000006371d7 in destroy_avp_list_unsafe (list=0x7f34f7a411b0) at core/usr_avp.c:625 avp = 0x2 foo = 0x2 __func__ = "destroy_avp_list_unsafe" #1 0x00007f351c6909ab in free_cell_helper (dead_cell=0x7f34f7a41018, silent=0, fname=0x7f351c796a02 "timer.c", fline=689) at h_table.c:260 b = 0x0 i = 1 rpl = 0x0 tt = 0x0 foo = 0x11c68daf2 cbs = 0x0 cbs_tmp = 0x7f34f80c3790 __func__ = "free_cell_helper" #2 0x00007f351c7291e6 in wait_handler (ti=1984410416, wait_tl=0x7f34f7a410a0, data=0x7f34f7a41018) at timer.c:689 p_cell = 0x7f34f7a41018 ret = 1 unlinked = 0 rcount = 1 __func__ = "wait_handler" #3 0x00000000004d0f56 in timer_list_expire (t=1984410416, h=0x7f34f6be7850, slow_l=0x7f34f6bea368, slow_mark=2702) at core/timer.c:874 tl = 0x7f34f7a410a0 ret = 0 #4 0x00000000004d13bd in timer_handler () at core/timer.c:939 saved_ticks = 1984410416 run_slow_timer = 0 i = 654 __func__ = "timer_handler" #5 0x00000000004d1845 in timer_main () at core/timer.c:978 No locals. #6 0x0000000000425cc8 in main_loop () at main.c:1727 i = 8 pid = 0 si = 0x0 si_desc = "udp receiver child=7 sock=127.0.0.1:5060 \000\000\000\000q\000\000\000@6y\000\000\000\000\000\000\b\206|\210X\322:\032\301\255\000\000\000\000\000\000\000\000 \000\000\000\000\000\000\000\002\000\000\000\000\063\275{\000\000\000\000\000>", '\000' <repeats 15 times>, "\320\220\377\226\374\177\000\000\351\022a\000\000\000\000" nrprocs = 8 woneinit = 1 __func__ = "main_loop" #7 0x000000000042ca76 in main (argc=10, argv=0x7ffc96ff9398) at main.c:2696 cfg_stream = 0x25ca010 c = -1 r = 0 tmp = 0x7ffc96ffa4c9 "" tmp_len = -1761635728 port = 32764 proto = -1761635632 options = 0x76c598 ":f:cm:M:dVIhEeb:l:L:n:vKrRDTN:W:w:t:u:g:P:G:SQ:O:a:A:x:X:Y:" ret = -1 seed = 1492539644 rfd = 4 debug_save = 0 debug_flag = 0 dont_fork_cnt = 2 n_lst = 0x7f351f6f6718 p = 0xffffffff <error: Cannot access memory at address 0xffffffff> st = {st_dev = 2049, st_ino = 1282695, st_nlink = 2, st_mode = 16895, st_uid = 0, st_gid = 0, __pad0 = 0, st_rdev = 0, st_size = 4096, st_blksize = 4096, st_blocks = 8, st_atim = {tv_sec = 1552931478, tv_nsec = 972761643}, st_mtim = {tv_sec = 1552931478, tv_nsec = 972761643}, st_ctim = {tv_sec = 1552931478, tv_nsec = 972761643}, __glibc_reserved = {0, 0, 0}} __func__ = "main" In the loop dump we have a different situation, there's a loop in the uri_avps_from structure as you can see from the next pointers: (gdb) p *dead_cell->uri_avps_from $3 = {id = 66, flags = 275, next = 0x7ff40a359450, d = {p = 0x7ff40a9ad540, l = 140686126667072, data = "@\325\232\n\364\177\000"}} (gdb) p *dead_cell->uri_avps_from.next $4 = {id = 66, flags = 275, next = 0x7ff409c4fa58, d = {p = 0x7ff40a359480, l = 140686120031360, data = "\200\224\065\n\364\177\000"}} (gdb) p *dead_cell->uri_avps_from.next.next $5 = {id = 66, flags = 275, next = 0x7ff40a359450, d = {p = 0x7ff409c4fa88, l = 140686112651912, data = "\210\372\304\t\364\177\000"}} backtrace: (gdb) bt full #0 0x00007ff43152e67e in _IO_default_xsputn () from /lib/x86_64-linux-gnu/libc.so.6 No symbol table info available. #1 0x00007ff43150150b in vfprintf () from /lib/x86_64-linux-gnu/libc.so.6 No symbol table info available. #2 0x00007ff431502ef1 in ?? () from /lib/x86_64-linux-gnu/libc.so.6 No symbol table info available. #3 0x00007ff43150032d in vfprintf () from /lib/x86_64-linux-gnu/libc.so.6 No symbol table info available. #4 0x00007ff4315087f7 in fprintf () from /lib/x86_64-linux-gnu/libc.so.6 No symbol table info available. #5 0x0000000000686e43 in qm_free (qmp=0x7ff409336000, p=0x7ff409c4fa58, file=0x7e0a75 "core: core/usr_avp.c", func=0x7e2d70 <__func__.8439> "destroy_avp_list_unsafe", line=626, mname=0x7e0a70 "core") at core/mem/q_malloc.c:512 __llevel = -3 qm = 0x7ff409336000 f = 0x7ff409c4fa20 size = 72 next = 0x0 prev = 0x0 __func__ = "qm_free" #6 0x0000000000637209 in destroy_avp_list_unsafe (list=0x7ff409e1b6c8) at core/usr_avp.c:626 avp = 0x7ff40a359450 foo = 0x7ff409c4fa58 __func__ = "destroy_avp_list_unsafe" #7 0x00007ff42ee5d9ab in free_cell_helper (dead_cell=0x7ff409e1b530, silent=0, fname=0x7ff42ef63a02 "timer.c", fline=689) at h_table.c:260 b = 0x0 i = 1 rpl = 0x0 tt = 0x0 foo = 0x12ee5aaf2 cbs = 0x0 cbs_tmp = 0x7ff409c5d420 __func__ = "free_cell_helper" #8 0x00007ff42eef61e6 in wait_handler (ti=89094309, wait_tl=0x7ff409e1b5b8, data=0x7ff409e1b530) at timer.c:689 p_cell = 0x7ff409e1b530 ret = 1 unlinked = 0 rcount = 1 __func__ = "wait_handler" #9 0x00000000004d0f56 in timer_list_expire (t=89094309, h=0x7ff4093b4850, slow_l=0x7ff4093b8058, slow_mark=5981) at core/timer.c:874 tl = 0x7ff409e1b5b8 ret = 0 #10 0x00000000004d13bd in timer_handler () at core/timer.c:939 saved_ticks = 89094309 run_slow_timer = 0 i = 861 __func__ = "timer_handler" #11 0x00000000004d1845 in timer_main () at core/timer.c:978 No locals. #12 0x0000000000425cc8 in main_loop () at main.c:1727 i = 8 pid = 0 si = 0x0 si_desc = "udp receiver child=7 sock=127.0.0.1:5060 \000\000\000\000q\000\000\000@6y\000\000\000\000\000\000\032 t\220\260\242\024\032\301\255\000\000\000\000\000\000\000\000 \000\000\000\000\000\000\000\002\000\000\000\000\063\275{\000\000\000\000\000>", '\000' <repeats 15 times>, "\220\306\336\071\377\177\000\000\351\022a\000\000\000\000" nrprocs = 8 woneinit = 1 __func__ = "main_loop" #13 0x000000000042ca76 in main (argc=10, argv=0x7fff39dec958) at main.c:2696 cfg_stream = 0x2292010 c = -1 r = 0 tmp = 0x7fff39dee4c9 "" tmp_len = 970901552 port = 32767 proto = 970901648 options = 0x76c598 ":f:cm:M:dVIhEeb:l:L:n:vKrRDTN:W:w:t:u:g:P:G:SQ:O:a:A:x:X:Y:" ret = -1 seed = 2710999419 rfd = 4 debug_save = 0 debug_flag = 0 dont_fork_cnt = 2 n_lst = 0x7ff431ec3718 p = 0xffffffff <error: Cannot access memory at address 0xffffffff> st = {st_dev = 2049, st_ino = 1282695, st_nlink = 2, st_mode = 16895, st_uid = 0, st_gid = 0, __pad0 = 0, st_rdev = 0, st_size = 4096, st_blksize = 4096, st_blocks = 8, st_atim = {tv_sec = 1552931523, tv_nsec = 918435869}, st_mtim = {tv_sec = 1552994274, tv_nsec = 814438687}, st_ctim = {tv_sec = 1552994274, tv_nsec = 814438687}, __glibc_reserved = {0, 0, 0}} __func__ = "main" We are not sure on how to keep debugging this issue which is causing some serious troubles in our environment, any help is appreciated Here you can find the dumps (beware, 12M download but 1.5G once uncompressed): https://drive.google.com/file/d/1U0LZedyona8jJZHq6HaoqXpfnU83p6Sp/view?usp=… Due thanks to Giacomo Vacca who helped us to dig into this issue. Thanks

2 2

Kamailio 5.1.7 crash
by Jon Bonilla (Manwe) 18 Mar '19

18 Mar '19

Hi all A customer of mine has some crashes every week. We installed the dbg and finally generated a core. Bt full attached. Kamailio installed from kamailio deb 5.1 repos kamailio -V version: kamailio 5.1.7 (x86_64/linux) flags: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, 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 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 Any hints? thanks, Jon -- https://pekepbx.com https://www.issabel.com/multitenant

3 2

Kamailio as Peer Trunk in Asterisk
by Isravel Raja 18 Mar '19

18 Mar '19

Hi, I wanted to achieve the following scenario with Kamailio and Asterisk/FreeSwitch Kamailio as a trunk for Receiving incoming calls and forward to Asterisk and Make outgoing calls. My current working setup like this VoIP Provider -> Kamailio -> Asterisk Clusters Where Kamailio(NAT for public) and Asterisk in the same local network, So I had to do only one thing just create the SIP trunk in Asterisk for authenticating all the Kamailio Incoming calls and making outgoing calls like this [kamailio] host=172.18.1.1 type=friend disallow=all allow=ulaw context=trunkinbound This is IP based authentication, This is working fine since both servers are in the same local network or having the public IP's What I want is, I want to register the Kamailio Trunk in an asterisk with Username Password authentication, My current setup for making that, VoIP Provider -> Kamailio(Public) -> Asterisk(Randomly Changing Public IP, Broadband Connection) I want to register Kamailio SIP in asterisk trunk so that I can forward the incoming calls to asterisk via SIP extension [kamailio] host=172.18.1.1 user=user secret=password type=friend disallow=all allow=ulaw context=trunkinbound Let me know if anyone doesn't understand my concern This e-mail message and any documents attached to it are confidential and may contain information that is protected from disclosure by various federal and state laws, including the HIPAA privacy rule (45 C.F.R., Part 164). This information is intended to be used solely by the entity or individual to whom this message is addressed. If you are not the intended recipient, be advised that any use, dissemination, forwarding, printing, or copying of this message without the sender's written permission is strictly prohibited and may be unlawful. Accordingly, if you have received this message in error, please notify the sender immediately by return e-mail or call (insert phone number), and then delete this message.

1 0

RFC: rating - ranking system for community
by Daniel-Constantin Mierla 18 Mar '19

18 Mar '19

Hello, starting to continue the discussions here on mailing lists about some of the approached topics during the last IRC meeting -- there will be couple of them. The one now is about finding and deploying a ranking/rating system that could eventually help community members to make decisions easier in regard to what components to use in their voip systems. The need was exemplified by user verticelo with the dificulty to decide what KEMI scripting language to use. While maintaining all the app_xyz are expected to be easy, at least I know that for those I created, the arguments were also from the perspective of the community. Like what others are using, so one can expect good assistance, hints and share of knowledge via community forums. This can be also extended to related tools, like what people use for shared IP high availability of kamailio, preferred database servers, ... This email is to ask if those that didn't participate to IRC devel meeting find such system useful and, if there is a positive feedback, is anyone aware of some OSS that we can deploy on kamailio.org for such purpose? It should be something that allows posting a topic (title and short description) along with a list of answers/options (each can be again like a title and short description) and provide a way to rate the options (like, thumbs up, starts, ...), eventually allowing also comments for each option. I guess it sounds a bit like stackoverflow ... Being users related, the email is sent only to sr-users, let's keep the discussion on this mailing list. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio World Conference - May 6-8, 2019 -- www.kamailioworld.com Kamailio Advanced Training - Mar 25-27, 2019, in Washington, DC, USA -- www.asipto.com

5 5

Re: [SR-Users] RFC: roadmap to next major release - v5.3.0
by Ilie Soltanici 18 Mar '19

18 Mar '19

Daniel, Sounds good, would be nice to have some improvements on usrloc module, like requested in this topic: https://lists.kamailio.org/pipermail/sr-users/2019-January/104329.html Regards,

2 1

Which RTP addon for RFC4040 Clearmode passthrough support ?
by Olivier 15 Mar '19

15 Mar '19

Hello, I'm looking for a solution to integrate legacy devices to a SIP network. More precisely, I need to forward to and receive Clearmode RTP traffic (see [1]). 1. Do you know any Kamailio-compliant RTP engine (rtpproxy, rtp engine, ..) that support this on a Debian host ? 2. Suggestion ? [1] https://tools.ietf.org/html/rfc4040 Best regards

2 2

rtpengine force-relay
by Vitalii Aleksandrov 15 Mar '19

15 Mar '19

Hi there, Well it's mostly rtpengine question but didn't know where should I send it and probably the answer will be more or less useful for kamailio users. By default if an offer has ICE candidates rtpengine leaves them untouched and just inserts itself as an additional low priority candidate and also rewrites c= line for the callee without ICE support. Using ICE=force-relay rtpengine inserts itself as a "relay" candidate what is great but doesn't touch c= line and callee without ICE have no chance to send RTP to rtpengine. Is it possible somehow to make a third behavior like force-relay + rtpengine IP in c= param? It would allow any callee to send media to rtpengine regardless of ICE support.

3 6

cdp avps issues in kamailio 5.2
by Pavel S 15 Mar '19

15 Mar '19

Hello Mojtava, > Did you use FHOSS or IMS_DIAMETER_SERVER module? No, I am using our own hss server. >Anyway what mandatory parameters do you mean exactly? According to RFC6733 section 5.3.1 - https://tools.ietf.org/html/rfc6733#section-5.3.1 The Capabilities-Exchange-Request (CER), indicated by the Command Code set to 257 and the Command Flags' 'R' bit set, is sent to exchange local capabilities. Upon detection of a transport failure, this message MUST NOT be sent to an alternate peer. When Diameter is run over SCTP [RFC4960] or DTLS/SCTP [RFC6083], which allow for connections to span multiple interfaces and multiple IP addresses, the Capabilities-Exchange-Request message MUST contain one Host-IP-Address AVP for each potential IP address that MAY be locally used when transmitting Diameter messages. Message Format <CER> ::= < Diameter Header: 257, REQ > { Origin-Host } { Origin-Realm } 1* { Host-IP-Address } { Vendor-Id } { Product-Name } [ Origin-State-Id ] * [ Supported-Vendor-Id ] * [ Auth-Application-Id ] * [ Inband-Security-Id ] * [ Acct-Application-Id ] * [ Vendor-Specific-Application-Id ] [ Firmware-Revision ] * [ AVP ] Kamailio 5.1 with loaded cdp, cdr_avp, ims_icsf modules and default configuration described here https://github.com/kamailio/kamailio/tree/master/misc/examples/ims/icscf sends Host-IP-Address but Kamailio 5.2 with the same configuration doesn't. Any idea how to fix it? Regards, Pavel Siderov >Hello, >The CER/CEA messages are used just for connections between two peers >diameter interface. Did you use FHOSS or IMS_DIAMETER_SERVER module? In >both cases, you should not have any issue. Anyway what mandatory parameters >do you mean exactly? >WIth Best Regards. Mojtava ><https://www.kamailio.org/docs/modules/5.1.x/modules/ims_diameter_server.html> >On Tue, Mar 12, 2019 at 8:17 PM Pafel <pafels at gmail.com <https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users>> wrote: > >>* Hello, *>>>>* I am testing ims setup with kamailio 5.2 using the default configuration *>>* provided here: *>>* https://github.com/kamailio/kamailio/tree/master/misc/examples/ims/ <https://github.com/kamailio/kamailio/tree/master/misc/examples/ims/> . *>>* Тhere is an issue I am facing with cdp avp in request sent to hss. There *>>* are some missing mandatory parameters in capabilities exchange request like *>*> 257 host-ip-address for example. Any idea how to add it via icscf.xml or *>*> kamailio.cfg ? The same parameter is passed to hss with kamailio 5.1 using *>*> default ims configuration. I read cdp and cdp_avp documentation but *>*> couldn't understand if it is possible to add it. *>>>>* Regards, *>>* Pavel Siderov *>>* _______________________________________________ *>>* Kamailio (SER) - Users Mailing List *>>* sr-users at lists.kamailio.org <https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users> *>*> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users <https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users> *>>

4 3

Siremis on Kamailio 5.2
by Joel Serrano 15 Mar '19

15 Mar '19

Hi, Just curious if siremis works would work on Kamailio 5.2? The webside might not be updated: Installation Siremis installation is straightforward, being done mostly through a web wizzard. In just a few steps and less than 10 minutes you have your Siremis web site set up and ready to grant you easy administration of your Kamailio SIP server. You need to install first a compatible version of Kamailio SIP Server <https://www.kamailio.org/>. Siremis v5.1.x (devel) *Last release: v5.1.0 (devel version)* *Compatible with: Kamailio 5.1.x, 5.0.x* Thanks! Joel.

2 3

Drop 200OK re-transmissions of suspended transaction
by Marco Capetta 14 Mar '19

14 Mar '19

Hi All, I started playing with async kamailio feature, in particular using "async_route" function provided by ASYNC module (https://www.kamailio.org/docs/modules/5.1.x/modules/async.html#async.f.asyn…). My scenario is the following: - A calls B - B answer the call - inside onreply_route[reply] I catch the 200OK message and I suspend the transaction for X seconds. - after X seconds the transaction is resumed and the call continues as expected Everything looks good, but I encountered an issue trying to drop reply re-transmission messages. My desire is to drop all the messages received from B (basically 200OK re-transmissions) meanwhile the transaction is suspended. I tested "t_is_retr_async_reply" function provided by TM module (https://www.kamailio.org/docs/modules/5.1.x/modules/tm.html#tm.f.t_is_retr_…), but I'm not able to get it worked as expected: - t_is_retr_async_reply() function can be used only inside named 'onreply_route' (no default 'onreply_route' or standard 'reply_route') - drop() function, on the contrary, doesn't allow to drop 200OK messages inside named 'onreply_route' (but only in default 'onreply_route' or standard 'reply_route'). Do you have any suggestion on how I can achieve my task? Thank you very much for your support. Marco

2 2

Kamailio and exporting in-memory dialplan entries to another database
by Olli Attila 14 Mar '19

14 Mar '19

Hello, I was wondering that is there a command / procedure available in Kamailio that would do dialplan.dump on a certain dialplan and then export/write the output to another sql database where another dialplan table is present? This would be a sort of backup procedure that I'm planning. Cheers, Olli

2 1

Kamailio IMS - need help installing and configuring
by Pedro P. 14 Mar '19

14 Mar '19

Hello everyone, I'm starting at Kamailio IMS. However, some tutorials are outdated and the download links did not work. I need help with the installation process, basic settings. Thank you !

1 0

RFC: roadmap to next major release - v5.3.0
by Daniel-Constantin Mierla 14 Mar '19

14 Mar '19

Hello, during the last IRC devel meeting, we approached when the next major release of Kamailio (v5.3.0) should be done, considering two options: 1) before the mid of summer: try to freeze during the second part of May (latest beginning of June) and release during end of June/beginning of July. Afterwards is expected many developers to be in summer vacation (at least July and August are the common holidays months across Europe) 2) during autumn: let the summer pass, allow few weeks so everyone gets sync'ed with what happened during the holidays, freeze by end of September of so, release after 1-1.5 months Right now we have a few new modules, some interesting new features to existing components (e.g., rtpengine ...). If any of you has a strong preference for one option, let us know. This message was sent to both sr-users and sr-dev, you can reply to the one you feel more comfortable with, I will watch both of them and send a summary if we get to some conclusion soon. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio World Conference - May 6-8, 2019 -- www.kamailioworld.com Kamailio Advanced Training - Mar 25-27, 2019, in Washington, DC, USA -- www.asipto.com

1 0

407 Proxy Authentication Required
by Yağız AYDIN 14 Mar '19

14 Mar '19

Hello, I'm trying to implement Kamailio IMS and registration by using Boghe IMS. Registration profiles are default profiles provided by FHoSS ( Alice & Bob). While trying registration, I am facing some problems. REGISTER message behaves as intended and results with 200 OK. After 200 OK message, Boghe IMS is sending SUBSCRIBE message to S-CSCF (via P-CSCF), this message results with a 407 Proxy Authentication Required, I have some questions about this scenario. 1-) Why do I have this SUBSCRIBE message? Even though i commented out WITH_AUTH function, why do I have 407 Proxy Authentication Required message? 2-) On IMS Client side, when informaion about Alice or Bob is entered, login process results with success, but I can't send any message or do come calls. Is is related about this 407 message? 3-) On FHoSS interface, when I check IMPU values of those users, User-Status is marked as REGISTERED. From this perspective, should I consider registration is successful or not? 4-) How can I handle with this 407 Proxy Authentication Required message? Best Regards, Yağız --

2 4

Add default ports to URIs
by Duarte Rocha 13 Mar '19

13 Mar '19

Greetings, When i receive a message in Kamailio i want to add "5060" to the URI's port info when it's value is not specified. I can do it with pseudovariables but i was wondering if there's any config or setting that would do this automatically? Best Regards, Duarte Rocha

2 2

Kamailio as Peer Trunk in Asterisk
by Isravel Raja 13 Mar '19

13 Mar '19

Hi, I wanted to achieve the following scenario with Kamailio and Asterisk/FreeSwitch Kamailio as a trunk for Receiving incoming calls and forward to Asterisk and Make outgoing calls. My current working setup like this VoIP Provider -> Kamailio -> Asterisk Clusters Where Kamailio(NAT for public) and Asterisk in the same local network, So I had to do only one thing just create the SIP trunk in Asterisk for authenticating all the Kamailio Incoming calls and making outgoing calls like this [kamailio] host=172.18.1.1 type=friend disallow=all allow=ulaw context=trunkinbound This is IP based authentication, This is working fine since both servers are in the same local network or having the public IP's What I want is, I want to register the Kamailio Trunk in an asterisk with Username Password authentication, My current setup for making that, VoIP Provider -> Kamailio(Public) -> Asterisk(Randomly Changing Public IP, Broadband Connection) I want to register Kamailio SIP in asterisk trunk so that I can forward the incoming calls to asterisk via SIP extension [kamailio] host=172.18.1.1 user=user secret=password type=friend disallow=all allow=ulaw context=trunkinbound Let me know if anyone doesn't understand my concern This e-mail message and any documents attached to it are confidential and may contain information that is protected from disclosure by various federal and state laws, including the HIPAA privacy rule (45 C.F.R., Part 164). This information is intended to be used solely by the entity or individual to whom this message is addressed. If you are not the intended recipient, be advised that any use, dissemination, forwarding, printing, or copying of this message without the sender's written permission is strictly prohibited and may be unlawful. Accordingly, if you have received this message in error, please notify the sender immediately by return e-mail or call (insert phone number), and then delete this message.

1 0

radius_www_authorize error code -1
by Denys Pozniak 13 Mar '19

13 Mar '19

Hello! We are using radius_www_authorize() function to authorize incoming SIP REGISTERs, but sometimes happens case -1: for valid credentials (as I could see this in sngrep). And this time I did not detect corresponding Access-Request to RADIUS server side. Setting Kamailio debug level does not help to catch the real reason for this case in syslog. How to investigate this issue? Simple script example: if (!radius_www_authorize("$td")) { switch ($rc) { case -1: send_reply("400", "Bad Request"); exit; default: }; }; # -1 (error) - some error occurred during authorization (see syslog); [root@kamaili]# kamailio -v version: kamailio 4.4.2 (x86_64/linux) 892ad6 flags: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, 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 ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. id: 892ad6 compiled on 14:33:45 Apr 18 2018 with gcc 4.8.5 [root@kamailio]# rpm -qa | grep freeradius-client freeradius-client-1.1.7-16.el7.centos.x86_64 -- BR, Denys Pozniak

1 0

REGISTRATION ends with 408 Request Timeout
by Yağız AYDIN 13 Mar '19

13 Mar '19

Hello, I am trying to register my Kamailio IMS with Boghe IMS/Client. During registration, I have multiple SUBSCRIBE and NOTIFY requests ends with 408 Request Timeout. Here I provide Kamailio output and SIP traffic. What might be the problem? How can I solve it? Note = On Boghe IMS/Client side, PUBLISH and SUBSCRIBE options are CLOSED. Thanks for helps, Regards ----------P-CSCF----------------- kamailio -f /etc/kamailio/pcscf/kamailio-pcscf-deneme.cfg -Ee loading modules under config path: /usr/lib/x86_64-linux-gnu/kamailio/modules 0(30872) INFO: <core> [core/sctp_core.c:74]: sctp_core_check_support(): SCTP API not enabled - if you want to use it, load sctp module Listening on udp: 10.3.0.185 [10.3.0.185]:4060 tcp: 10.3.0.185 [10.3.0.185]:4060 Aliases: *: pcscf.mnc001.mcc001.3gppnetwork.org:* WARNING: no fork mode 0(30872) INFO: <core> [core/tcp_main.c:4721]: init_tcp(): using epoll_lt as the io watch method (auto detected) 0(30872) INFO: rr [../outbound/api.h:52]: ob_load_api(): unable to import bind_ob - maybe module is not loaded 0(30872) INFO: rr [rr_mod.c:175]: mod_init(): outbound module not available 0(30872) INFO: ims_usrloc_pcscf [hslot.c:62]: ul_init_locks(): locks array size 512 0(30872) INFO: <core> [core/udp_server.c:153]: probe_max_receive_buffer(): SO_RCVBUF is initially 212992 0(30872) INFO: <core> [core/udp_server.c:205]: probe_max_receive_buffer(): SO_RCVBUF is finally 524288 0(30872) WARNING: ims_usrloc_pcscf [usrloc_db.c:61]: connect_db(): DB connection already open... continuing 5(30877) INFO: jsonrpcs [jsonrpcs_sock.c:443]: jsonrpc_dgram_process(): a new child 0/30877 0(30872) INFO: <script>: [REGISTER] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: REGISTER (sip:alice@mnc001.mcc001.3gppnetwork.org (10.3.0.161:49934) to sip:alice@mnc001.mcc001.3gppnetwork.org, bddf8c98-bdea-229d-3517-3417ec6adcde) 0(30872) ERROR: ims_registrar_pcscf [save.c:342]: save_pending(): Error parsing sec-agree parameters: 4 0(30872) WARNING: ims_usrloc_pcscf [usrloc_db.c:420]: db_update_pcontact_security_temp(): not yet implemented or unknown security type 0(30872) ERROR: ims_usrloc_pcscf [udomain.c:586]: update_temp_security(): Error updating temp security for contact in DB 0(30872) ERROR: ims_registrar_pcscf [save.c:362]: save_pending(): Error updating temp security 0(30872) ERROR: <core> [core/resolve.c:941]: get_record(): unknown type 41 0(30872) INFO: <script>: [REGISTER] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: REGISTER (sip:alice@mnc001.mcc001.3gppnetwork.org (10.3.0.161:49934) to sip:alice@mnc001.mcc001.3gppnetwork.org, bddf8c98-bdea-229d-3517-3417ec6adcde) 0(30872) ERROR: ims_registrar_pcscf [save.c:342]: save_pending(): Error parsing sec-agree parameters: 4 0(30872) WARNING: ims_usrloc_pcscf [usrloc_db.c:420]: db_update_pcontact_security_temp(): not yet implemented or unknown security type 0(30872) ERROR: ims_usrloc_pcscf [udomain.c:586]: update_temp_security(): Error updating temp security for contact in DB 0(30872) ERROR: ims_registrar_pcscf [save.c:362]: save_pending(): Error updating temp security 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, dfad767b-fcaa-5605-3043-fdab7277afaa) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, 0acfa4a0-7899-6d55-4762-e9dd27e7cdd8) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, bbef7a73-f999-1250-5310-e8dff2548aa8) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, ddee4bb5-bcac-26d7-3075-989e77746da9) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, c1dd1520-8cef-5350-3573-8bdf555e77ae) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, 8bdb427a-cfbc-521d-6914-8af9744e7fbd) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, dc8101b5-9f8b-c010-9160-d49a1745f7bd) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, 9ab16525-8c6a-2261-3216-f9ef55729cbb) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, ab807656-6986-0242-5431-be9f63237878) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, 9fda4725-fcb8-6457-0576-aefeef0fce6f) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, b8bc1520-fba6-d15c-0744-f955774fcfab) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, faa8a454-669a-0616-5707-f9e85403dcaa) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, 0ffe5623-8acd-0762-7058-d9bd0e7eabff) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, acad5a15-efff-1c27-6146-abda7144d6eb) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, dbcb4b74-ccbd-6077-4178-a9d83245acad) 0(30872) INFO: <script>: [SUBSCRIBE] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: SUBSCRIBE ( sip:alice@mnc001.mcc001.3gppnetwork.org (10.3.0.161:49934) to sip:alice@mnc001.mcc001.3gppnetwork.org, f0af5607-98fa-15d7-6455-988f0e71fadc) 0(30872) ERROR: <core> [core/resolve.c:941]: get_record(): unknown type 41 0(30872) INFO: <script>: [SUBSCRIBE] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: SUBSCRIBE ( sip:alice@mnc001.mcc001.3gppnetwork.org (10.3.0.161:49934) to sip:alice@mnc001.mcc001.3gppnetwork.org, 78277425-cdaf-c80a-ceff-67700e71af89) 0(30872) INFO: <script>: [SUBSCRIBE] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: SUBSCRIBE ( sip:alice@mnc001.mcc001.3gppnetwork.org (10.3.0.161:49934) to sip:alice@mnc001.mcc001.3gppnetwork.org, dbcf716a-da9a-6075-3755-8faa2764cfd7) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, f0af5607-98fa-15d7-6455-988f0e71fadc) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, dfad767b-fcaa-5605-3043-fdab7277afaa) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, 0acfa4a0-7899-6d55-4762-e9dd27e7cdd8) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, bbef7a73-f999-1250-5310-e8dff2548aa8) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, ddee4bb5-bcac-26d7-3075-989e77746da9) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, c1dd1520-8cef-5350-3573-8bdf555e77ae) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, 8bdb427a-cfbc-521d-6914-8af9744e7fbd) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, dc8101b5-9f8b-c010-9160-d49a1745f7bd) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, 9ab16525-8c6a-2261-3216-f9ef55729cbb) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, ab807656-6986-0242-5431-be9f63237878) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, 9fda4725-fcb8-6457-0576-aefeef0fce6f) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, b8bc1520-fba6-d15c-0744-f955774fcfab) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, faa8a454-669a-0616-5707-f9e85403dcaa) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, 0ffe5623-8acd-0762-7058-d9bd0e7eabff) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, acad5a15-efff-1c27-6146-abda7144d6eb) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, dbcb4b74-ccbd-6077-4178-a9d83245acad) 0(30872) INFO: <script>: [SUBSCRIBE] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: SUBSCRIBE ( sip:alice@mnc001.mcc001.3gppnetwork.org (10.3.0.161:49934) to sip:alice@mnc001.mcc001.3gppnetwork.org, 78277425-cdaf-c80a-ceff-67700e71af89) 0(30872) INFO: <script>: [SUBSCRIBE] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: SUBSCRIBE ( sip:alice@mnc001.mcc001.3gppnetwork.org (10.3.0.161:49934) to sip:alice@mnc001.mcc001.3gppnetwork.org, dbcf716a-da9a-6075-3755-8faa2764cfd7) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, dfad767b-fcaa-5605-3043-fdab7277afaa) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, 0acfa4a0-7899-6d55-4762-e9dd27e7cdd8) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, bbef7a73-f999-1250-5310-e8dff2548aa8) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, ddee4bb5-bcac-26d7-3075-989e77746da9) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, c1dd1520-8cef-5350-3573-8bdf555e77ae) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, 8bdb427a-cfbc-521d-6914-8af9744e7fbd) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, dc8101b5-9f8b-c010-9160-d49a1745f7bd) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, 9ab16525-8c6a-2261-3216-f9ef55729cbb) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, ab807656-6986-0242-5431-be9f63237878) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, 9fda4725-fcb8-6457-0576-aefeef0fce6f) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, b8bc1520-fba6-d15c-0744-f955774fcfab) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, faa8a454-669a-0616-5707-f9e85403dcaa) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, 0ffe5623-8acd-0762-7058-d9bd0e7eabff) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, acad5a15-efff-1c27-6146-abda7144d6eb) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, dbcb4b74-ccbd-6077-4178-a9d83245acad) 0(30872) INFO: <script>: [SUBSCRIBE] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: SUBSCRIBE ( sip:alice@mnc001.mcc001.3gppnetwork.org (10.3.0.161:49934) to sip:alice@mnc001.mcc001.3gppnetwork.org, 78277425-cdaf-c80a-ceff-67700e71af89) 0(30872) INFO: <script>: [SUBSCRIBE] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: SUBSCRIBE ( sip:alice@mnc001.mcc001.3gppnetwork.org (10.3.0.161:49934) to sip:alice@mnc001.mcc001.3gppnetwork.org, dbcf716a-da9a-6075-3755-8faa2764cfd7) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, dfad767b-fcaa-5605-3043-fdab7277afaa) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, 0acfa4a0-7899-6d55-4762-e9dd27e7cdd8) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, bbef7a73-f999-1250-5310-e8dff2548aa8) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, ddee4bb5-bcac-26d7-3075-989e77746da9) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, c1dd1520-8cef-5350-3573-8bdf555e77ae) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, 8bdb427a-cfbc-521d-6914-8af9744e7fbd) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, dc8101b5-9f8b-c010-9160-d49a1745f7bd) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, 9ab16525-8c6a-2261-3216-f9ef55729cbb) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, ab807656-6986-0242-5431-be9f63237878) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, 9fda4725-fcb8-6457-0576-aefeef0fce6f) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, b8bc1520-fba6-d15c-0744-f955774fcfab) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, faa8a454-669a-0616-5707-f9e85403dcaa) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, 0ffe5623-8acd-0762-7058-d9bd0e7eabff) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, acad5a15-efff-1c27-6146-abda7144d6eb) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, dbcb4b74-ccbd-6077-4178-a9d83245acad) 0(30872) INFO: <script>: [SUBSCRIBE] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: SUBSCRIBE ( sip:alice@mnc001.mcc001.3gppnetwork.org (10.3.0.161:49934) to sip:alice@mnc001.mcc001.3gppnetwork.org, 78277425-cdaf-c80a-ceff-67700e71af89) 0(30872) INFO: <script>: [SUBSCRIBE] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: SUBSCRIBE ( sip:alice@mnc001.mcc001.3gppnetwork.org (10.3.0.161:49934) to sip:alice@mnc001.mcc001.3gppnetwork.org, dbcf716a-da9a-6075-3755-8faa2764cfd7) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, dfad767b-fcaa-5605-3043-fdab7277afaa) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, 0acfa4a0-7899-6d55-4762-e9dd27e7cdd8) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, bbef7a73-f999-1250-5310-e8dff2548aa8) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, ddee4bb5-bcac-26d7-3075-989e77746da9) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, c1dd1520-8cef-5350-3573-8bdf555e77ae) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, 8bdb427a-cfbc-521d-6914-8af9744e7fbd) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, dc8101b5-9f8b-c010-9160-d49a1745f7bd) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, 9ab16525-8c6a-2261-3216-f9ef55729cbb) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, ab807656-6986-0242-5431-be9f63237878) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, 9fda4725-fcb8-6457-0576-aefeef0fce6f) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, b8bc1520-fba6-d15c-0744-f955774fcfab) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, faa8a454-669a-0616-5707-f9e85403dcaa) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, 0ffe5623-8acd-0762-7058-d9bd0e7eabff) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, acad5a15-efff-1c27-6146-abda7144d6eb) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, dbcb4b74-ccbd-6077-4178-a9d83245acad) 0(30872) INFO: <script>: [SUBSCRIBE] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: SUBSCRIBE ( sip:alice@mnc001.mcc001.3gppnetwork.org (10.3.0.161:49934) to sip:alice@mnc001.mcc001.3gppnetwork.org, 78277425-cdaf-c80a-ceff-67700e71af89) 0(30872) INFO: <script>: [SUBSCRIBE] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: SUBSCRIBE ( sip:alice@mnc001.mcc001.3gppnetwork.org (10.3.0.161:49934) to sip:alice@mnc001.mcc001.3gppnetwork.org, dbcf716a-da9a-6075-3755-8faa2764cfd7) ------------------I-CSCF--------------------------------------------------- kamailio -f /etc/kamailio/icscf/kamailio-icscf-deneme.cfg -Ee loading modules under config path: /usr/lib/x86_64-linux-gnu/kamailio/modules 0(30791) INFO: <core> [core/sctp_core.c:74]: sctp_core_check_support(): SCTP API not enabled - if you want to use it, load sctp module Listening on udp: 10.3.0.186 [10.3.0.186]:4060 tcp: 10.3.0.186 [10.3.0.186]:4060 Aliases: *: icscf.mnc001.mcc001.3gppnetwork.org:* WARNING: no fork mode 0(30791) INFO: <core> [core/tcp_main.c:4721]: init_tcp(): using epoll_lt as the io watch method (auto detected) 0(30791) INFO: rr [../outbound/api.h:52]: ob_load_api(): unable to import bind_ob - maybe module is not loaded 0(30791) INFO: rr [rr_mod.c:175]: mod_init(): outbound module not available 0(30791) INFO: <core> [core/udp_server.c:153]: probe_max_receive_buffer(): SO_RCVBUF is initially 212992 0(30791) INFO: <core> [core/udp_server.c:205]: probe_max_receive_buffer(): SO_RCVBUF is finally 524288 0(30791) INFO: cdp [cdp_mod.c:242]: cdp_child_init(): CDiameterPeer child starting ... 5(30797) INFO: jsonrpcs [jsonrpcs_sock.c:443]: jsonrpc_dgram_process(): a new child 0/30797 6(30798) INFO: cdp [worker.c:332]: worker_process(): [0] Worker process started... 7(30799) INFO: cdp [worker.c:332]: worker_process(): [1] Worker process started... 8(30800) INFO: cdp [worker.c:332]: worker_process(): [2] Worker process started... 9(30801) INFO: cdp [worker.c:332]: worker_process(): [3] Worker process started... 10(30802) INFO: cdp [worker.c:332]: worker_process(): [4] Worker process started... 11(30803) INFO: cdp [worker.c:332]: worker_process(): [5] Worker process started... 12(30804) INFO: cdp [worker.c:332]: worker_process(): [6] Worker process started... 13(30805) INFO: cdp [worker.c:332]: worker_process(): [7] Worker process started... 14(30806) INFO: cdp [worker.c:332]: worker_process(): [8] Worker process started... 15(30807) INFO: cdp [worker.c:332]: worker_process(): [9] Worker process started... 16(30808) INFO: cdp [worker.c:332]: worker_process(): [10] Worker process started... 17(30809) INFO: cdp [worker.c:332]: worker_process(): [11] Worker process started... 18(30810) INFO: cdp [worker.c:332]: worker_process(): [12] Worker process started... 19(30811) INFO: cdp [worker.c:332]: worker_process(): [13] Worker process started... 20(30812) INFO: cdp [worker.c:332]: worker_process(): [14] Worker process started... 21(30813) INFO: cdp [worker.c:332]: worker_process(): [15] Worker process started... 22(30814) INFO: cdp [receiver.c:449]: receiver_process(): receiver_process(): [] Receiver process doing init on new process... 22(30814) INFO: cdp [receiver.c:454]: receiver_process(): receiver_process(): [] Receiver process starting up... 23(30815) INFO: cdp [receiver.c:449]: receiver_process(): receiver_process(): [hss.mnc001.mcc001.3gppnetwork.org] Receiver process doing init on new process... 23(30815) INFO: cdp [receiver.c:182]: add_serviced_peer(): add_serviced_peer(): Adding serviced_peer_t to receiver for peer [ hss.mnc001.mcc001.3gppnetwork.org] 24(30816) INFO: cdp [acceptor.c:81]: acceptor_process(): Acceptor process starting up... 0(30791) INFO: cdp [cdp_mod.c:244]: cdp_child_init(): ... CDiameterPeer child started 25(30817) INFO: cdp [timer.c:205]: timer_process(): Timer process starting up... 23(30815) INFO: cdp [receiver.c:454]: receiver_process(): receiver_process(): [hss.mnc001.mcc001.3gppnetwork.org] Receiver process starting up... 24(30816) WARNING: cdp [tcp_accept.c:120]: create_socket(): create_socket(): Trying to open/bind/listen on 10.3.0.186 port 3869 24(30816) WARNING: cdp [tcp_accept.c:145]: create_socket(): create_socket(): Successful socket open/bind/listen on 10.3.0.186 port 3869 24(30816) INFO: cdp [acceptor.c:95]: acceptor_process(): Acceptor opened sockets. Entering accept loop ... 25(30817) INFO: cdp [peerstatemachine.c:524]: I_Snd_Conn_Req(): I_Snd_Conn_Req(): Peer hss.mnc001.mcc001.3gppnetwork.org 25(30817) INFO: cdp [receiver.c:868]: peer_connect(): peer_connect(): Trying to connect to 10.3.0.184 port 3868 25(30817) INFO: cdp [receiver.c:937]: peer_connect(): peer_connect(): Peer hss.mnc001.mcc001.3gppnetwork.org:3868 connected 0(30791) INFO: <script>: [REGISTER] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30791) ERROR: <script>: REGISTER (sip:alice@mnc001.mcc001.3gppnetwork.org (10.3.0.185:4060) to sip:alice@mnc001.mcc001.3gppnetwork.org, bddf8c98-bdea-229d-3517-3417ec6adcde) 0(30791) INFO: ims_icscf [cxdx_uar.c:71]: create_uaa_return_code(): created AVP successfully : [uaa_return_code] 6(30798) INFO: ims_icscf [cxdx_avp.c:137]: cxdx_get_avp(): cxdx_get_result_code: Failed finding avp 6(30798) INFO: ims_icscf [cxdx_uar.c:71]: create_uaa_return_code(): created AVP successfully : [uaa_return_code] 6(30798) ERROR: <core> [core/resolve.c:941]: get_record(): unknown type 41 0(30791) INFO: <script>: [REGISTER] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30791) ERROR: <script>: REGISTER (sip:alice@mnc001.mcc001.3gppnetwork.org (10.3.0.185:4060) to sip:alice@mnc001.mcc001.3gppnetwork.org, bddf8c98-bdea-229d-3517-3417ec6adcde) --------------------------------S-CSCF--------------------------------- kamailio -f /etc/kamailio/scscf/kamailio-scscf-deneme.cfg -Ee loading modules under config path: /usr/lib/x86_64-linux-gnu/kamailio/modules 0(30819) INFO: <core> [core/sctp_core.c:74]: sctp_core_check_support(): SCTP API not enabled - if you want to use it, load sctp module Listening on udp: 10.3.0.187 [10.3.0.187]:6060 tcp: 10.3.0.187 [10.3.0.187]:6060 Aliases: *: scscf.mnc001.mcc001.3gppnetwork.org:* WARNING: no fork mode 0(30819) INFO: <core> [core/tcp_main.c:4721]: init_tcp(): using epoll_lt as the io watch method (auto detected) 0(30819) INFO: rr [../outbound/api.h:52]: ob_load_api(): unable to import bind_ob - maybe module is not loaded 0(30819) INFO: rr [rr_mod.c:175]: mod_init(): outbound module not available 0(30819) INFO: ims_usrloc_scscf [hslot.c:69]: ul_init_locks(): locks array size 512 0(30819) INFO: ims_usrloc_scscf [contact_hslot.c:67]: init_contacts_locks(): locks array size 512 0(30819) INFO: ims_usrloc_scscf [hslot_sp.c:70]: subs_init_locks(): locks array size 512 0(30819) INFO: <core> [core/udp_server.c:153]: probe_max_receive_buffer(): SO_RCVBUF is initially 212992 0(30819) INFO: <core> [core/udp_server.c:205]: probe_max_receive_buffer(): SO_RCVBUF is finally 524288 0(30819) INFO: cdp [cdp_mod.c:242]: cdp_child_init(): CDiameterPeer child starting ... 5(30824) INFO: jsonrpcs [jsonrpcs_sock.c:443]: jsonrpc_dgram_process(): a new child 0/30824 6(30825) INFO: cdp [worker.c:332]: worker_process(): [0] Worker process started... 7(30826) INFO: cdp [worker.c:332]: worker_process(): [1] Worker process started... 8(30827) INFO: cdp [worker.c:332]: worker_process(): [2] Worker process started... 9(30828) INFO: cdp [worker.c:332]: worker_process(): [3] Worker process started... 10(30829) INFO: cdp [worker.c:332]: worker_process(): [4] Worker process started... 11(30831) INFO: cdp [worker.c:332]: worker_process(): [5] Worker process started... 12(30833) INFO: cdp [worker.c:332]: worker_process(): [6] Worker process started... 14(30837) INFO: cdp [worker.c:332]: worker_process(): [8] Worker process started... 13(30835) INFO: cdp [worker.c:332]: worker_process(): [7] Worker process started... 15(30838) INFO: cdp [worker.c:332]: worker_process(): [9] Worker process started... 16(30842) INFO: cdp [worker.c:332]: worker_process(): [10] Worker process started... 17(30843) INFO: cdp [worker.c:332]: worker_process(): [11] Worker process started... 19(30847) INFO: cdp [worker.c:332]: worker_process(): [13] Worker process started... 18(30845) INFO: cdp [worker.c:332]: worker_process(): [12] Worker process started... 0(30819) INFO: cdp [cdp_mod.c:244]: cdp_child_init(): ... CDiameterPeer child started 22(30852) INFO: cdp [receiver.c:449]: receiver_process(): receiver_process(): [] Receiver process doing init on new process... 22(30852) INFO: cdp [receiver.c:454]: receiver_process(): receiver_process(): [] Receiver process starting up... 23(30853) INFO: cdp [receiver.c:449]: receiver_process(): receiver_process(): [hss.mnc001.mcc001.3gppnetwork.org] Receiver process doing init on new process... 23(30853) INFO: cdp [receiver.c:182]: add_serviced_peer(): add_serviced_peer(): Adding serviced_peer_t to receiver for peer [ hss.mnc001.mcc001.3gppnetwork.org] 23(30853) INFO: cdp [receiver.c:454]: receiver_process(): receiver_process(): [hss.mnc001.mcc001.3gppnetwork.org] Receiver process starting up... 25(30858) INFO: cdp [timer.c:205]: timer_process(): Timer process starting up... 24(30854) INFO: cdp [acceptor.c:81]: acceptor_process(): Acceptor process starting up... 20(30849) INFO: cdp [worker.c:332]: worker_process(): [14] Worker process started... 21(30851) INFO: cdp [worker.c:332]: worker_process(): [15] Worker process started... 24(30854) WARNING: cdp [tcp_accept.c:120]: create_socket(): create_socket(): Trying to open/bind/listen on 10.3.0.187 port 3870 24(30854) WARNING: cdp [tcp_accept.c:145]: create_socket(): create_socket(): Successful socket open/bind/listen on 10.3.0.187 port 3870 24(30854) INFO: cdp [acceptor.c:95]: acceptor_process(): Acceptor opened sockets. Entering accept loop ... 25(30858) INFO: cdp [peerstatemachine.c:524]: I_Snd_Conn_Req(): I_Snd_Conn_Req(): Peer hss.mnc001.mcc001.3gppnetwork.org 25(30858) INFO: cdp [receiver.c:868]: peer_connect(): peer_connect(): Trying to connect to 10.3.0.184 port 3868 25(30858) INFO: cdp [receiver.c:937]: peer_connect(): peer_connect(): Peer hss.mnc001.mcc001.3gppnetwork.org:3868 connected 0(30819) INFO: <script>: [REGISTER] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30819) INFO: ims_auth [cxdx_mar.c:79]: create_return_code(): created AVP successfully : [maa_return_code] - [-2] 6(30825) INFO: ims_auth [cxdx_avp.c:137]: cxdx_get_avp(): cxdx_get_experimental_result_code: Failed finding avp (avp_code = 297, vendor_id = 0) 6(30825) INFO: ims_auth [cxdx_mar.c:79]: create_return_code(): created AVP successfully : [maa_return_code] - [1] 0(30819) INFO: <script>: [REGISTER] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30819) INFO: ims_auth [authorize.c:827]: authenticate(): uri=sip: mnc001.mcc001.3gppnetwork.org nonce=04cd0652709df5d623429c0dbc8f5f2f response=d3c9e4eb2a533fe48e9569ab128afe53 qop=auth-int nc=00000001 cnonce=b4c66d5473e1da9bf59735657686d706 hbody=d41d8cd98f00b204e9800998ecf8427e 0(30819) INFO: ims_auth [authorize.c:882]: authenticate(): UE said: d3c9e4eb2a533fe48e9569ab128afe53 and we expect d3c9e4eb2a533fe48e9569ab128afe53 ha1 edd6cb70b2ab3a374d5404ac53ea7e55 (REGISTER) 0(30819) WARNING: ims_auth [authorize.c:1006]: authenticate(): NB: Ignoring all failed auth - check your config if you don't expect this 0(30819) INFO: ims_registrar_scscf [cxdx_sar.c:84]: create_return_code(): created AVP successfully : [saa_return_code] - [-2] 7(30826) INFO: ims_registrar_scscf [cxdx_avp.c:138]: cxdx_get_avp(): cxdx_get_experimental_result_code: Failed finding avp 0(30819) INFO: <script>: [REGISTER] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 7(30826) INFO: ims_registrar_scscf [cxdx_sar.c:84]: create_return_code(): created AVP successfully : [saa_return_code] - [1] 0(30819) INFO: <script>: [SUBSCRIBE] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30819) INFO: <script>: [SUBSCRIBE] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30819) INFO: ims_isc [ims_isc_mod.c:233]: isc_match_filter(): Checking triggers 0(30819) INFO: <script>: [SUBSCRIBE] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30819) INFO: ims_isc [ims_isc_mod.c:233]: isc_match_filter(): Checking triggers 0(30819) INFO: <script>: [SUBSCRIBE] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30819) INFO: <script>: [SUBSCRIBE] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30819) INFO: <script>: [SUBSCRIBE] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30819) INFO: <script>: [SUBSCRIBE] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30819) INFO: <script>: [SUBSCRIBE] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30819) INFO: <script>: [SUBSCRIBE] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30819) INFO: <script>: [SUBSCRIBE] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30819) INFO: <script>: [SUBSCRIBE] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] -----------------------------ngrep------------------------------------------ U 10.3.0.161:62602 -> 10.3.0.185:4060 #1 REGISTER sip:mnc001.mcc001.3gppnetwork.org SIP/2.0..Via: SIP/2.0/UDP 10.3.0 .161:62602;branch=z9hG4bK2293842870;rport..From: <sip:alice@mnc001.mcc001.3 gppnetwork.org>;tag=2293851690..To: <sip:alice@mnc001.mcc001.3gppnetwork.or g>..Contact: <sip:alice@10.3.0.161:62602 ;transport=udp>;expires=600000;+g.o ma.sip-im;language="en,fr";+g.3gpp.smsip;+g.oma.sip-im.large-message;audio; +g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-application.ims.iari.gsma-vs";+g.3gpp. cs-voice..Call-ID: 54465103-da8d-a9a9-217a-bd8cabd0a465..CSeq: 5477 REGISTE R..Content-Length: 0..Max-Forwards: 70..Authorization: Digest username="ali ce(a)mnc001.mcc001.3gppnetwork.org",realm="mnc001.mcc001.3gppnetwork.org ",non ce="",uri="sip:mnc001.mcc001.3gppnetwork.org",response=""..Allow: INVITE, A CK, CANCEL, BYE, MESSAGE, OPTIONS, NOTIFY, PRACK, UPDATE, REFER..Privacy: n one..P-Access-Network-Info: ADSL;utran-cell-id-3gpp=00000000..User-Agent: I M-client/OMA1.0 Boghe-Win32/v2.0.153.836..P-Preferred-Identity: <sip:alice@ mnc001.mcc001.3gppnetwork.org>..Supported: path.... # U 10.3.0.185:4060 -> 10.3.0.161:62602 #2 SIP/2.0 100 Trying..Via: SIP/2.0/UDP 10.3.0.161:62602 ;branch=z9hG4bK2293842 870;rport=62602;received=10.3.0.161..From: <sip:alice@mnc001.mcc001.3gppnet work.org>;tag=2293851690..To: <sip:alice@mnc001.mcc001.3gppnetwork.org >..Ca ll-ID: 54465103-da8d-a9a9-217a-bd8cabd0a465..CSeq: 5477 REGISTER..Server: K amailio P-CSCF..Content-Length: 0..Warning: 392 10.3.0.185:4060 "Noisy feed back tells: pid=30872 req_src_ip=10.3.0.161 req_src_port=62602 in_uri=sip: mnc001.mcc001.3gppnetwork.org out_uri=sip:mnc001.mcc001.3gppnetwork.org via _cnt==1".... # U 10.3.0.185:4060 -> 10.3.0.161:62602 #3 SIP/2.0 401 Unauthorized - Challenging the UE..Via: SIP/2.0/UDP 10.3.0.161 : 62602;received=10.3.0.161;branch=z9hG4bK2293842870;rport=62602..From: <sip: alice(a)mnc001.mcc001.3gppnetwork.org>;tag=2293851690..To: <sip:alice@mnc001. mcc001.3gppnetwork.org >;tag=9bb9548d48f8c3c628773a7ade1ae022-78b5..Call-ID: 54465103-da8d-a9a9-217a-bd8cabd0a465..CSeq: 5477 REGISTER..WWW-Authenticat e: Digest realm="mnc001.mcc001.3gppnetwork.org", nonce="f39d692b0ec5f77a16e db779cec82e8e", algorithm=MD5, qop="auth,auth-int"..Server: Kamailio S-CSCF ..Content-Length: 0..Warning: 392 10.3.0.187:6060 "Noisy feedback tells: p id=30827 req_src_ip=10.3.0.186 req_src_port=4060 in_uri=sip: scscf.mnc001.mc c001.3gppnetwork.org:6060 out_uri=sip: scscf.mnc001.mcc001.3gppnetwork.org:6 060 via_cnt==4".... # U 10.3.0.161:62602 -> 10.3.0.185:4060 #4 REGISTER sip:mnc001.mcc001.3gppnetwork.org SIP/2.0..Via: SIP/2.0/UDP 10.3.0 .161:62602;branch=z9hG4bK2293850812;rport..From: <sip:alice@mnc001.mcc001.3 gppnetwork.org>;tag=2293851690..To: <sip:alice@mnc001.mcc001.3gppnetwork.or g>..Contact: <sip:alice@10.3.0.161:62602 ;transport=udp>;expires=600000;+g.o ma.sip-im;language="en,fr";+g.3gpp.smsip;+g.oma.sip-im.large-message;audio; +g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-application.ims.iari.gsma-vs";+g.3gpp. cs-voice..Call-ID: 54465103-da8d-a9a9-217a-bd8cabd0a465..CSeq: 5478 REGISTE R..Content-Length: 0..Max-Forwards: 70..Authorization: Digest username="ali ce(a)mnc001.mcc001.3gppnetwork.org",realm="mnc001.mcc001.3gppnetwork.org ",non ce="f39d692b0ec5f77a16edb779cec82e8e",uri="sip:mnc001.mcc001.3gppnetwork.or g",response="7259db7c12d0cdd550556b25851cc174",algorithm=MD5,cnonce="0a9efc d9c6fca265c8587fd4ea9b75cb",qop=auth-int,nc=00000001..Allow: INVITE, ACK, C ANCEL, BYE, MESSAGE, OPTIONS, NOTIFY, PRACK, UPDATE, REFER..Privacy: none.. P-Access-Network-Info: ADSL;utran-cell-id-3gpp=00000000..User-Agent: IM-cli ent/OMA1.0 Boghe-Win32/v2.0.153.836..P-Preferred-Identity: <sip:alice@mnc00 1.mcc001.3gppnetwork.org>..Supported: path.... # U 10.3.0.185:4060 -> 10.3.0.161:62602 #5 SIP/2.0 100 Trying..Via: SIP/2.0/UDP 10.3.0.161:62602 ;branch=z9hG4bK2293850 812;rport=62602;received=10.3.0.161..From: <sip:alice@mnc001.mcc001.3gppnet work.org>;tag=2293851690..To: <sip:alice@mnc001.mcc001.3gppnetwork.org >..Ca ll-ID: 54465103-da8d-a9a9-217a-bd8cabd0a465..CSeq: 5478 REGISTER..Server: K amailio P-CSCF..Content-Length: 0..Warning: 392 10.3.0.185:4060 "Noisy feed back tells: pid=30872 req_src_ip=10.3.0.161 req_src_port=62602 in_uri=sip: mnc001.mcc001.3gppnetwork.org out_uri=sip:mnc001.mcc001.3gppnetwork.org via _cnt==1".... # U 10.3.0.185:4060 -> 10.3.0.161:56702 #6 NOTIFY sip:alice@10.3.0.161:56702;transport=udp SIP/2.0..Via: SIP/2.0/UDP 1 0.3.0.185:4060;branch=z9hG4bKea02.bd6e4c76e778b145d63e9c39c5faf221.0..Via: SIP/2.0/UDP 10.3.0.187:6060 ;branch=z9hG4bKea02.eb9813f500000000000000000000 0000.0..To: <sip:alice@mnc001.mcc001.3gppnetwork.org >;tag=1753523419..From: <sip:alice@mnc001.mcc001.3gppnetwork.org >;tag=9bb9548d48f8c3c628773a7ade1a e022-7ed6..CSeq: 24556 NOTIFY..Call-ID: dfad767b-fcaa-5605-3043-fdab7277afa a..Content-Length: 1398..User-Agent: Kamailio S-CSCF..Contact: <sip:scscf.m nc001.mcc001.3gppnetwork.org:6060>..Event: reg..Max-Forwards: 69..Subscript ion-State: active;expires=59687..Content-Type: application/reginfo+xml....< ?xml version="1.0"?>.<reginfo xmlns="urn:ietf:params:xml:ns:reginfo" versio n="89" state="full">..<registration aor="sip:alice@mnc001.mcc001.3gppnetwor k.org" id="0x7f29e0645ce8" state="active">...<contact id="0x7f29e0647128" s tate="active" event="registered" expires="3136" q="0.000">....<uri>sip:alic e@10.3.0.161:49428;transport=udp</uri>...<unknown-param name="+g.3gpp.smsip "></unknown-param>...<unknown-param name="+g.3gpp.icsi-ref">"urn0X0.07FFF00 0BDBP-1022urn-70X0.07FFF000BDB9P-10223gpp-application.ims.iari.gsma-vs"</un known-param>...</contact>...<contact id="0x7f29e065aa28" state="active" eve nt="registered" expires="3226" q="0.000">....<uri> sip:alice@10.3.0.161:4993 4;transport=udp</uri>...<unknown-param name="+g.3gpp.icsi-ref">"urn0X0.0000 0EBB514F8P-1022urn-70X0.07F29E4A137CBP-10223gpp # U 10.3.0.185 -> 10.3.0.161 +21732@1480:600 #7 -application.ims.iari.gsma-vs"</unknown-param>...<unknown-param name="+g.3g pp.smsip"></unknown-param>...<unknown-param name="expires">"600000"</unknow n-param>...</contact>...<contact id="0x7f29e065ecd0" state="active" event=" registered" expires="3600" q="0.000">....<uri>sip:alice@10.3.0.161:62602 ;tr ansport=udp</uri>...<unknown-param name="+g.3gpp.icsi-ref">"urn0X0.0558E280 4FB7P-1022urn-70X0P+03gpp-application.ims.iari.gsma-vs"</unknown-param>...< unknown-param name="+g.3gpp.smsip"></unknown-param>...<unknown-param name=" expires">"600000"</unknown-param>...</contact>..</registration>.</reginfo>. # U 10.3.0.185:4060 -> 10.3.0.161:64088 #8 NOTIFY sip:alice@10.3.0.161:64088;transport=udp SIP/2.0..Via: SIP/2.0/UDP 1 0.3.0.185:4060;branch=z9hG4bK9034.6bdcb80f0efd1d4d8e90e90788523e14.0..Via: SIP/2.0/UDP 10.3.0.187:6060 ;branch=z9hG4bK9034.8b235b5600000000000000000000 0000.0..To: <sip:alice@mnc001.mcc001.3gppnetwork.org >;tag=1753616070..From: <sip:alice@mnc001.mcc001.3gppnetwork.org >;tag=9bb9548d48f8c3c628773a7ade1a e022-cc79..CSeq: 24553 NOTIFY..Call-ID: 0acfa4a0-7899-6d55-4762-e9dd27e7cdd 8..Content-Length: 1397..User-Agent: Kamailio S-CSCF..Contact: <sip:scscf.m nc001.mcc001.3gppnetwork.org:6060>..Event: reg..Max-Forwards: 69..Subscript ion-State: active;expires=59792..Content-Type: application/reginfo+xml....< ?xml version="1.0"?>.<reginfo xmlns="urn:ietf:params:xml:ns:reginfo" versio n="86" state="full">..<registration aor="sip:alice@mnc001.mcc001.3gppnetwor k.org" id="0x7f29e0645ce8" state="active">...<contact id="0x7f29e0647128" s tate="active" event="registered" expires="3136" q="0.000">....<uri>sip:alic e@10.3.0.161:49428;transport=udp</uri>...<unknown-param name="+g.3gpp.smsip "></unknown-param>...<unknown-param name="+g.3gpp.icsi-ref">"urn0X0.07FFF00 0BDBP-1022urn-70X0.07FFF000BDB9P-10223gpp-application.ims.iari.gsma-vs"</un known-param>...</contact>...<contact id="0x7f29e065aa28" state="active" eve nt="registered" expires="3226" q="0.000">....<uri> sip:alice@10.3.0.161:4993 4;transport=udp</uri>...<unknown-param name="+g.3gpp.icsi-ref">"urn0X0.0000 0EBB514FP-1022urn-70X0.07F29E4A137CBP-10223gpp- # U 10.3.0.185 -> 10.3.0.161 +21733@1480:599 #9 application.ims.iari.gsma-vs"</unknown-param>...<unknown-param name="+g.3gp p.smsip"></unknown-param>...<unknown-param name="expires">"600000"</unknown -param>...</contact>...<contact id="0x7f29e065ecd0" state="active" event="r egistered" expires="3600" q="0.000">....<uri>sip:alice@10.3.0.161:62602 ;tra nsport=udp</uri>...<unknown-param name="+g.3gpp.icsi-ref">"urn0X0.0558E2804 FB7P-1022urn-70X0P+03gpp-application.ims.iari.gsma-vs"</unknown-param>...<u nknown-param name="+g.3gpp.smsip"></unknown-param>...<unknown-param name="e xpires">"600000"</unknown-param>...</contact>..</registration>.</reginfo>. # U 10.3.0.185:4060 -> 10.3.0.161:49483 #10 NOTIFY sip:alice@10.3.0.161:49483;transport=udp SIP/2.0..Via: SIP/2.0/UDP 1 0.3.0.185:4060;branch=z9hG4bK8bbf.b5ae369a8d069d44118b59a4d45a757b.0..Via: SIP/2.0/UDP 10.3.0.187:6060 ;branch=z9hG4bK8bbf.34d5484200000000000000000000 0000.0..To: <sip:alice@mnc001.mcc001.3gppnetwork.org >;tag=2274225491..From: <sip:alice@mnc001.mcc001.3gppnetwork.org >;tag=9bb9548d48f8c3c628773a7ade1a e022-b2dc..CSeq: 24511 NOTIFY..Call-ID: c1dd1520-8cef-5350-3573-8bdf555e77a e..Content-Length: 1398..User-Agent: Kamailio S-CSCF..Contact: <sip:scscf.m nc001.mcc001.3gppnetwork.org:6060>..Event: reg..Max-Forwards: 69..Subscript ion-State: active;expires=580374..Content-Type: application/reginfo+xml.... <?xml version="1.0"?>.<reginfo xmlns="urn:ietf:params:xml:ns:reginfo" versi on="44" state="full">..<registration aor="sip:alice@mnc001.mcc001.3gppnetwo rk.org" id="0x7f29e0645ce8" state="active">...<contact id="0x7f29e0647128" state="active" event="registered" expires="3135" q="0.000">....<uri>sip:ali ce@10.3.0.161:49428;transport=udp</uri>...<unknown-param name="+g.3gpp.smsi p"></unknown-param>...<unknown-param name="+g.3gpp.icsi-ref">"urn0X0.07FFF0 00BDBP-1022urn-70X0.07FFF000BDB9P-10223gpp-application.ims.iari.gsma-vs"</u nknown-param>...</contact>...<contact id="0x7f29e065aa28" state="active" ev ent="registered" expires="3225" q="0.000">....<uri> sip:alice@10.3.0.161:499 34;transport=udp</uri>...<unknown-param name="+g.3gpp.icsi-ref">"urn0X0.000 00EBB514F8P-1022urn-70X0.07F29E4A137CBP-10223gp # U 10.3.0.185 -> 10.3.0.161 +21734@1480:601 #11 p-application.ims.iari.gsma-vs"</unknown-param>...<unknown-param name="+g.3 gpp.smsip"></unknown-param>...<unknown-param name="expires">"600000"</unkno wn-param>...</contact>...<contact id="0x7f29e065ecd0" state="active" event= "registered" expires="3599" q="0.000">....<uri>sip:alice@10.3.0.161:62602 ;t ransport=udp</uri>...<unknown-param name="+g.3gpp.icsi-ref">"urn0X0.0558E28 04FB7P-1022urn-70X0P+03gpp-application.ims.iari.gsma-vs"</unknown-param>... <unknown-param name="+g.3gpp.smsip"></unknown-param>...<unknown-param name= "expires">"600000"</unknown-param>...</contact>..</registration>.</reginfo> . # U 10.3.0.185:4060 -> 10.3.0.161:52923 #12 NOTIFY sip:alice@10.3.0.161:52923;transport=udp SIP/2.0..Via: SIP/2.0/UDP 1 0.3.0.185:4060;branch=z9hG4bKadba.ce55b6f7bef3f603cde4a55375dd8c86.0..Via: SIP/2.0/UDP 10.3.0.187:6060 ;branch=z9hG4bKadba.d52eaf2600000000000000000000 0000.0..To: <sip:alice@mnc001.mcc001.3gppnetwork.org >;tag=2273886730..From: <sip:alice@mnc001.mcc001.3gppnetwork.org >;tag=9bb9548d48f8c3c628773a7ade1a e022-d59d..CSeq: 24517 NOTIFY..Call-ID: bbef7a73-f999-1250-5310-e8dff2548aa 8..Content-Length: 1398..User-Agent: Kamailio S-CSCF..Contact: <sip:scscf.m nc001.mcc001.3gppnetwork.org:6060>..Event: reg..Max-Forwards: 69..Subscript ion-State: active;expires=580056..Content-Type: application/reginfo+xml.... <?xml version="1.0"?>.<reginfo xmlns="urn:ietf:params:xml:ns:reginfo" versi on="50" state="full">..<registration aor="sip:alice@mnc001.mcc001.3gppnetwo rk.org" id="0x7f29e0645ce8" state="active">...<contact id="0x7f29e0647128" state="active" event="registered" expires="3136" q="0.000">....<uri>sip:ali ce@10.3.0.161:49428;transport=udp</uri>...<unknown-param name="+g.3gpp.smsi p"></unknown-param>...<unknown-param name="+g.3gpp.icsi-ref">"urn0X0.07FFF0 00BDBP-1022urn-70X0.07FFF000BDB9P-10223gpp-application.ims.iari.gsma-vs"</u nknown-param>...</contact>...<contact id="0x7f29e065aa28" state="active" ev ent="registered" expires="3226" q="0.000">....<uri> sip:alice@10.3.0.161:499 34;transport=udp</uri>...<unknown-param name="+g.3gpp.icsi-ref">"urn0X0.000 00EBB514F8P-1022urn-70X0.07F29E4A137CBP-10223gp # U 10.3.0.185 -> 10.3.0.161 +21735@1480:601 #13 p-application.ims.iari.gsma-vs"</unknown-param>...<unknown-param name="+g.3 gpp.smsip"></unknown-param>...<unknown-param name="expires">"600000"</unkno wn-param>...</contact>...<contact id="0x7f29e065ecd0" state="active" event= "registered" expires="3600" q="0.000">....<uri>sip:alice@10.3.0.161:62602 ;t ransport=udp</uri>...<unknown-param name="+g.3gpp.icsi-ref">"urn0X0.0558E28 04FB7P-1022urn-70X0P+03gpp-application.ims.iari.gsma-vs"</unknown-param>... <unknown-param name="+g.3gpp.smsip"></unknown-param>...<unknown-param name= "expires">"600000"</unknown-param>...</contact>..</registration>.</reginfo> . # U 10.3.0.185:4060 -> 10.3.0.161:51090 #14 NOTIFY sip:alice@10.3.0.161:51090;transport=udp SIP/2.0..Via: SIP/2.0/UDP 1 0.3.0.185:4060;branch=z9hG4bKdd46.16bbd8e9fa22e61163e25a1b1cb4da7d.0..Via: SIP/2.0/UDP 10.3.0.187:6060 ;branch=z9hG4bKdd46.3f6d5b6200000000000000000000 0000.0..To: <sip:alice@mnc001.mcc001.3gppnetwork.org >;tag=2274040838..From: <sip:alice@mnc001.mcc001.3gppnetwork.org >;tag=9bb9548d48f8c3c628773a7ade1a e022-ca38..CSeq: 24514 NOTIFY..Call-ID: ddee4bb5-bcac-26d7-3075-989e77746da 9..Content-Length: 1397..User-Agent: Kamailio S-CSCF..Contact: <sip:scscf.m nc001.mcc001.3gppnetwork.org:6060>..Event: reg..Max-Forwards: 69..Subscript ion-State: active;expires=580239..Content-Type: application/reginfo+xml.... <?xml version="1.0"?>.<reginfo xmlns="urn:ietf:params:xml:ns:reginfo" versi on="47" state="full">..<registration aor="sip:alice@mnc001.mcc001.3gppnetwo rk.org" id="0x7f29e0645ce8" state="active">...<contact id="0x7f29e0647128" state="active" event="registered" expires="3136" q="0.000">....<uri>sip:ali ce@10.3.0.161:49428;transport=udp</uri>...<unknown-param name="+g.3gpp.smsi p"></unknown-param>...<unknown-param name="+g.3gpp.icsi-ref">"urn0X0.07FFF0 00BDBP-1022urn-70X0.07FFF000BDB9P-10223gpp-application.ims.iari.gsma-vs"</u nknown-param>...</contact>...<contact id="0x7f29e065aa28" state="active" ev ent="registered" expires="3226" q="0.000">....<uri> sip:alice@10.3.0.161:499 34;transport=udp</uri>...<unknown-param name="+g.3gpp.icsi-ref">"urn0X0.000 00EBB514FP-1022urn-70X0.07F29E4A137CBP-10223gpp # U 10.3.0.185 -> 10.3.0.161 +21736@1480:600 #15 -application.ims.iari.gsma-vs"</unknown-param>...<unknown-param name="+g.3g pp.smsip"></unknown-param>...<unknown-param name="expires">"600000"</unknow n-param>...</contact>...<contact id="0x7f29e065ecd0" state="active" event=" registered" expires="3600" q="0.000">....<uri>sip:alice@10.3.0.161:62602 ;tr ansport=udp</uri>...<unknown-param name="+g.3gpp.icsi-ref">"urn0X0.0558E280 4FB7P-1022urn-70X0P+03gpp-application.ims.iari.gsma-vs"</unknown-param>...< unknown-param name="+g.3gpp.smsip"></unknown-param>...<unknown-param name=" expires">"600000"</unknown-param>...</contact>..</registration>.</reginfo>. # U 10.3.0.185:4060 -> 10.3.0.161:60376 #16 NOTIFY sip:alice@10.3.0.161:60376;transport=udp SIP/2.0..Via: SIP/2.0/UDP 1 0.3.0.185:4060;branch=z9hG4bK0274.dd46eeff6c2e63dfce9ab8268123f312.0..Via: SIP/2.0/UDP 10.3.0.187:6060 ;branch=z9hG4bK0274.a63fdda300000000000000000000 0000.0..To: <sip:alice@mnc001.mcc001.3gppnetwork.org >;tag=2275281208..From: <sip:alice@mnc001.mcc001.3gppnetwork.org >;tag=9bb9548d48f8c3c628773a7ade1a e022-a078..CSeq: 24505 NOTIFY..Call-ID: dc8101b5-9f8b-c010-9160-d49a1745f7b d..Content-Length: 1398..User-Agent: Kamailio S-CSCF..Contact: <sip:scscf.m nc001.mcc001.3gppnetwork.org:6060>..Event: reg..Max-Forwards: 69..Subscript ion-State: active;expires=581479..Content-Type: application/reginfo+xml.... <?xml version="1.0"?>.<reginfo xmlns="urn:ietf:params:xml:ns:reginfo" versi on="38" state="full">..<registration aor="sip:alice@mnc001.mcc001.3gppnetwo rk.org" id="0x7f29e0645ce8" state="active">...<contact id="0x7f29e0647128" state="active" event="registered" expires="3135" q="0.000">....<uri>sip:ali ce@10.3.0.161:49428;transport=udp</uri>...<unknown-param name="+g.3gpp.smsi p"></unknown-param>...<unknown-param name="+g.3gpp.icsi-ref">"urn0X0.07FFF0 00BDBP-1022urn-70X0.07FFF000BDB9P-10223gpp-application.ims.iari.gsma-vs"</u nknown-param>...</contact>...<contact id="0x7f29e065aa28" state="active" ev ent="registered" expires="3225" q="0.000">....<uri> sip:alice@10.3.0.161:499 34;transport=udp</uri>...<unknown-param name="+g.3gpp.icsi-ref">"urn0X0.000 00EBB514F8P-1022urn-70X0.07F29E4A137CBP-10223gp # U 10.3.0.185 -> 10.3.0.161 +21737@1480:601 #17 p-application.ims.iari.gsma-vs"</unknown-param>...<unknown-param name="+g.3 gpp.smsip"></unknown-param>...<unknown-param name="expires">"600000"</unkno wn-param>...</contact>...<contact id="0x7f29e065ecd0" state="active" event= "registered" expires="3599" q="0.000">....<uri>sip:alice@10.3.0.161:62602 ;t ransport=udp</uri>...<unknown-param name="+g.3gpp.icsi-ref">"urn0X0.0558E28 04FB7P-1022urn-70X0P+03gpp-application.ims.iari.gsma-vs"</unknown-param>... <unknown-param name="+g.3gpp.smsip"></unknown-param>...<unknown-param name= "expires">"600000"</unknown-param>...</contact>..</registration>.</reginfo> . # U 10.3.0.185:4060 -> 10.3.0.161:49513 #18 NOTIFY sip:alice@10.3.0.161:49513;transport=udp SIP/2.0..Via: SIP/2.0/UDP 1 0.3.0.185:4060;branch=z9hG4bKa26e.b002c543e82c8cd2471829e5f2fbb146.0..Via: SIP/2.0/UDP 10.3.0.187:6060 ;branch=z9hG4bKa26e.bab0c7d300000000000000000000 0000.0..To: <sip:alice@mnc001.mcc001.3gppnetwork.org >;tag=2274232905..From: <sip:alice@mnc001.mcc001.3gppnetwork.org >;tag=9bb9548d48f8c3c628773a7ade1a e022-bb04..CSeq: 24508 NOTIFY..Call-ID: 8bdb427a-cfbc-521d-6914-8af9744e7fb d..Content-Length: 1397..User-Agent: Kamailio S-CSCF..Contact: <sip:scscf.m nc001.mcc001.3gppnetwork.org:6060>..Event: reg..Max-Forwards: 69..Subscript ion-State: active;expires=580431..Content-Type: application/reginfo+xml.... <?xml version="1.0"?>.<reginfo xmlns="urn:ietf:params:xml:ns:reginfo" versi on="41" state="full">..<registration aor="sip:alice@mnc001.mcc001.3gppnetwo rk.org" id="0x7f29e0645ce8" state="active">...<contact id="0x7f29e0647128" state="active" event="registered" expires="3135" q="0.000">....<uri>sip:ali ce@10.3.0.161:49428;transport=udp</uri>...<unknown-param name="+g.3gpp.smsi p"></unknown-param>...<unknown-param name="+g.3gpp.icsi-ref">"urn0X0.07FFF0 00BDBP-1022urn-70X0.07FFF000BDB9P-10223gpp-application.ims.iari.gsma-vs"</u nknown-param>...</contact>...<contact id="0x7f29e065aa28" state="active" ev ent="registered" expires="3225" q="0.000">....<uri> sip:alice@10.3.0.161:499 34;transport=udp</uri>...<unknown-param name="+g.3gpp.icsi-ref">"urn0X0.000 00EBB514FP-1022urn-70X0.07F29E4A137CBP-10223gpp # U 10.3.0.185 -> 10.3.0.161 +21738@1480:600 #19 -application.ims.iari.gsma-vs"</unknown-param>...<unknown-param name="+g.3g pp.smsip"></unknown-param>...<unknown-param name="expires">"600000"</unknow n-param>...</contact>...<contact id="0x7f29e065ecd0" state="active" event=" registered" expires="3599" q="0.000">....<uri>sip:alice@10.3.0.161:62602 ;tr ansport=udp</uri>...<unknown-param name="+g.3gpp.icsi-ref">"urn0X0.0558E280 4FB7P-1022urn-70X0P+03gpp-application.ims.iari.gsma-vs"</unknown-param>...< unknown-param name="+g.3gpp.smsip"></unknown-param>...<unknown-param name=" expires">"600000"</unknown-param>...</contact>..</registration>.</reginfo>. # U 10.3.0.185:4060 -> 10.3.0.161:59883 #20 NOTIFY sip:alice@10.3.0.161:59883;transport=udp SIP/2.0..Via: SIP/2.0/UDP 1 0.3.0.185:4060;branch=z9hG4bKfe92.82fddde6e4a09dafdade08e6ff2ef6b7.0..Via: SIP/2.0/UDP 10.3.0.187:6060 ;branch=z9hG4bKfe92.6cfb0d5700000000000000000000 0000.0..To: <sip:alice@mnc001.mcc001.3gppnetwork.org >;tag=2275595571..From: <sip:alice@mnc001.mcc001.3gppnetwork.org >;tag=9bb9548d48f8c3c628773a7ade1a e022-4f19..CSeq: 24504 NOTIFY..Call-ID: ab807656-6986-0242-5431-be9f6323787 8..Content-Length: 1398..User-Agent: Kamailio S-CSCF..Contact: <sip:scscf.m nc001.mcc001.3gppnetwork.org:6060>..Event: reg..Max-Forwards: 69..Subscript ion-State: active;expires=581765..Content-Type: application/reginfo+xml.... <?xml version="1.0"?>.<reginfo xmlns="urn:ietf:params:xml:ns:reginfo" versi on="37" state="full">..<registration aor="sip:alice@mnc001.mcc001.3gppnetwo rk.org" id="0x7f29e0645ce8" state="active">...<contact id="0x7f29e0647128" state="active" event="registered" expires="3135" q="0.000">....<uri>sip:ali ce@10.3.0.161:49428;transport=udp</uri>...<unknown-param name="+g.3gpp.smsi p"></unknown-param>...<unknown-param name="+g.3gpp.icsi-ref">"urn0X0.07FFF0 00BDBP-1022urn-70X0.07FFF000BDB9P-10223gpp-application.ims.iari.gsma-vs"</u nknown-param>...</contact>...<contact id="0x7f29e065aa28" state="active" ev ent="registered" expires="3225" q="0.000">....<uri> sip:alice@10.3.0.161:499 34;transport=udp</uri>...<unknown-param name="+g.3gpp.icsi-ref">"urn0X0.000 00EBB514F8P-1022urn-70X0.07F29E4A137CBP-10223gp # U 10.3.0.185 -> 10.3.0.161 +21739@1480:601 #21 p-application.ims.iari.gsma-vs"</unknown-param>...<unknown-param name="+g.3 gpp.smsip"></unknown-param>...<unknown-param name="expires">"600000"</unkno wn-param>...</contact>...<contact id="0x7f29e065ecd0" state="active" event= "registered" expires="3599" q="0.000">....<uri>sip:alice@10.3.0.161:62602 ;t ransport=udp</uri>...<unknown-param name="+g.3gpp.icsi-ref">"urn0X0.0558E28 04FB7P-1022urn-70X0P+03gpp-application.ims.iari.gsma-vs"</unknown-param>... <unknown-param name="+g.3gpp.smsip"></unknown-param>...<unknown-param name= "expires">"600000"</unknown-param>...</contact>..</registration>.</reginfo> . # I 10.3.0.161 -> 10.3.0.185 3:3 #22 ....E..4T...@..f...........~. ..NOTIFY sip:alice@10.3.0.161:56702 ;transport =udp SIP/2.0..Via: SIP/2.0/UDP 10.3.0.185:4060 ;branch=z9hG4bKea02.bd6e4c76e 778b145d63e9c39c5faf221.0..Via: SIP/2.0/UDP 10.3.0.187:6060 ;branch=z9hG4bKe a02.eb9813f5000000000000000000000000.0..To: <sip:alice@mnc001.mcc001.3gppne twork.org>;tag=1753523419..From: <sip:alice@mnc001.mcc001.3gppnetwork.org >; tag=9bb9548d48f8c3c628773a7ade1ae022-7ed6..CSeq: 24556 NOTIFY..Call-ID: dfa d767b-fcaa-5605-3043-fdab7277afaa..Content-Length: 1398..User-Agent: Kamail io S-CSCF..Contact: <sip:sc # U 10.3.0.185:4060 -> 10.3.0.161:62602 #23 SIP/2.0 200 OK..Via: SIP/2.0/UDP 10.3.0.161:62602 ;received=10.3.0.161;branc h=z9hG4bK2293850812;rport=62602..From: <sip:alice@mnc001.mcc001.3gppnetwork .org>;tag=2293851690..To: <sip:alice@mnc001.mcc001.3gppnetwork.org >;tag=9bb 9548d48f8c3c628773a7ade1ae022-442f..Call-ID: 54465103-da8d-a9a9-217a-bd8cab d0a465..CSeq: 5478 REGISTER..Contact: <sip:alice@10.3.0.161:49428 ;transport =udp>;q=0;expires=2823;language="en";+g.3gpp.smsip;+g.oma.sip-im.large-mess age;audio;+g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-application.ims.iari.gsma-vs ";+g.3gpp.cs-voice, <sip:alice@10.3.0.161:49934 ;transport=udp>;expires=2904 ;+g.3gpp.cs-voice;+g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-application.ims.iari .gsma-vs";audio;+g.oma.sip-im.large-message;+g.3gpp.smsip;language="en,fr"; +g.oma.sip-im, <sip:alice@10.3.0.161:62602 ;transport=udp>;expires=3240;+g.3 gpp.cs-voice;+g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-application.ims.iari.gsma -vs";audio;+g.oma.sip-im.large-message;+g.3gpp.smsip;language="en,fr";+ g.om a.sip-im..P-Associated-URI: <sip:alice@mnc001.mcc001.3gppnetwork.org >..Serv ice-Route: <sip:orig@scscf.mnc001.mcc001.3gppnetwork.org:6060;lr>..Server: Kamailio S-CSCF..Content-Length: 0..Warning: 392 10.3.0.187:6060 "Noisy fee dback tells: pid=30828 req_src_ip=10.3.0.186 req_src_port=4060 in_uri=sip: scscf.mnc001.mcc001.3gppnetwork.org:6060 out_uri=sip:scscf.mnc001.mcc001.3g ppnetwork.org:6060 via_cnt==4".... # U 10.3.0.185:4060 -> 10.3.0.161:64217 #24 NOTIFY sip:alice@10.3.0.161:64217;transport=udp SIP/2.0..Via: SIP/2.0/UDP 1 0.3.0.185:4060;branch=z9hG4bK061f.f9b5369f276621f592a50ad7d13b620e.0..Via: SIP/2.0/UDP 10.3.0.187:6060 ;branch=z9hG4bK061f.4044cf9700000000000000000000 0000.0..To: <sip:alice@mnc001.mcc001.3gppnetwork.org >;tag=2275735375..From: <sip:alice@mnc001.mcc001.3gppnetwork.org >;tag=9bb9548d48f8c3c628773a7ade1a e022-58ee..CSeq: 24503 NOTIFY..Call-ID: 9ab16525-8c6a-2261-3216-f9ef55729cb b..Content-Length: 1398..User-Agent: Kamailio S-CSCF..Contact: <sip:scscf.m nc001.mcc001.3gppnetwork.org:6060>..Event: reg..Max-Forwards: 69..Subscript ion-State: active;expires=581888..Content-Type: application/reginfo+xml.... <?xml version="1.0"?>.<reginfo xmlns="urn:ietf:params:xml:ns:reginfo" versi on="36" state="full">..<registration aor="sip:alice@mnc001.mcc001.3gppnetwo rk.org" id="0x7f29e0645ce8" state="active">...<contact id="0x7f29e0647128" state="active" event="registered" expires="3135" q="0.000">....<uri>sip:ali ce@10.3.0.161:49428;transport=udp</uri>...<unknown-param name="+g.3gpp.smsi p"></unknown-param>...<unknown-param name="+g.3gpp.icsi-ref">"urn0X0.07FFF0 00BDBP-1022urn-70X0.07FFF000BDB9P-10223gpp-application.ims.iari.gsma-vs"</u nknown-param>...</contact>...<contact id="0x7f29e065aa28" state="active" ev ent="registered" expires="3225" q="0.000">....<uri> sip:alice@10.3.0.161:499 34;transport=udp</uri>...<unknown-param name="+g.3gpp.icsi-ref">"urn0X0.000 00EBB51718P-1022urn-70X0.07F29E4A137CBP-10223gp --

1 0

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