Re: how to send multicast message to MUC and privatemessage together

Mailing list - Fri, 2015-11-06 04:00
<message to='multicast.header2.org' from='a< at >header1.org/work'> <addresses xmlns='http://jabber.org/protocol/address'> <address type='to' jid='to< at >header1.org'/> <address type='to' jid='cc< at >conference.header2.org'/> </addresses> <body>Hello, World!</body> </message> On Thu, Nov 5, 2015 at 8:58 PM, Gaurav Jain <monkeyfdude< at >gmail.com> wrote: _______________________________________________ ejabberd mailing list ejabberd< at >jabber.ru http://lists.jabber.ru/mailman/listinfo/ejabberd
Categories: ejabberd

how to send multicast message to MUC and private messagetogether

Mailing list - Fri, 2015-11-06 03:58
I use mod_multicast and I use 'to' attribute. I try to send message to non-muc user (abc< at >example.com) and a muc user ( mucuser< at >example.com) If I set message type to **chat** then I get an error it is not allowed to send private messages to conference. If I set it to **groupchat**, then I get `service-unavailable` for non-muc (private) user. How can I send multicast message to muc and non-muc (private) user in the same message? _______________________________________________ ejabberd mailing list ejabberd< at >jabber.ru http://lists.jabber.ru/mailman/listinfo/ejabberd
Categories: ejabberd

Re: ejabberdctl reload_config doesn't work?

Mailing list - Wed, 2015-11-04 14:33
You are right, the command name and its definition is misleading, because most configurable values will not take effect: The configuration may be reloaded into memory, but that only takes immediate effect in static things like ACL and Access rules. Things handled by live processes (like port listeners and modules) do not take effect, only after a server restart (which is when the configured values are passed to the processes that will use them). The only way to change the configuration values in listeners and modules processes is using the WebAdmin, which allows to set different options and restart the corresponding processes. I'll clarify the command description and documentation. -- Badlop ProcessOne On 2 November 2015 at 18:04, Sedovic, Dave <david.sedovic< at >hpe.com> wrote:
Categories: ejabberd

ejabberdctl reload_config doesn't work?

Mailing list - Mon, 2015-11-02 16:04
We are running on ejabberd 15.07. I have made a change to the ejabberd.yml config file, and I run the "ejabberdctl reload_config" command, but do not see the config change taking effect. My first change was to increase the max_inactivity value for mod_http_bind. Based on what I see in the log file, this didn't seem to be taking effect. So I tried increasing the log_level, which is easy to check. But after doing the reload_config, the log_level stays the same. Is there something I'm missing? Thanks, Dave
Categories: ejabberd

[CFP] FOSDEM 2016, RTC devroom, speakers,volunteers neeeded

