>  
> 
> Huijun Yang wrote:
>> It would fail because from Joe's previous trace in the case of 
>> conference to external extension, the code did not seem to handle 407

>> challenge, and call failed. In this case, inviting a local user for 
>> some reason did not get challenged. It might be a bug in sipXproxy, 
>> and that is why I am asking for sipxproxy.log to verify. If it is 
>> indeed a bug in sipXproxy, once that bug is fixed, it will challenge 
>> the request in the case of inviting a local user. If the code to 
>> handle the challenge is not there, it will fail as well, same as the 
>> case of inviting external extension.
> 
> 
>> I reproduced the successful conference invite and am attaching
> sipXproxy.log here.
> 
> Was not able to get the cause from the log. You may want to fire an 
> issue for this.
> 
> Huijun


Damian, thanks for your detailed explaination.

> Check the difference between conference-invite-working.xml and
conference-invite.xml that Joe posted.

> To recapture the problem: sipXconfig is inviting users to a
conference. The initial invite is not going to get > challenged unless
reaching the invitee requires a permission (that's why inviting local
user or inviting through SIP URL > works and inviting a number that has
a dial rule with permission does not).

But I am not sure about this. Now sipXproxy will challenge every call
request that initiated from local users regardless of the permission of
invitee.


> And, if I understand this correctly, recent changes to authentication
do not apply here at all: FROM address identity > is not that of the
user, it's conference server and conference server does not have
credentials.

That is probably the reason, I did not know conference server does not
have credentials, so it was not considered as a "local user". But if
that is the case, it does not explain why the same conference server in
the case of calling external extension was challenged? 


Thanks,
Huijun


_______________________________________________
sipx-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev

Reply via email to