sr-users

sr-users@lists.kamailio.org

8 participants
37523 discussions

rtpproxy failed to load
by Tom Braarup Cuykens 09 Mar '15

09 Mar '15

kb.asipto.com/kamailio:skype-like-service-in-less-than-one-hour I found this guide for an older version of Kamailio, but there seems to be some issues when trying to use it on the latest stable version. When I try to start Kamailio i get this : [....] 0(17153) INFO: tls [tls_init.c:399]: init_tls_compression(): tls: init_tls: disabling compression... 0(17153) ERROR: <core> [cfg.y:3286]: yyparse(): cfg. parser: failed to find command force_rtp_proxy (params 0) 0(17153) : <core> [cfg.y:3426]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 729, column 19: unknown command, missing loadmodule? 0(17153) ERROR: <core> [cfg.y:3286]: yyparse(): cfg. parser: failed to find command force_rtp_proxy (params 0) 0(17153) : <core> [cfg.y:3426]: yyerror_at(): parse error in config fil[FAILc/kamailio/kamailio.cfg, line 806, column 19: unknown command, missing loadmodule? ERROR: bad config file (2 errors) ... It seems it cannot load the rtpproxy module or that force_rtp_proxy command does not exist. For Debian the modules are located in /usr/lib/x86_64-linux-gnu/kamailio/modules/ and it was found there, seems to be loaded in the config file (line 5 and 235). According to the rtpproxy doc the module has this command. Does anyone have an idea what could be the issue ? I am planning to update this guide for the current version once I fixed all the issues. The most easy issues are the db/usernames/password and the path to the modules. -- Med venlig hilsen Tom Braarup Cuykens plusTEL.dk

2 1

lua_run seems to be working in asynchronous way
by José Seabra 09 Mar '15

09 Mar '15

Hi there, I'm using kamailio version 4.2.2 to a short time, and I'm using lua scripts to build some avps with information needed to make calls(lua functions uses redis as source data to build avp data.), what i have noticed today making some tests is that when i make a call my lua function: if(!lua_run("get_prefs","$fU","$fd")) { xdbg("SCRIPT: failed to execute lua function!\n"); } kamailio gets the avp's after send the invite to the destine,(the invite will fail because kamailio needs avp information). it seems that kamailio calls the lua_run in asynchronous way, i never noticed that before in old version. is that a normal behavior or it is an issue in this version? Best Regards -- Cumprimentos José Seabra

2 5

Re: [SR-Users] kamailio asterisk
by Slava Bendersky 08 Mar '15

08 Mar '15

Hello Everyone, I set up tcp and udp for right now to test all config and dialog is not established correctly. Call between extensions not working. Call from extesnsion to extension going right a way to voicemail. Any help thank you. Here one call debug. http://fpaste.org/195572/14258553/ Slava. From: "Slava Bendersky" <volga629(a)networklab.ca> To: miconda(a)gmail.com Cc: "sr-users" <sr-users(a)lists.sip-router.org> Sent: Tuesday, March 3, 2015 9:08:19 AM Subject: Re: [SR-Users] kamailio asterisk Hello Daniel, Is notify should follow subscribe routes ? Here SUBSCRIBE completely look normal to me. <--- SIP read from UDP:10.18.130.46:5060 ---> SUBSCRIBE sip:10102@networklab.ca SIP/2.0 Record-Route: <sip:kamailio_pub_ip:5081;transport=tls;lr=on;ftag=08c99307d3;nat=yes> Accept: application/simple-message-summary Via: SIP/2.0/UDP 10.18.130.46;branch=z9hG4bKdee2.b83c2028dc57c641d2b8cad968347d6a.0;i=2 Via: SIP/2.0/TLS 192.168.0.16:5063;rport=5063;received=client_pub_ip;branch=z9hG4bK0c54032bd8905d262 Max-Forwards: 69 From: "10102" <sips:10102@networklab.ca>;tag=08c99307d3 To: <sips:10102@networklab.ca> Call-ID: cea703eb8c21f709 CSeq: 1096440084 SUBSCRIBE Allow: ACK, BYE, CANCEL, INVITE, MESSAGE, NOTIFY, OPTIONS, REFER, SUBSCRIBE, UPDATE Allow-Events: message-summary Authorization: Digest username="10102",realm="networklab.ca",nonce="29ac01f1",uri="sips:10102@networklab.ca",response="0298c2a93bdd4969a3cd0b757d671dbb",algorithm=MD5 Contact: <sips:10102@client_pub_ip:5063>;audio Event: message-summary Expires: 3600 Supported: eventlist, replaces, timer User-Agent: Media5-fone/4.1.6.3283 Android/4.1.2 Content-Length: 0 Path: <sip:outbound@10.18.130.46;lr;received=sip:client_pub_ip:5063%3Btransport%3Dtls> P-hint: outbound Slava From: "Daniel-Constantin Mierla" <miconda(a)gmail.com> To: "Slava Bendersky" <volga629(a)networklab.ca> Cc: "sr-users" <sr-users(a)lists.sip-router.org> Sent: Tuesday, March 3, 2015 1:50:03 AM Subject: Re: [SR-Users] kamailio asterisk Hello, I pushed a fix for it -- the issue was in a LM_DBG() trying to print te address for local socket, but it was not set yet, it was affecting only when running in debug mode with debug=3. I pushed the patch to branch 4.2, so if you want the fix, then you have to install from git branch 4.2. For REGISTER, you need to add the Path header (see path module), otherwise the OPTIONS and INVITE sent out to the phone are not going via Kamailio. You have to check the version of your Asterisk to be one that supports Path. Cheers, Daniel On 27/02/15 14:40, Slava Bendersky wrote: Hello Daniel, Here paste for gdb http://fpaste.org/191338/25043949/ I got REGISTER and SUBSCRIBE start working correctly I see on asterisk correct record routes and sip traffic flow, but when asterisk or client ( soft phone) send OPTIONS or NOTIFY can't get properly relay it. This is SUBSCRIBE route. <--- Transmitting (NAT) to 10.18.130.46:5060 ---> SIP/2.0 200 OK Via: SIP/2.0/UDP 10.18.130.46;branch=z9hG4bKf852.e0223f39c2bbad8366fdf1b7cb22b336.0;i=8;received=10.18.130.46;rport=5060 Via: SIP/2.0/TLS 192.168.88.252:5062;received=Client public ip;branch=z9hG4bK0bbe1f7d27257bba9;rport=5062 Record-Route: <sip:10.18.130.46;r2=on;lr=on;ftag=a185d974ec;nat=yes> Record-Route: <sip:PUBLIC_KAMAILIO_IP:5081;transport=tls;r2=on;lr=on;ftag=a185d974ec;nat=yes> From: "Slava Bendersky" <sips:10101@networklab.ca> ;tag=a185d974ec To: <sips:10101@networklab.ca> ;tag=as00757d3e Call-ID: b08adb1ad1804a83 CSeq: 236711034 SUBSCRIBE Server: FPBX-2.11.0(11.15.1) Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE Supported: replaces, timer Expires: 3600 Contact: <sip:10101@10.18.130.50:5060> ;expires=3600 Content-Length: 0 Slava. From: "Daniel-Constantin Mierla" <miconda(a)gmail.com> To: "Slava Bendersky" <volga629(a)networklab.ca> Cc: "sr-users" <sr-users(a)lists.sip-router.org> Sent: Friday, February 27, 2015 6:42:33 AM Subject: Re: [SR-Users] kamailio asterisk Hello, I asked for the wrong command, as the bt full was already sent before -- I wanted the output from gdb for: p *tcpconn Daniel On 27/02/15 04:10, Slava Bendersky wrote: BQ_BEGIN Hello Daniel, Here bt full from back trace. http://fpaste.org/191207/50064491/ Slava. From: "volga629" <volga629(a)skillsearch.ca> To: miconda(a)gmail.com , "Slava Bendersky" <volga629(a)networklab.ca> Cc: "sr-users" <sr-users(a)lists.sip-router.org> Sent: Thursday, February 26, 2015 9:56:48 PM Subject: Re: [SR-Users] kamailio asterisk Hello Daniel, I tried $rz option on top of request route and that where I see wrong request uri like sip:sips : . And as far I can see it happenes only for SUBSCRIBE INVITE and NOTIFY. if($rz=="sips") { $ru = "sip" + $(ru{s.substr,4,0}); } Slava. Sent from mobile device typos are expected. From: Daniel-Constantin Mierla <miconda(a)gmail.com> Sent: Feb 25, 2015 1:04 PM To: Slava Bendersky Cc: sr-users Subject: Re: [SR-Users] kamailio asterisk Hello, On 25/02/15 17:19, Slava Bendersky wrote: BQ_BEGIN Hello Daniel, substr you suggested didn't worked. See my previous email. your previous email didn't say anything about the results. That's why I asked. Be sure you don't have those spaces that are in the email you wrote. Also, I had more parenthesis in the parameter of the subst_uri(). Or you can try the alternative with: if($rz=="sips") { $ru = "sip" + $(ru{s.substr,4,0}); } I asked for more details from the backtrace to confirm that what I found is the cause for the crash in this case -- see one of my previous emails from today. Cheers, Daniel BQ_END -- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Kamailio World Conference, May 27-29, 2015 Berlin, Germany - http://www.kamailioworld.com BQ_END -- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Kamailio World Conference, May 27-29, 2015 Berlin, Germany - http://www.kamailioworld.com _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users(a)lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

1 0

Group call advice: remove calling branch after alias_db_lookup/lookup_branches
by Anthony Messina 08 Mar '15

08 Mar '15

In terms of implementing "group" calling via the append_branch feature of both alias_db_lookup followed by lookup_branches, I'm looking for a reliable way to ensure that if the caller happens to be a member of the group (list of branches), the branch that's created to the original caller is dropped. Originally, I was thinking of comparing $rU and $fU in branch_route, but this would limit the ability for one contact of an AOR to call another contact of the same AOR. Can anyone offer an example of an efficient method to accomplish this? -- Anthony - https://messinet.com/ - https://messinet.com/~amessina/gallery 8F89 5E72 8DF0 BCF0 10BE 9967 92DC 35DC B001 4A4E

2 3

ndb_redis set <null> reply to EXISTS query
by Yuriy Gorlichenko 06 Mar '15

06 Mar '15

Hello I try to get some replies from redis. Time after time redis request give me null result. But redis bs not disconnected. This happens only with websocket endpoints. My queries is: redis_cmd("srv1", "EXISTS $si", "s"); So at xLOG i see that $si correctly sended, but result is null. At db I keep key IP with value TIMESTAMP Intresting that route, that givesme this result idependend of WS or UDP endpoint. IT does not know about it anything.

2 11

Route Between WebSockets without rtpengine getting into the mix
by Don Fanning 05 Mar '15

05 Mar '15

Hello All, Prior to going down the rtpengine path for another need, calling was working fine between WSS client. Now that I've added in some pieces from caruizdiaz's config [ https://github.com/caruizdiaz/kamailio-ws/blob/master/kamailio-ws.cfg] relating to SETUP_BY_TRANSPORT, it has broken that functionality. Is there a way to skip rtpengine if the originator and destination are both on wss? route[RELAY] { # enable additional event routes for forwarded requests # - serial forking, RTP relaying handling, a.s.o. if (is_method("INVITE|BYE|SUBSCRIBE|UPDATE")) { t_on_branch("MANAGE_BRANCH"); t_on_reply("MANAGE_REPLY"); } if (is_method("INVITE")) { route(SETUP_BY_TRANSPORT); if(!t_is_set("failure_route")) t_on_failure("MANAGE_FAILURE"); } if (!t_relay()) { sl_reply_error(); } exit; } route[SETUP_BY_TRANSPORT] { if ($ru =~ "transport=ws") { xlog("L_INFO", "Request going to WS"); if(sdp_with_transport("RTP/SAVPF")) { rtpengine_manage("rtcp-mux-demux trust-address replace-origin replace-session-connection ICE=force DTLS=passive"); t_on_reply("REPLY_WS_TO_WS"); return; } #rtpengine_manage("rtcp-mux-demux trust-address replace-origin replace-session-connection ICE=force DTLS=passive RTP/SAVP"); t_on_reply("REPLY_FROM_WS"); } else if ($proto =~ "ws") { xlog("L_INFO", "Request coming from WS"); rtpengine_manage("rtcp-mux-demux trust-address replace-origin replace-session-connection ICE=remove DTLS=passive RTP/SAVP"); t_on_reply("REPLY_TO_WS"); } else { xlog("L_INFO", "This is a classic phone call"); rtpengine_manage("replace-origin replace-session-connection"); t_on_reply("MANAGE_CLASSIC_REPLY"); } } Thanks for any help! -Don

2 1

segfault problem with unixodbc module
by Lucas Wals Ochoa 05 Mar '15

05 Mar '15

Hello, this is the first time I send a question here, hope my english is good enough to explain my problem. I have a Kamailio 4.1.8+RTPProxy setup working, but recently I saw RTP Engine proxy, so I decided to give a try. I installed the latest kamailio stable version (4.2.3) and adapt the configuration I have(that uses a MariaDB database), to try the rtpengine module, but I couldn't even start kamailio process, cause I received a segfault problem at unixodbc module. The version of unixodbc that I installed is 2.3.1-10 That was the first time I encounter this error. I thought that maybe the database I have created with the version 4.1.8 wasn't compatible, so I decided to create a new database, but the problem persisted. So I'm here to know if someone know something about this, or have had a similar problem. I attached the system log for Kamailio, and a backtrace I made using "gdb" with the corefile that Kamailio creates when it crash. Log: Mar 4 12:46:35 localhost systemd: Starting SYSV: Kamailio is a fast, reliable and flexible SIP Server.... Mar 4 12:46:35 localhost kamailio: WARNING: <core> [socket_info.c:1392]: fix_hostname(): could not rev. resolve 10.0.0.70 Mar 4 12:46:35 localhost /usr/sbin/kamailio[2369]: WARNING: tm [tm.c:845]: mod_init(): WARNING: mod_init: reparse_on_dns_failover is enabled on a multihomed host -- check the readme of tm module! Mar 4 12:46:35 localhost /usr/sbin/kamailio[2369]: INFO: rr [../outbound/api.h:54]: ob_load_api(): Failed to import bind_ob Mar 4 12:46:35 localhost /usr/sbin/kamailio[2369]: INFO: rr [rr_mod.c:160]: mod_init(): outbound module not available Mar 4 12:46:35 localhost /usr/sbin/kamailio[2369]: INFO: usrloc [hslot.c:53]: ul_init_locks(): locks array size 1024 Mar 4 12:46:35 localhost /usr/sbin/kamailio[2369]: INFO: auth [auth_mod.c:350]: mod_init(): auth: qop set, but nonce-count (nc_enabled) support disabled Mar 4 12:46:35 localhost kernel: kamailio[2369]: segfault at 10070 ip 00007fc3d554df7e sp 00007fff89556450 error 4 in libmyodbc5w.so[7fc3d5527000+47000] Mar 4 12:46:35 localhost kamailio: ERROR: <core> [daemonize.c:315]: daemonize(): Main process exited before writing to pipe Mar 4 12:46:35 localhost kamailio: Starting kamailio: Mar 4 12:46:35 localhost systemd: kamailio.service: control process exited, code=exited status=1 Mar 4 12:46:35 localhost systemd: Failed to start SYSV: Kamailio is a fast, reliable and flexible SIP Server.. Mar 4 12:46:35 localhost systemd: Unit kamailio.service entered failed state. Backtrace of gdb: Using host libthread_db library "/lib64/libthread_db.so.1". Core was generated by `/usr/sbin/kamailio -P /var/run/kamailio.pid -m 64 -M 8 -u kamailio -g kamailio'. Program terminated with signal 11, Segmentation fault. #0 0x00007fc3d554df7e in get_ctype () from /usr/lib64/libmyodbc5.so Missing separate debuginfos, use: debuginfo-install kamailio-4.2.3-3.1.x86_64 (gdb) backtrace #0 0x00007fc3d554df7e in get_ctype () from /usr/lib64/libmyodbc5.so #1 0x00007fc3d554dfac in init_parser () from /usr/lib64/libmyodbc5.so #2 0x00007fc3d554ec41 in parse () from /usr/lib64/libmyodbc5.so #3 0x00007fc3d5553484 in prepare () from /usr/lib64/libmyodbc5.so #4 0x00007fc3d5559e9c in SQLPrepareWImpl () from /usr/lib64/libmyodbc5.so #5 0x00007fc3d5559eb9 in SQLExecDirectW () from /usr/lib64/libmyodbc5.so #6 0x00007fc3de43b05f in SQLExecDirect () from /lib64/libodbc.so.2 #7 0x00007fc3de695302 in db_unixodbc_submit_query () from /usr/lib64/kamailio/modules/db_unixodbc.so #8 0x00007fc3de21522e in db_do_submit_query () from /usr/lib64/kamailio/libsrdb1.so.1 #9 0x00007fc3de215cf7 in db_do_query_internal () from /usr/lib64/kamailio/libsrdb1.so.1 #10 0x00007fc3de21661a in db_do_query () from /usr/lib64/kamailio/libsrdb1.so.1 #11 0x00007fc3de696d90 in db_unixodbc_query () from /usr/lib64/kamailio/modules/db_unixodbc.so #12 0x00007fc3de20ce90 in db_table_version () from /usr/lib64/kamailio/libsrdb1.so.1 #13 0x00007fc3da209693 in init_ds_db () from /usr/lib64/kamailio/modules/dispatcher.so #14 0x00007fc3da1f4f1a in mod_init () from /usr/lib64/kamailio/modules/dispatcher.so #15 0x0000000000520e8d in init_mod () #16 0x0000000000520be8 in init_mod () #17 0x000000000052119a in init_modules () #18 0x0000000000517951 in main () Hope someone can help me. Thanks in advance.

3 5

WARNING: <core> [local_timer.c:83]: _local_timer_dist_tl(): 0 expire timer added"?
by Anthony Messina 05 Mar '15

05 Mar '15

Good day. Is anyone able to let me in on what this means "WARNING: <core> [local_timer.c:83]: _local_timer_dist_tl(): 0 expire timer added"? I just started seeing this after pulling down 5c1a9df from git and it seems like something that I probably don't want happening. -- Anthony - https://messinet.com/ - https://messinet.com/~amessina/gallery 8F89 5E72 8DF0 BCF0 10BE 9967 92DC 35DC B001 4A4E

3 13

wss calls between devices works but strange error
by Don Fanning 05 Mar '15

05 Mar '15

Hi All, I'm placing calls between two devices over WSS and sipML5. Connection seems to work and stays up (despite some grumbling sometimes with 603 failed to get local SDP) but my question is the following log entries - could someone translate what is happening here? Thanks! Mar 5 03:35:19 sandbox /usr/local/sbin/kamailio[4917]: WARNING: <core> [tcp_main.c:1221]: tcp_do_connect(): 127.0.0.2:5061: could not find corresponding listening socket for 127.0.0.1, using default... Mar 5 03:35:19 sandbox /usr/local/sbin/kamailio[4917]: ERROR: <core> [tcp_main.c:2740]: tcpconn_1st_send(): connect 127.0.0.2:5061 failed (RST) Connection refused Mar 5 03:35:19 sandbox /usr/local/sbin/kamailio[4917]: ERROR: <core> [tcp_main.c:2750]: tcpconn_1st_send(): 127.0.0.2:5061: connect & send for 0x7f0eb3944ac0 failed: Connection refused (111) Mar 5 03:35:19 sandbox /usr/local/sbin/kamailio[4917]: ERROR: <core> [forward.h:247]: msg_send(): tcp_send failed Mar 5 03:35:19 sandbox /usr/local/sbin/kamailio[4917]: ERROR: sl [sl_funcs.c:387]: sl_reply_error(): ERROR: sl_reply_error used: Unfortunately error on sending to next hop occurred (477/SL) Mar 5 03:35:19 sandbox /usr/local/sbin/kamailio[4917]: INFO: <script>: Request in RELAY - call is {<null>} for {106E} Mar 5 03:35:19 sandbox /usr/local/sbin/kamailio[4917]: WARNING: <core> [tcp_main.c:1221]: tcp_do_connect(): 127.0.0.2:5061: could not find corresponding listening socket for 127.0.0.1, using default... Mar 5 03:35:19 sandbox /usr/local/sbin/kamailio[4917]: ERROR: <core> [tcp_main.c:2740]: tcpconn_1st_send(): connect 127.0.0.2:5061 failed (RST) Connection refused Mar 5 03:35:19 sandbox /usr/local/sbin/kamailio[4917]: ERROR: <core> [tcp_main.c:2750]: tcpconn_1st_send(): 127.0.0.2:5061: connect & send for 0x7f0eb3944ac0 failed: Connection refused (111) Mar 5 03:35:19 sandbox /usr/local/sbin/kamailio[4917]: ERROR: <core> [forward.h:247]: msg_send(): tcp_send failed Mar 5 03:35:19 sandbox /usr/local/sbin/kamailio[4917]: ERROR: sl [sl_funcs.c:387]: sl_reply_error(): ERROR: sl_reply_error used: Unfortunately error on sending to next hop occurred (477/SL) Mar 5 03:35:21 sandbox /usr/local/sbin/kamailio[4917]: INFO: <script>: Request in RELAY - call is {<null>} for {106E} Mar 5 03:35:21 sandbox /usr/local/sbin/kamailio[4917]: WARNING: <core> [tcp_main.c:1221]: tcp_do_connect(): 127.0.0.2:5061: could not find corresponding listening socket for 127.0.0.1, using default... Mar 5 03:35:21 sandbox /usr/local/sbin/kamailio[4917]: ERROR: <core> [tcp_main.c:2740]: tcpconn_1st_send(): connect 127.0.0.2:5061 failed (RST) Connection refused Mar 5 03:35:21 sandbox /usr/local/sbin/kamailio[4917]: ERROR: <core> [tcp_main.c:2750]: tcpconn_1st_send(): 127.0.0.2:5061: connect & send for 0x7f0eb3944ac0 failed: Connection refused (111) Mar 5 03:35:21 sandbox /usr/local/sbin/kamailio[4917]: ERROR: <core> [forward.h:247]: msg_send(): tcp_send failed Mar 5 03:35:21 sandbox /usr/local/sbin/kamailio[4917]: ERROR: sl [sl_funcs.c:387]: sl_reply_error(): ERROR: sl_reply_error used: Unfortunately error on sending to next hop occurred (477/SL) Mar 5 03:35:25 sandbox /usr/local/sbin/kamailio[4917]: INFO: <script>: Request in RELAY - call is {<null>} for {106E} Mar 5 03:35:25 sandbox /usr/local/sbin/kamailio[4917]: WARNING: <core> [tcp_main.c:1221]: tcp_do_connect(): 127.0.0.2:5061: could not find corresponding listening socket for 127.0.0.1, using default... Mar 5 03:35:25 sandbox /usr/local/sbin/kamailio[4917]: ERROR: <core> [tcp_main.c:2740]: tcpconn_1st_send(): connect 127.0.0.2:5061 failed (RST) Connection refused Mar 5 03:35:25 sandbox /usr/local/sbin/kamailio[4917]: ERROR: <core> [tcp_main.c:2750]: tcpconn_1st_send(): 127.0.0.2:5061: connect & send for 0x7f0eb3944ac0 failed: Connection refused (111) Mar 5 03:35:25 sandbox /usr/local/sbin/kamailio[4917]: ERROR: <core> [forward.h:247]: msg_send(): tcp_send failed Mar 5 03:35:25 sandbox /usr/local/sbin/kamailio[4917]: ERROR: sl [sl_funcs.c:387]: sl_reply_error(): ERROR: sl_reply_error used: Unfortunately error on sending to next hop occurred (477/SL) Mar 5 03:35:33 sandbox /usr/local/sbin/kamailio[4918]: INFO: <script>: Request in RELAY - call is {<null>} for {106E} Mar 5 03:35:33 sandbox /usr/local/sbin/kamailio[4918]: WARNING: <core> [tcp_main.c:1221]: tcp_do_connect(): 127.0.0.2:5061: could not find corresponding listening socket for 127.0.0.1, using default... Mar 5 03:35:33 sandbox /usr/local/sbin/kamailio[4918]: ERROR: <core> [tcp_main.c:2740]: tcpconn_1st_send(): connect 127.0.0.2:5061 failed (RST) Connection refused Mar 5 03:35:33 sandbox /usr/local/sbin/kamailio[4918]: ERROR: <core> [tcp_main.c:2750]: tcpconn_1st_send(): 127.0.0.2:5061: connect & send for 0x7f0eb3944ac0 failed: Connection refused (111) Mar 5 03:35:33 sandbox /usr/local/sbin/kamailio[4918]: ERROR: <core> [forward.h:247]: msg_send(): tcp_send failed Mar 5 03:35:33 sandbox /usr/local/sbin/kamailio[4918]: ERROR: sl [sl_funcs.c:387]: sl_reply_error(): ERROR: sl_reply_error used: Unfortunately error on sending to next hop occurred (477/SL) Mar 5 03:35:49 sandbox /usr/local/sbin/kamailio[4918]: INFO: <script>: Request in RELAY - call is {<null>} for {106E} Mar 5 03:35:49 sandbox /usr/local/sbin/kamailio[4918]: WARNING: <core> [tcp_main.c:1221]: tcp_do_connect(): 127.0.0.2:5061: could not find corresponding listening socket for 127.0.0.1, using default... Mar 5 03:35:49 sandbox /usr/local/sbin/kamailio[4918]: ERROR: <core> [tcp_main.c:2740]: tcpconn_1st_send(): connect 127.0.0.2:5061 failed (RST) Connection refused Mar 5 03:35:49 sandbox /usr/local/sbin/kamailio[4918]: ERROR: <core> [tcp_main.c:2750]: tcpconn_1st_send(): 127.0.0.2:5061: connect & send for 0x7f0eb3944ac0 failed: Connection refused (111) Mar 5 03:35:49 sandbox /usr/local/sbin/kamailio[4918]: ERROR: <core> [forward.h:247]: msg_send(): tcp_send failed Mar 5 03:35:49 sandbox /usr/local/sbin/kamailio[4918]: ERROR: sl [sl_funcs.c:387]: sl_reply_error(): ERROR: sl_reply_error used: Unfortunately error on sending to next hop occurred (477/SL)

2 1

How to Use Multiple DMQ Notification Addresses
by Robert Boisvert 04 Mar '15

04 Mar '15

Hello all, I would like to setup a DMQ bus where servers can come on and offline and have DMQ continue working with the online servers. I'm having trouble understanding how to do that with the notification address. Can someone point me in the right direction? More specifically, suppose I have five servers named A, B, C, D, and E. I would like all of them to be on the DMQ bus when active but they may come up at different times. For example, when A, B and C start I want each of them to be on the same DMQ bus. However, the way I understand it, if I make E the notification address none will be on the bus because E is not active. I could create a circular notification chain where A uses B as a notification server, B uses C, and so on. Of course, there are problems when one or more servers are missing from the chain. Any help on this is greatly appreciated. Thanks, Bob

2 3

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

sr-users