# SIP Adaptation

To inter-operate between multiple SIP providers, it often becomes necessary to make specific changes to the service itself for meeting the requirements of different providers. One provider might want a header in a particular format while another provider wants the same header in a different format. Adding patches to the service itself in MBG to support such customized requests is not feasible because it requires too many patches to be managed.

The SIP Adaptation feature in MBG 10.0 makes support for customized requests easy to implement and scalable. SIP Adaptation is done through a SIP Proxy that operates between two or more SIP endpoints. To accomplish this, a plug-in architecture was created in MBG's core service. This architecture permits plugins to act on SIP headers in MBG's SIP processing pipeline. An open-source scripting language, Lua, originally intended for embedding in a software application to provide customizable scripting support, was used for scripting the plugins. For information about scripting the plugins, see the MBG Lua API document in the Creating_Pipelines page.

The SIP Adaptation page displays any configured adaptation pipelines in the "Pipeline information" table. This table is blank until you have created pipelines. See Creating_Pipelines on how to create a pipeline. Pipelines might have a global scope and apply to all SIP traffic, or they may be tied to a particular SIP trunk. After you have created a pipeline, see Update Configuration Settings to apply the pipeline globally across all SIP trunks, and see Configure SIP Trunking to apply to specific SIP Trunks.