On Tue, Sep 16, 2008 at 5:06 PM, Joseph Attardi <[EMAIL PROTECTED]> wrote: > Scott Lawrence wrote: >> I suggest that the authentication be that of the user who is creating >> the outbound conference request - whoever logged in on the web interface >> to request that the new user be invited into the conference. > I took a look at the click to call code in sipXconfig, and I seem to be > using pretty much the same code, passing the same arguments to > SipService.sendRefer(). > > As a test, I logged in as a regular user and used the click to call > feature to call the conference extension, and it worked. So it must have > something to do with the user you're logged in as. Sure enough, when I > made a regular user owner of the conference, and logged in as that user, > I was able to add users to the conference using my UI. > > So the problem seems to be when you attempt to do this as superadmin. > This might demonstrate my lack of knowledge about parts of sipx, but I > looked in credential.xml and permission.xml, and superadmin does have an > entry in both files. So shouldn't this work?
You have to respond to the Challenge response with a REFER having the appropriate credentials. The credentials should be passed in to your code by sipxconfig when it calls you and asks to do the Refer. This should be identical to what click to call does. Ranga > > -- > Joe Attardi > [EMAIL PROTECTED] > _______________________________________________ > sipx-dev mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-dev > Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev > -- M. Ranganathan _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
