You can also use 302 responses to gather some information about the
remote party. Contacts returned in the response are not necessarily
the
SIP URI's. I've tried using mail addresses, SIP tel: URI's and
HTTP URLs
too.
So, if the remote party is Busy at the moment, but has other
ways to
let u contact them, 302 is one of the answers to this.
On
9/11/06, Juha Heinanen <jh@tutpro.com> wrote:
> Roger Lewau
writes:
>
> > In my mind that statement is completely
off the wall, it is not the
> > requesting client that should
be responsible for establishing the forwarded
> > call, it
never is in the rest of the telecom industry so why should it be
>
> the case for SIP?
>
> 302 is not about "forwarded
call". it just tells the caller that the
> callee is at some
other uri, which the caller may or may not wish to
> contact. in
many pstn networks, you can hear an announcement that the
> number you
tried is not in use and you should try another number
> instead.
>
> if callee wants to "forward" calls, he has other means for that
purpose,
> for example, his phone can forward the invite to some other
uri or he
> may configure his proxy to do so.
>
> --
juha
> _______________________________________________
>
Serusers mailing list
> Serusers@lists.iptel.org
>
http://lists.iptel.org/mailman/listinfo/serusers>
_______________________________________________
Serusers mailing list
Serusers@lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers