On Mon, 2008-09-01 at 11:06 -0700, Boris Rozinov wrote: > Hello, > I'd like to understand the logic behind challenging requests sent by > SIP Phones. > May initial findings are:
> REGISTER is challenged (of course it makes sense) > initial INVITE and reINVITE are not challenged (not clear why initial > INVITE is not challenged) In the released versions, this is correct for internal calls (that is, any call that does not require that the caller have some permission). In 4.0 this is going to change so that the initial INVITE is always challenged. > SUBSCRIBE is challenged (makes perfect sense) > In-dialog REFER is challenged with exception of REFER that has > embedded Replaces in ReferTo header that is not challenged The challenge of REFER is so that the system can authenticate the transferred call with the identity of the party doing the transfer. _______________________________________________ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