Mailing list - Sat, 2015-10-31 08:27
FOSDEM is one of the world's premier meetings of free software developers, with over five thousand people attending each year. FOSDEM 2016 takes place 30-31 January 2016 in Brussels, Belgium. http://fosdem.org This email contains information about: - Real-Time communications dev-room and lounge, - speaking opportunities, - volunteering in the dev-room and lounge, - related events around FOSDEM, including the XMPP summit, - social events (including the Saturday night dinner), - the Planet aggregation sites for RTC blogs Call for participation - Real Time Communications (RTC) ======================================================= The Real-Time dev-room and Real-Time lounge is about all things involving real-time communication, including: XMPP, SIP, WebRTC, telephony, mobile VoIP, codecs, privacy and encryption. The dev-room is a successor to the previous XMPP and telephony dev-rooms. We are looking for speakers for the dev-room and volunteers and participants for the tables in the Real-Time lounge. The dev-room is only on Saturday, 30 January 2016. The lounge will be present for both days. To discuss the dev-room and lounge, please join the FSFE-sponsored Free RTC mailing list: https://lists.fsfe.org/mailman/listinfo/free-rtc Speaking opportunities ---------------------- Note: if you used Pentabarf before, please use the same account/username Main track: the deadline for main track presentations is midnight today, 30 October. Leading developers in the Real-Time Communications field are encouraged to consider submitting a presentation to the main track at https://fosdem.org/submit Real-Time Communications dev-room: deadline 27 November Please also use the Pentabarf system to submit a talk proposal for the dev-room. On the "General" tab, please look for the "Track" option and choose "Real-Time devroom". https://penta.fosdem.org/submission/FOSDEM16/ Other dev-rooms: some speakers may find their topic is in the scope of more than one dev-room. It is permitted to apply to more than one dev-room but please be kind enough to tell us if you do this. You can find the full list of dev-rooms at https://www.fosdem.org/2016/schedule/tracks/ Lightning talks: deadline 27 November The lightning talks are an excellent opportunity to introduce a wider audience to your project. Given that dev-rooms are becoming increasingly busy, all speakers are encouraged to consider applying for a lightning talk as well as a slot in the dev-room. On the "General" tab, please look for the "Track" option and choose "Lightning Talks". https://fosdem.org/submit First-time speaking? -------------------- FOSDEM dev-rooms are a welcoming environment for people who have never given a talk before. Please feel free to contact the dev-room administrators personally if you would like to ask any questions about it. Submission guidelines --------------------- The Pentabarf system will ask for many of the essential details. Please remember to re-use your account from previous years if you have one. In the "Submission notes", please tell us about: - the purpose of your talk - any other talk applications (dev-rooms, lightning talks, main track) - availability constraints and special needs You can use HTML in your bio, abstract and description. If you maintain a blog, please consider providing us with the URL of a feed with posts tagged for your RTC-related work. We will be looking for relevance to the conference and dev-room themes, presentations aimed at developers of free and open source software about RTC-related topics. Please feel free to suggest a duration between 20 minutes and 55 minutes but note that the final decision on talk durations will be made by the dev-room administrators. As the two previous dev-rooms have been combined into one, we may decide to give shorter slots than in previous years so that more speakers can participate. Please note FOSDEM aims to record and live-stream all talks. The CC-BY license is used. For any questions, please join the FSFE-sponsored Free RTC mailing list: https://lists.fsfe.org/mailman/listinfo/free-rtc Volunteers needed ================= To make the dev-room and lounge run successfully, we are looking for volunteers: - FOSDEM provides video recording equipment and live streaming, volunteers are needed to assist in this - organizing one or more restaurant bookings (dependending upon number of participants) for the evening of Saturday, 30 January - participation in the Real-Time lounge - helping attract sponsorship funds for the dev-room to pay for the Saturday night dinner and any other expenses - circulating this Call for Participation to other mailing lists FOSDEM is made possible by volunteers and if you have time to contribute, please feel free to get involved through https://volunteers.fosdem.org/ Related events - XMPP and RTC summits ===================================== The XMPP Standards Foundation (XSF) has traditionally held a summit in the days before FOSDEM. There is discussion about a similar summit taking place on 28 and 29 January 2016 http://wiki.xmpp.org/web/Summit_19 - please join the mailing list for details: http://mail.jabber.org/mailman/listinfo/summit We are also considering a more general RTC or telephony summit, potentially on 29 January. Please join the Free-RTC mailing list and send an email if you would be interested in participating, sponsoring or hosting such an event. Social events and dinners ========================= The traditional FOSDEM beer night occurs on Friday, 29 January On Saturday night, there are usually dinners associated with each of the dev-rooms. Most restaurants in Brussels are not so large so these dinners have space constraints. Please subscribe to the Free-RTC mailing list for further details about the Saturday night dinner options and how you can register for a seat: https://lists.fsfe.org/mailman/listinfo/free-rtc Spread the word and discuss =========================== If you know of any mailing lists where this CfP would be relevant, please forward this email. If this dev-room excites you, please blog or microblog about it, especially if you are submitting a talk. If you regularly blog about RTC topics, please send details about your blog to the planet site administrators: http://planet.jabber.org ralphm< at >ik.nu http://planet.sip5060.net daniel< at >pocock.pro http://planet.opentelecoms.org daniel< at >pocock.pro Please also link to the Planet sites from your own blog or web site. Contact ======= For discussion and queries, please join the free-rtc mailing list: https://lists.fsfe.org/mailman/listinfo/free-rtc The dev-room administration team: Daniel Pocock <daniel< at >pocock.pro> Ralph Meijer <ralphm< at >ik.nu> Saúl Ibarra Corretgé <saul< at >ag-projects.com> Iain R. Learmonth <irl< at >debian.org> _______________________________________________ ejabberd mailing list ejabberd< at >jabber.ru http://lists.jabber.ru/mailman/listinfo/ejabberd
Categories: ejabberd

Re: Clarifications about ejabberd_stun

Mailing list - Fri, 2015-10-30 15:12
* Dominik George <nik< at >naturalnet.de> [2015-10-30 16:21]: The second address was used by an earlier STUN version (RFC 3489). ejabberd_stun implements RFC 5389, which no longer provides the corresponding functionality. Yes, via DNS. Unless you've set "auth_type: anonymous", ejabberd's authentication backend is used. Note that this won't work with SCRAM storage (because STUN does MD5 auth). If you have multiple virtual hosts configured, you also want to specify the "auth_realm" option. You should add DNS SRV records as described in the admin guide: http://docs.ejabberd.im/admin/guide/configuration/#stun-and-turn Clients *should* then discover the STUN/TURN services automatically. It does log these things if your loglevel is set to 4 or larger. Holger
Categories: ejabberd

Clarifications about ejabberd_stun

Mailing list - Fri, 2015-10-30 14:21
Hi, I have recently switched back to ejabberd from Prosody. I have a few questions about the STUN/TURN component. I activated ti with: - port: 3478 transport: udp module: ejabberd_stun use_turn: true turn_ip: "" turn_min_port: 49152 turn_max_port: 50152 - port: 3478 module: ejabberd_stun use_turn: true turn_ip: "" turn_min_port: 49152 turn_max_port: 50152 - port: 5349 module: ejabberd_stun tls: true certfile: "/etc/ssl/private/W_teckids.org.pem" use_turn: true turn_ip: "" turn_min_port: 49152 turn_max_port: 50152 Now I have a few questions: 1. As far as I understand, STUN needs two IP addresses on the host to work properly. How do I set the second address to use? 2. Should clients auto-discover the TURN transport when doing ICE? 3. How is authentication handled for TURN? 4. Is there anything more I have to do to make Jingle clients use STUN and TURN on the XMPP server? 5. Can I make the module log session registration and stuff like that to see if it works? Thanks in advance, Nik
Categories: ejabberd

[ANN] ejabberd 15.10

Mailing list - Thu, 2015-10-29 15:25
This month's ejabberd release contains new features, performance optimization, bugfixes and many other improvements. This release includes a brand new module to help with file transfer. In XMPP, transferring files between users required users to be online at the same time. It all changed with XEP-0363 and it is now possible to share file using HTTP protocol while doing the signaling over XMPP. Thanks to Holger and Evgeny, we are now pleased to include this feature in ejabberd core, with mod_http_upload. ejabberd now also includes a module to export metrics information about ejabberd behavior to Grapherl (https://github.com/processone/grapherl), a tool that was developed during the Google Summer of Code by Vanshdeep Singh. This is only the beginning, as we are planning to both increase the number of metrics and available backends in upcoming releases. As a start, you can now track the traffic (both from clients and between servers), the offline messages and the user registration and account deletion. We improved the overall performance of ejabberd, thanks to optimization in the XML parser. We also improved the documentation to help you set up mod_xmlrpc with OAuth for those who were already using it prior to 15.09 release. Finally, as usual, we fixed bugs and improved many features across the whole server. Here is the full list of changes. ## Changes ### Core - c2s: Let stop/1 close XEP-0198 sessions - c2s: Close socket when waiting for resume - s2s: Don't crash on certificates without extensions - xml: Optimizations in memory allocator - OAuth: Fix cyrsasl_oauth:mech_new call ### Modules - mod_http_upload: New HTTP File Upload module (XEP-0363) - mod_http_upload_quota: New module to support user quotas - mod_metrics: New simple metrics module for use with grapherl - mod_mam: Advertise XEP-0313 v0.4 support in room disco - mod_mam: Avoid MAM dups when routing to multiple resources ### Compilation - Make: Pass {C,CPP,LD}FLAGS used in main ./configure to deps - Use OTP directory structure for 'make install' - mix.lock should be commited to ensure consistent builds - Code cosmetic cleanup ### Commands - Let modules_update_specs report failures - Fix problem with --auth - Fix unauthenticated calls to commands with policy=user - Improve access_commands option backward compatibility ### Configuration - ejabberdctl.cfg: New CONTRIB_MODULES_CONF_DIR - Be able to merge old style configs with {listen,...} - Fix support for macros - mod_ping: New option ping_ack_timeout ## Feedback As usual, the release is tagged in the Git source code repository on Github: https://github.com/processone/ejabberd.git The source package and binary installers are available at ProcessOne: https://www.process-one.net/en/ejabberd/downloads/ If you suspect that you've found a bug, please search or fill a bug report on Github: https://github.com/processone/ejabberd/issues
Categories: ejabberd

Persistent MUC rooms and muc_registered table

Mailing list - Tue, 2015-10-27 14:19
Hi all, Persistent MUC room not stored in muc_registered table (db_type odbc, mysql). Table are always empty, but we have many persistent rooms. I checked room option (persistent true) inside muc_room table and also checked option via jabber client (Vacuum-IM). And i cann't find any sql inserts to muc_registered table in mod_muc's code.
Categories: ejabberd

Re: mod_muc_odbc performance

Mailing list - Mon, 2015-10-26 14:45
Mon, 26 Oct 2015 17:36:57 +0300 Vladimir Stafievsky <vladimir.stafievsky< at >syncopate.ru> wrote: I think the problem is not in lists:zf() but in the queries mod_muc doing to all rooms during processing this disco request. Each query is synchronous (get_state, or something). Anyway, you can try to play with this by changing the code: disabling this get_state calls, disabling disco requests in your client, etc.
Categories: ejabberd

Re: mod_muc_odbc performance

Mailing list - Mon, 2015-10-26 13:36
I think the bottleneck is in iq_disco_items function of mod_muc. We have >8500 groups, many users connects per second - each connected user call iq_disco_items when trying to join any room from his bookmarks. iq_disco_items have heavy load query inside - lists:zf, that looking for data from all groups but not only connected user's group. Maybe I'm wrong, because i'm erlang newbie. Anyway, thanks for any help. 14.10.2015 19:24, Evgeny Khramtsov пишет: _______________________________________________ ejabberd mailing list ejabberd< at >jabber.ru http://lists.jabber.ru/mailman/listinfo/ejabberd
Categories: ejabberd
Syndicate content