SIP Request-URIs for Service Control

B. Campbell and R. Sparks, “Control of Service Context using SIP Request-URI”, IETF RFC 3087 - proposes a mechanism to communicate context information^† to an application (via the use of a distinctive Request-URI).

Using different URIs to provide both state information and the information about what lead to this state transition (for example, you were forwarded to the voicemail system because the user did not answer vs. being forwarded to the voicemail system because the user is busy with another call).

^† Call state information, such as the calling party, called party, reason for forward, etc.

Slide Notes

B. Campbell and R. Sparks, “Control of Service Context using SIP Request-URI”, IETF RFC 3087, April 2001 http://www.ietf.org/rfc/rfc3087.txt Links to an external site.

Transcript

[slide337] There's been lots of efforts to be able to have a control-of-service URI, so now we can actually send information saying, well, the reason you were forwarded to the voicemail is because the person that you called didn't answer their phone. That might be different than the reason you were forwarded to voicemail is because they were busy on the phone. Right? That means that the voicemail service could play different messages in response to them, depending upon what the conditions were.