Hi,
In relation to the following mail(to recapitulate and summarize), I need
few clarifications..
As a part of s2s federation, I have been able to do the following..
1) Both sun and moon machines are on LAN. 501 user is registered with IM
account on sun and 502 on moon. From 501 client I am able to add 502 as
buddy (to 501) and vice versa.Unable to do @call, @xfer and @conf for
which XX-7238 <http://track.sipfoundry.org/browse/XX-7238> is raised.
2) Created test account on gmail. Using, the s2s screen in end user
portal(of 501), added this test account as External account(for 501
user). After this, I could see all the contacts associated with the test
account added as buddies to 501 user.I was able to chat with one of the
buddies online as well.
I guess that this is what is "federation with Gtalk". Now, while
chatting from 501 with one of the buddies, I wanted to do a conference
chat by inviting another buddy too into the chat. It did not work. So,
given the fact that there should be a conference already created(from
features > conference) for the conference chat to work and also that
this conference is relevant to sipx user(501) only (and not to the buddy
that got added from External account), I guess that this is the expected
behavior. Please confirm.
PS: Please let me know if I am missing anything(that is supposed to be
working and not tried..)
PPS: Also please note that, I could get the scenario 2 working without
providing the "gmail.com" in list of allowed servers in the s2s
federation setting page. In other words I did not change anything in S2S
page, to chat from scs user to a gmail buddy. Please advise if it is
intended to work like that or is a bug.
Thanks in Advance,
Chitralekha.
Chitralekha wrote:
Robert Joly wrote:
Please note that both the "Server1" and "Server2" are located
in the IntRAnet.
The below described scenario's are performed for the
Servers(Server1 and Server2) available in the IntRAnet and
not between SCS and Internet.
Thanks,
Chitralekha.
Hi All,
Issues with respect to "server to server federation for
openfire" i.e XX-6519
<http://track.sipfoundry.org/browse/XX-6519> and XX-6797
<http://track.sipfoundry.org/browse/XX-6797> is resolved and
working successfully.
I could successfully Add Pidgin client "User X" (registered
to Server1) as a buddy to the Pidgin client "UserY"(
registered to Server2).Instant Messaging between UserX and
UserY works successfully.
My Queries:
---------------------
1.Phones associated with the UserX or UserY does not ring on
issuing the command "@call" or "@xfer" while UserX and UserY
are connected through IM chat,They fail to get connected with
the Audio.
The command "@call" or "@xfer" just enter in the IM chat
window as a plain text message.
2.UserY fails to get added to the running conference chat
initiated by the user UserX.
[Procedure:-
A conference chat is established and UserX is the owner of
the Conference.When UserX tries to add UserY (by drag and
drop from the available buddy list,it fails.The Invitation
does not reach the UserY]
3.UserY fails directly to join the conference available on
the Server1.]
[Procedure:-
From the TUI of the Pidgin client UserY navigate to the
Tools--->Room list--->Get List--->edit the pre-populated
server to "conference.server1.qantom.int " and click on the
"Find Rooms" button.No conference room is listed on the "room
list" window]
Kindly advice if this is the design intent or can be raised
an Improvement issue or this is a Bug.
The @call, @xfer and @conf directives only work within a given system.
Therefore the behaviors you observe are correct. Having said that, the
system should return you some kind of failure message when you issue
these failing directives. If you do not see any such messages, please
open a tracker.
An Improvement issue is logged:
http://track.sipfoundry.org/browse/XX-7238
(Display failure message when "@call","@xfer" and "@conf"directives
are issued between s2s IM Chat.)
Thanks,
Chitralekha.
------------------------------------------------------------------------
_______________________________________________
sipx-dev mailing list [email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
sipXecs IP PBX -- http://www.sipfoundry.org/
_______________________________________________
sipx-dev mailing list [email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
sipXecs IP PBX -- http://www.sipfoundry.org/
