Page History

...

With basic call routing, Transformation Tables are tied to Call Routes. As a call route is executed, the associated Transformation Table is used to match, and possibly, manipulate the data within the IEs. For example, a Call Route to Lync Skype can be associated with a Transformation Table that checks the called number IE against Active Directory's msRTCSIP-Line attribute. If a match is found, the call is routed to LyncSkype. If the Transformation Table fails, all the IEs are restored to their original values before the next Call Route Entry is executed.

...

1. Call arrives at ingress port.
2. Ingress Signaling Group sends the call to the configured Action Set. Note that the Call Routing Table configuration is ignored when an Action Set Table is defined.
3. The first entry in the Action Set Table executes.
4. The associated Transformation Table is processed.
5. If the Transformation Table fails, the call is disconnected per the Action on Failure configuration. If the transformation succeeds, the call is sent to the Lync Routes Skype Routes Call Route Table.
6. The Lync Routes Skype Routes Call Route Table executes.
7. The associated translation table is processed.
8. The call is sent to the egress Signaling Group.
9. The call is sent to the destination SIP Server.

...

• Normalize Numbers
• Block Listed Numbers
• Find a Calling Name
• Send calls to Exchange for voicemail retrieval
• Calls to Fax Numbers
• Permit voicemail for analog Lync devicesSkype devices
• Send calls to Lync UsersSkype Users
• Use the PBX as the route of last resort

...