[BLISS] Use of the PUBLISH transaction for the SUS/RES procedures

Hi, 

the use of the PUBLISH transaction to control the suspension and resume of a Call Completion queue position was previously discussed at the mail list. The outcome was, that it is not appropriate to change the state of the queue by targeting the information to the monitor's AOR.

At the last IETF meeting a different approach was discussed off-line. The caller sends it's own status information in PUBLISH with his own AOR in To: and From: headers. The Request-URI of this PUBLISH request contains the monitor AOR as received in the Call-Info header of the 486 response. 

In this case there is no change in the CC monitor (the queue) state done by the PUBLISH request directly, but either an indirect change of the state based on the information about the caller status. The CC monitor acts as a kind of a state composer, composing the state of the queue from the states of the different callers.

This architecture can even be extended to support the presence service directly. The caller (or the CC agent on behalf of the caller) can send the URI of his presence server to the monitor in a parameter of the initial CC SUBSCRIBE request. The monitor would then subscribe to this URI and receive the presence status of the caller from his presence server. The caller UA (CC agent) would than have to send his presence information only to his regular presence server.

The interworking of the SUS/RES procedures from the PSTN/TCAP are also quite simple when the PUBLISH method is used. Appropriate TCAP SUSPEND indication would be mapped to the "closed" presence PIDF state and RESUME to the "open" PIDF state transported in the PUBLISH method.

Comments are welcome. 

BR, Martin

_______________________________________________
BLISS mailing list
BLISS@ietf.org
https://www.ietf.org/mailman/listinfo/bliss