Woof! In accepting the patch and working on XCF-3252 (http://track.sipfoundry.org/browse/XCF-3252), I'm seeing a lot of seemingly erronious information.
In summary, the desired behavior is for the WebGUI to make a SIP call, and when that call is answered the call is then REFERed into the conference bridge. I feel the "From:" tag of this call should be that of the CONFERENCE URL, so that the recipiant of the call can see it is from the conference, and that if they use their call list to call back into the conference they have the correct conference URL to do so. M. Ranganathan wrote: > You can only invite participants when logged in as the conference owner (not > superadmin) This is incorrect. As long as the credentials used for the call have permissions to make the call, then the system will let the call go thru. So I changed the code to use the credentials of the conference owner, so when logged in as superadmin the call will still be authenticated with the conference owner's credentials, NOT superadmin's. Aside: The superadmin DOES have credentials. He just doesn't have any permissions. There appears to be some confusion of this fact in the JIRA entry. M. Ranganathan continued: > and the from header has to be the conference owner because otherwise > SIpx-Proxy > will return 404 Not Found. Note that this is a new behavior that used to be > different > in the past where I COULD place the Conference extension in the From Header. > Indeed, it is this very change in behavior that caused the current issue to > be > created in the first place. Now this makes no sense to me. The From header can be anything I darn well want it to be. The only 'check' on this is that if the from domain is "this" system, it should challenge me for credentials. As long as I have credentials, this should be just fine. In fact, I changed the code to set the from header to be that of the conference. And when dialing out to gateways and such that need permission, I get challenged. As long as I respond to the challenge with valid credentials, all works well. Odditites: I don't understand the following things I'm seeing from experimentation, perhaps someone can explain it to me: 1. If the "From" address is a registered "user" on the system, and INVITE gets challenged immediately for credentials. However, if the "From" address is not a user on the system, but is in the system's domain (like the conference URL will be), the INVITE only gets challenged if the call needs permissions. I thought from all the discussions on authentication and what not that all calls with a "from" address in the domain would get challenged. This appears not to be the case. 2. Unlike INVITE, a REFER gets challenged for permissions no matter what the "From" address was. 3. When the device that got the REFER sends the new INVITE, it includes the X-sipX-Authidentity: header, yet the system still challenges it for authentication. Wasn't the purpose of X-sipX-Authidentity: to make is such that this would not occur, and instead the call would be allowed as if it came from the user described therein? --Woof! --Woof! _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
