There is no explicit support for callerprefs. I think though that most of the scenarios they are goof for could be achieved using textops and selects+AVP processing.
-jiri
At 15:40 18/10/2007, Stefan.Brozinski@materna.de wrote:
-- Jiri Kuthan http://iptel.org/~jiri/
3841 is a draft of a possible standard. While it might be supported at some point (and you're welcome to write it... remember, SER's an open-source product), I think it's a better idea to focus on the core SIP stuff first, and then worry about the 60-70+ draft additions that 'everyone just has to have.' Who knows? By then, it might even be standardised. :)
N.
Stefan.Brozinski@materna.de wrote:
3841 is a draft of a possible standard.
This is an interesting statement. Where did you find this information?
I looked at http://www.ietf.org/rfc/rfc3841.txt (no surprise) and can't find anything about a "draft" status.
Regards Stefan
I'm sorry.... not even draft status yet. It's still only proposed.
http://www.rfc-editor.org/rfcxx00.html#Proposed
Latest issuance of the Official Internet Protocol Standards.
N.
Stefan.Brozinski@materna.de wrote:
SIP wrote:
I'm sorry.... not even draft status yet. It's still only proposed.
Ok, so we have to stop working on RFC 3261 as well? It is listed in the same category...
Seriously: There are different classes of RFCs. Only few are stable enough to get the highest merits of being an Internet Standard (those that have a STDxxx number). If you look at that list, even HTTP is only Draft Standard (be careful not to interfere this with an Internet-Draft---those documents beginning with draft-* can change very often and do not have any official status).
Regards, Olaf
-
Jiri Kuthan -
Olaf Bergmann -
SIP -
Stefan.Brozinski＠materna.de