Filter
Top Products
RealPresence Collaboration Server (RMX) 1500/1800/2000/4000 Administrator’s Guide
Polycom®, Inc. 835
● SIP Dial in participants, both defined and undefined, do not inherit Precedence or Domain
characteristics from the Participant’s Address Book. (Additional fields, added to the Participant’s
Properties - Advanced and Address Book - Advanced dialog boxes are used to enter and modify
Precedence or Domain characteristics for SIP Dial-out participants.)
● For backward compatibility, calls received with a SIP Message header that contains no Precedence
Domain and the Resource Priority information, are assigned ROUTINE priority in the first defined
Precedence Domain.
● Incoming calls are accepted or rejected depending on the:
Value of the REJECT_INCORRECT_PRECEDENCE_DOMAIN_NAME System Flag.
Match or mismatch of the Precedence Domains, set in the RMX and contained in the incoming
SIP Message r-value.
The r-value is of the following format:
r-value = <domain name>
-<subdomain>.<r-priority>
Table 5-46 shows an example of calls accepted or rejected assuming:
Domain Name = UC
Sub Domain = 000000
r-priority = 2
8 FLASH-OVERRIDE 33 (0x21) 33 (0x21)
6 FLASH 35 (0x23) 35 (0x23)
4 IMMEDIATE 37 (0x25) 37 (0x25)
2 PRIORITY 39 (0x27) 39 (0x27)
0 ROUTINE 51 (0x33) 51 (0x33)
NONE No Resource Priority header for backward compatibility
Precedence Domain and Resource Priority - DSCP Default Values
Resource
Priority
Precedence Level
DSCP Value
Audio Video