On Mon, 2008-09-22 at 13:29 -0400, Joe Attardi wrote: > Scott Lawrence wrote: > > You can test this by setting up a dial plan that requires some > > permission (it doesn't matter which one), and inviting a participant > > with a number that matches that dial plan. What you'll see is an INVITE > > to sipXecs which will be challenged with a 407 Proxy Authentication > > response. > Yup, that's exactly what I saw. > > I created a rule that any number with the prefix 5 should go to, say, > [EMAIL PROTECTED] This did not work, as I saw the 407 as you said > I would. However dialing directly [EMAIL PROTECTED] from the > conference UI does manage to place the call. > > I agree with you that this needs to be handled, but as you said if we > switch back to the other way some of the other problems come back. > > However: I've spent way more time on this conference issue as is than I > had planned, and there is still a lot of other stuff left in this sprint. > > What I would like to do - but I won't do it without someone's OK - is > commit what I have for now and open a new issue to handle the proxy > authentication stuff. For now we can just have the caveat that you have > to enter a direct sip address instead of going through the local proxy > (as I said above).
I don't object to your checking things in if you want to, but the issue cannot be resolved yet. You've got the restriction wrong - the problem is that you cannot invite a PSTN number into a conference. I strongly suspect that will not be acceptable. _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
