<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Hi Roger,<br>
I think that was Juha's point: we don't. <br>
302 was created to enable a user agent to communicate back to the other
user agent that it can be reached somewhere else. Thus, your server
should relay the 302 and the receiving user agent should then decide
what to do. Some UAs immediate initiate a new call, while others
(e.g.software agents) may pop up a question to the user: "Callee is not
available, but can be reached at location" (which of course may well be
an international PSTN call that can be expensive).<br>
Some UAs also have options that can be set: How to handle redirects<br>
<br>
Server-centric forwarding can be better handled by user preferences and
loading av pairs.<br>
<br>
That being said, I remember a thread a while ago with a discussion on
how to turn a 302 into a forwarding. I don't remember the outcome, but
it is probably possible, although not according to the RFCs. You do
have some problems though, e.g. if the UA sends back an email uri etc.<br>
<br>
And of course, as people tend to follow RFCs, you will probably get one
angry customer if he realizes that his 302 generates a cost. If you
have control over the UA and have decided to use 302 instead of the
more standardized call forward scenario, you really are making
problems for yourself.<br>
g-)<br>
<br>
Roger Lewau wrote:
<blockquote
cite="midWorldClient-F200609110951.AA51010752@serverhallen.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html; ">
<style title="table borders">.htmtableborders, .htmtableborders td,
.htmtableborders th {border : 1px dashed lightgrey ! important;} </style>
<style type="text/css">html, body { border: 0px; } span.macro, span.macro ul,
span.macro div, span.macro p {background : #CCCCCC;} </style>
<style type="text/css"> p{margin-bottom: 0.15em;margin-top:
0.15em;}body{font-family:tahoma;font-size:10pt;}; </style>
<font style="font-size: 10pt; font-family: tahoma;">
<div>Hello Juha and Andrey</div>
<div> </div>
<div>302 "Moved temporarily" is definately about
forwarding/redirecting calls. This is how the vast majority of all IP
phones and ATAs handle call forwarding. It might not be the intended
use of 302 according to RFCs, even if I see nothing that says
otherwise, but this is how it is used in end devices today. This brings
us back to my original question. How do you guys handle 302 redirection
so that costs are charged to the callee.</div>
<div> </div>
<div>Kind regards</div>
<div>Roger </div>
</font><br>
<blockquote
style="border-left: 2px solid rgb(0, 0, 0); padding-right: 0px; padding-left: 5px; margin-left: 5px; margin-right: 0px;">-----Original
Message-----<br>
From: "Andrey Kouprianov" <a class="moz-txt-link-rfc2396E" href="mailto:andrey.kouprianov@gmail.com"><andrey.kouprianov@gmail.com></a><br>
To: <a class="moz-txt-link-abbreviated" href="mailto:serusers@iptel.org">serusers@iptel.org</a><br>
Date: Mon, 11 Sep 2006 12:51:09 +0700<br>
Subject: Re: [Serusers] Handling 302 responses<br>
<br>
<div style="font-family: monospace,courier new,courier;">You can
also use 302 responses to gather some information about the<br>
remote party. Contacts returned in the response are not necessarily<br>
the SIP URI's. I've tried using mail addresses, SIP tel: URI's and<br>
HTTP URLs too.<br>
<br>
So, if the remote party is Busy at the moment, but has other ways to<br>
let u contact them, 302 is one of the answers to this.<br>
<br>
On 9/11/06, Juha Heinanen <a class="moz-txt-link-rfc2396E" href="mailto:jh@tutpro.com"><jh@tutpro.com></a> wrote:<br>
> Roger Lewau writes:<br>
><br>
> > In my mind that statement is completely off the wall, it is
not the<br>
> > requesting client that should be responsible for
establishing the forwarded<br>
> > call, it never is in the rest of the telecom industry so why
should it be<br>
> > the case for SIP?<br>
><br>
> 302 is not about "forwarded call". it just tells the caller that
the<br>
> callee is at some other uri, which the caller may or may not wish
to<br>
> contact. in many pstn networks, you can hear an announcement that
the<br>
> number you tried is not in use and you should try another number<br>
> instead.<br>
><br>
> if callee wants to "forward" calls, he has other means for that
purpose,<br>
> for example, his phone can forward the invite to some other uri or
he<br>
> may configure his proxy to do so.<br>
><br>
> -- juha<br>
> _______________________________________________<br>
> Serusers mailing list<br>
> <a class="moz-txt-link-abbreviated" href="mailto:Serusers@lists.iptel.org">Serusers@lists.iptel.org</a><br>
> <a href="http://lists.iptel.org/mailman/listinfo/serusers"
target="_blank">
http://lists.iptel.org/mailman/listinfo/serusers</a><br>
><br>
_______________________________________________<br>
Serusers mailing list<br>
<a class="moz-txt-link-abbreviated" href="mailto:Serusers@lists.iptel.org">Serusers@lists.iptel.org</a><br>
<a href="http://lists.iptel.org/mailman/listinfo/serusers"
target="_blank">http://lists.iptel.org/mailman/listinfo/serusers</a><br>
</div>
</blockquote>
<pre wrap="">
<hr size="4" width="90%">
_______________________________________________
Serusers mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Serusers@lists.iptel.org">Serusers@lists.iptel.org</a>
<a class="moz-txt-link-freetext" href="http://lists.iptel.org/mailman/listinfo/serusers">http://lists.iptel.org/mailman/listinfo/serusers</a>
</pre>
</blockquote>
</body>
</html>