#500 closed enhancement (fixed)

allow for send messages to routing to specific jabber resources or all jabber resources

Reported by: anonymous Owned by: wilmer
Priority: normal Milestone:
Component: Jabber Version: 1.2.3
Keywords: Cc:
IRC client+version: Client-independent Operating System: Linux
OS version/distro:


When chatting with my dad he has 3 different sessions into gtalk. and no matter what settings I set in gtalk, it does not reliably route the message to him. It usually routes to either his cellphone which he isn't looking at or his machine at home. A solution for this would be allowing bitlbee to message dad/* messaging the bare jid and then allowing the receivers sender handle it appropriately, or allowing me to message dad/home , dad/work , dad/cell. to do this well would also have to see the jid came from on receives.

because of this issue, for jabber i just use it to receive messages and have to respond with another jabber client which isn't optimal

Attachments (0)

Change History (6)

comment:1 Changed at 2009-06-07T16:02:29Z by Wilmer van der Gaast <wilmer@…>

I'm working on a proper fix here, this is indeed annoying. :-/ You can set the resource_select setting to "activity" instead of priority, this should automatically send your msgs to the resource he's writing you from.

comment:2 Changed at 2009-07-25T01:10:28Z by pmgalves@…

By any chance, don't you mean 'time' instead of activity? priority and time are the only options listed on the docs

comment:3 Changed at 2009-07-25T08:23:14Z by wilmer

Unfortunately that's a doc bug, the "time" setting is invalid. :-( That lie has been documented for a long time.

comment:4 Changed at 2009-10-12T12:16:52Z by anonymous

One additional option I would like is "broadcast", that is to broadcast the first message and then respond to the resource that responds. After a period of inactivity say X minutes the new message(s) are broadcasted again.

In effect first send to dad/* then when dad responds from dad/cell only send future messages to dad/cell. Until there is an inactivity period of X minutes..

comment:5 Changed at 2009-10-28T01:19:50Z by brian@…


Thank you so much! I was struggling with this today and thought the "time" switch on resource_priority would save me. It didn't work so I figured it was a bug and came here. Then I found out that I should be using "activity" and now all is working as desired. Thank you again!!


comment:6 Changed at 2010-05-11T22:03:54Z by wilmer

Resolution: fixed
Status: newclosed

BTW, also recent releases have a activity_timeout and when that one expires, BitlBee sends the msg to the bare JID which in most cases will result in a broadcast. This should solve the majority of the problems.

Modify Ticket

as closed The owner will remain wilmer.
The resolution will be deleted.

Add Comment

E-mail address and name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.