AASTRA SIP-DECT (Release 3.0)- OM System Manual - Installation, Administration and Maintenance EN - Manual (Page 223)

SIP–DECT OM System Manual Release 3.0 11 Appendix
Aastra depl-1624/1.0 Page: 223 (241)
/16/ RFC 3264, An Offer/Answer Model with Session Description Protocol (SDP),
June 2002
/17/ RFC 3420, Internet Media Type message/sipfrag, November 2002
/18/ RFC 3515, The Session Initiation Protocol (SIP) Refer method, April 2003
/19/ RFC 3665, The Session Initiation Protocol (SIP) Basic Call Flow Examples,
December 2003
/20/ RFC 3842, A Message Summary and Message Waiting Indication Event Package for
the Session Initiation Protocol (SIP), August 2004
/21/ RFC 3891, The Session Initiation Protocol (SIP) “Replaces” Header, September 2004
/22/ RFC 3892, The Session Initiation Protocol (SIP) Referred-By Mechanism, September
2004
/23/ RFC 4566, SDP: Session Description Protocol
/24/ Compendium “OpenMobility SIP–DECT 3.0 Solution; Installation & Administration”
/25/ SIP–DECT; OM Locating Application; Installation, Administration & User Guide
/26/ SIP–DECT; OM Integrated Messaging & Alerting Application; Installation,
Administration & User Guide
/27/ SIP–DECT; OM Handset Sharing & Provisioning; User Guide
/28/ SIP–DECT; Aastra 610d, 620d, 630d; Messaging & Alerting Applications; User Guide
Issue 4
/29/ Aastra 610d, 620d, 630d SIP–DECT User’s Guide Issue 4
/30/ aad-0384 OM Application XML Interface specification (OM AXI)
/31/ RFC 2782, A DNS RR for specifying the location of services (DNS SRV)
/32/ RFC 3262, Reliability of Provisional Responses in the Session Initiation Protocol
(SIP)
/33/ RFC 3311, The Session Initiation Protocol (SIP) UPDATE Method
/34/ SIP–DECT XML terminal interface specification
11.7 Pre-Configuration File Rules
The following file format description can be used to administrate the RFP and PP
configuration with external applications, e.g. an external configuration management tool or a
PBX communications system.
The framework of the text file follows strictly defined rules. The main framework is divided in
two parts:
1 An instruction section is used to drive a generic data creation for those fields not filled
within data sequence section.
2 A data sequence section defines data record fields. Each of them are explicitly set.
Layout rules in detail are:
•
Comments start with “#”.
•
Each record is terminated by the regular expressions “\r” or “\n”.