Hi Christian, IMHO, the way you describe first -using HTTP- should be the way to go rather than following the scheme in your examples -using SIP-. It looks to me that more and more SIP -with its extensions- is invading some HTTP functionality space -and at certain areas there is no real black and white boundaries-. But IMHO, this case is a data exchange between two IP domain entities rather being directly related with creating a "session" between them.
For HTTP way of doing things -for example for service provisioning-, is there really a need for standardization (not a rhetorical but a real question)? Is it too different than the case that I manage my bank account online? Tolga > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of Christian > Stredicke > Sent: Friday, March 12, 2004 1:44 AM > To: [EMAIL PROTECTED] > Cc: [EMAIL PROTECTED] > Subject: RE: [Sip-implementors] Controlling Redirection > > > Hi Wayne, > > the question remains how a phone would communicate to the proxy/registrar. > Of course it�s possible to set this up on the proxy/registrar > with HTTP and > a web client, but is there a standardized way to do this? > > For example: > > Phone -> Proxy/Registrar > ------------------------------------------------ > PUBLISH sip:[EMAIL PROTECTED] SIP/2.0 > From: <sip:[EMAIL PROTECTED]>;tag=123 > To: <sip:[EMAIL PROTECTED]> > Call-ID: fhs4tcm0q3xt > CSeq: 1 PUBLISH > Content-Length: 564 > Content-Type: application/redirection-setup > Event: registration-setup > > Redirection-Event: not-registered > Redirection-Target: <sip:[EMAIL PROTECTED]> > Redirection-Timeout: 0 > ------------------------------------------------ > > or: > > Proxy/Registrar to Phone (notifies about http possibility): > ------------------------------------------------ > SIP/2.0 200 You are registered > From: <sip:[EMAIL PROTECTED]>;tag=123 > To: <sip:[EMAIL PROTECTED]>;tag=bhgz7 > Call-ID: fhs4tcm0q3xt > CSeq: 1 REGISTER > Content-Length: 564 > Content-Type: text/xml > > <?xml version="1.0"?> > <web-access> > <event name="redirect" type="not-registered"> > <URL method="POST">https://proxy.com:5068/set_redirection.php</URL> > <field name="origin">$from_url</field> > <field name="red_event">$redirection_event</field> > <field name="red_number">$redirection_number</field> > <event> > </web-access> > ------------------------------------------------ > > Maybe the IM community knows more? > > Christian > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > [EMAIL PROTECTED] > Sent: Thursday, March 11, 2004 8:22 PM > To: Christian Stredicke > Cc: [EMAIL PROTECTED]; > [EMAIL PROTECTED] > Subject: Re: [Sip-implementors] Controlling Redirection > > > Christian, > � � � � You were correct in the assumption in brackets against > the 'Redirect > when not logged in' in my experience, if a proxy which is the > registrar for > a UA has no registration for this user it will call process this > immediately > as for a no answer event. Then treatment depends on the service and > provisioning of this user - Recorded Voice Announcement 'User unavailable' > or Call Forward to Voice Mail, or Call Forward to another number etc.. > > � � � � If the UA was registered but not available 'turned off' then the > Proxy Registrar would Invite the UA but this would subsequently fail and > invoke the same no answer treatment as outlined above. > � � � � > � � � � Redirection of FAX messages - now there is a concept. In talking > about a general UA - I am thinking a phone user ? - same process as above > with the UA being currently registered etc. If the UA is registered and > available the Invite would be recieved by the UA but the SDP would be > incompatable eg. the phone end point is not capable of receiving a FAX > message and would return a 415 'Unsupported Media Type' or similar > termination code. I have not tried this scenario out and ao can't say with > 100% what you would get. I am not aware of an intelligence in the proxy or > UA that could redirect the incoming call to a FAX.... although > that would be > nifty. > > Regards, > > Wayne Davies > System Support Engineer - Broadsoft > > Office: +61 3 96260468 > Mobile: 0417282909 > email: � [EMAIL PROTECTED] > > > "Christian Stredicke" <[EMAIL PROTECTED]> > Sent by: [EMAIL PROTECTED] > 11/03/2004 10:49 PM > � � � � > � � � � To: � � � �<[EMAIL PROTECTED]> > � � � � cc: � � � � > � � � � Subject: � � � �[Sip-implementors] Controlling Redirection > > > > Sorry if that's a stupid question. > � > On my cell phone I can set the redirection for the following cases: > � > - Redirect always > - Redirect when not logged in (in SIP that would correspondent to not > registered) > - Redirect when not answering after x seconds > - Redirect Fax messages (?) > - Other cases? > � > 3xx is no solution (if the UA is switched off it can't answer). I > guess the > proxy or registrar would have to handle this. How would a SIP user agent > tell the proxy or registrar this? Do we already have an RFC or is there > something going on in a working group? > � > Christian > -- > Christian Stredicke > tel:+49.30.39833.401 (ENUM & PSTN) > ----------------------------------------------------------------- > Questions? Check out frequently asked questions (FAQ): > http://snom.com/faq_en.php > ----------------------------------------------------------------- > �_______________________________________________ > Sip-implementors mailing list > [EMAIL PROTECTED] > http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors > > > > > ****************************************************************** > ********** > ** > - NOTICE FROM DIMENSION DATA AUSTRALIA > This message is confidential, and may contain proprietary or legally > privileged information. If you have received this email in error, please > notify the sender and delete it immediately. > > Internet communications are not secure. You should scan this > message and any > attachments for viruses. Under no circumstances do we accept liability for > any loss or damage which may result from your receipt of this > message or any > attachments. > ****************************************************************** > ********** > ** > > > _______________________________________________ > Sip-implementors mailing list > [EMAIL PROTECTED] > http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors _______________________________________________ Sip-implementors mailing list [EMAIL PROTECTED] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
