Tuesday, 12 June 2012

NET UX Optional Transformation Rules

There are two (2) types of "transformation rules" in a NET UX gateway.
  1. Mandatory 
  2. Optional
Mandatory rules are just that "mandatory' ALL rules MUST match within the transformation rule, optional rules are optional, in that the "Input Field Type" MUST match.

The following show 4 optional "Calling Address/Number" Input field type entries, for this rule to be successful, one of the circled rules must be completed without error.
In the case of multiple matches, the last matched rule will be the one used.  This is where the sequence of the rules plays an important part.  Rules can be re-sequenced using the "Resequence" function.

The following link to the UX documentation, as some examples (the above screen shots came from the documentation).

No comments:

Post a Comment

MoH - Skype, AudioCodes and an SIP Carrier

Troubleshooting an MoH issue today, where a SfB client would places a PSTN caller on hold, and the PSTN caller would get no MoH.   SBC con...