A student's open lab: learning and sharing, free for everyone.

SIP UniverseFree University

Home / Oracle, Ribbon, and AudioCodes / Header rules run in order

Header rules run in order

Oracle HMR header rules run in configured order. The 10.1 fundamentals page names add, delete, manipulate, store, and reject.

Learn in 5 minutes

  1. Put header rules in configured order
  2. Name the documented actions
  3. Leave the reject status code in the release guide

Visual

Server removed on the way out · study drawing · cyphermonkeylabs.com PhoneSBCCarrier INVITE 100 INVITE 180

SVG HTML PNG

A later rule sees the message earlier rules produced.

Worked example

Delete Server Run this Acme header-rule subset against the INVITE. Server should disappear.

  1. Read header-name and action.
  2. Run the rule.
  3. Confirm Server is gone.

Vendor menus, ports, and license names change. Confirm before relying on a sentence that is not an RFC.

Fault

A later rule that stores Server records an empty result. The delete rule is configured first.

Header rules run in configured order.

Quiz

Header rules on the Oracle SBC run


add, delete, manipulate, and store are


The SIP status produced by reject


action delete on header-name Server


msg-type any means the teaching rule is considered for


A store of Server must be placed


Ecosystem

Glossary, sister systems, and the integration seam for this room.

Quality management and recording QM scores interactions. The standardized way an SBC forks a session to a recorder is SIPREC.

Glossary · Ecosystem map · Ports · Troubleshooting

Sources and go deeper