> 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. _______________________________________________ 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/
