> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/products/integrations/intercoms/sip-integration/sip-bas-ip-device-setup.md). # SIP - BAS-IP Device Setup The Gallagher **SIP Integration** lets operators configure and use SIP devices within the **Command Centre Client** (not the Configuration Client). It currently supports SIP intercom devices and **video intercoms up to 1080p**. SIP-Intercom-to-Command-Centre calls were implemented **from v9.20 onwards**. {% hint style="warning" %} SIP does not currently support encryption or isolating SIP intercoms. {% endhint %} **Versions supported:** v8.90, v9.00, v9.10 (or later). ## Licensing The licence file must contain: ``` [Features] SIP=1 [Limits] SIP Devices=X SIP Services=X ``` where **X** is the maximum number of SIP Device or Service items configurable. The base licence covers **5 SIP Devices**; more can be purchased separately under part **`C12903`**. ## Tested hardware Gallagher only guarantees the models tested below. Verify any untested SIP model before purchasing the integration licence. | Model | Type | Video | Call forwarding | | ---------------------------------------------- | --------------------- | ----- | ------------------------------- | | Axis A8207-VE Mk II Network Video Door Station | Standard SIP intercom | Yes | Yes | | Axis C1004-E Network Cabinet Speaker | Standard SIP speaker | No | Yes | | AXIS A8105-E | Standard SIP intercom | Yes | Yes | | 2N IP FORCE | Standard SIP intercom | Yes | No | | Zenitel Vingtor-Stentofon TCIV-3+ | Standard SIP intercom | Yes | Yes | | Zenitel Vingtor-Stentofon TKIS-2 Speaker | Standard SIP speaker | No | Yes | | Aiphone IX-DV | Aiphone | Yes | Workstation-to-workstation only | | Aiphone IX-DVF-2RA | Aiphone | Yes | Workstation-to-workstation only | | Aiphone IX-SS-2G | Aiphone | No | Workstation-to-workstation only | | IDEMIA/MorphoAccess SIGMA Wide | Standard SIP intercom | Yes | No | > ⚠️ **IDEMIA/Morpho SIP limitations:** calls to IDEMIA/Morpho readers **cannot** be initiated from the Command Centre workstation (Intercom Viewer). Calls **must be initiated from the reader**, cannot be forwarded, and cannot be encrypted. ## Worked example (BAS-IP AV-08FB) Tested with **Intercom AV-08FB**, Firmware Framework **1.9.0 (20220722)**, Launcher **3.18.0**. The IPs, device serial, and workstation name in the screenshots are the vendor's setup-example values on a private (`192.168.10.x`) test network, not production data. Substitute your own site values. ### 1. Log in to the intercom Open a browser to the intercom's IP. The **factory defaults** are published by the vendor for initial setup. Change them immediately after first login: IP `192.168.1.90` or `192.168.1.91`; login `admin`; password `123456`. ![BAS-IP web interface login page in a browser, showing the OFFLINE status badge and the Sign In form with username admin](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-6d696fcda84ad24fbdeeb4428bafcd351634366b%2FSECHUB-intercom-sip-basip-01-login.png?alt=media) The Dashboard shows Device info (Framework, Launcher, Serial number, Device name) and Network info (DHCP, IP address, Subnet mask, Gateway, DNS server, MAC address). ![BAS-IP Dashboard showing Device info and Network info panels, with DHCP disabled and a static IP configured](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-694dd07a5332059a7d887f6ed7817fe9dd57c0e1%2FSECHUB-intercom-sip-basip-02-dashboard-device-network-info.png?alt=media) ### 2. Set the apartment identity Under **Panel > Apartment Settings**, set Building, Unit, Floor, Apartment, and Device number. These values build the Device URI later. ![BAS-IP Panel Apartment Settings page with Building, Unit, Floor, Apartment and Device number all set to 1](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-b32aabd21f141846d4c961e08f1be5b183fb75da%2FSECHUB-intercom-sip-basip-03-apartment-settings.png?alt=media) ### 3. Disable the on-device SIP server Under **Panel > SIP settings**, set to **Disabled**. This is for a SIP *Server*. The Command Centre SIP Service is not a SIP server; it is a SIP **endpoint using peer-to-peer communication**. The intercom shows **"OFFLINE"** once SIP settings are disabled, which is expected. ![BAS-IP Panel SIP settings page with the Enable/Disable box unchecked and the OFFLINE badge highlighted](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-a19da3a386527503a4aa802599809dc377fdeb63%2FSECHUB-intercom-sip-basip-04-sip-settings-disabled.png?alt=media) ### 4. Set the call number Under **Call Settings**, set **Number** to `sip:000@[Command Centre Server IP or the machine running the SIP Service]`. Example: `sip:000@192.168.10.11`. For large sites with many intercoms, install the SIP Service on a separate 'middleware' machine on the same network (see the release note). ![BAS-IP Call settings page showing the Concierge number sip:000@192.168.10.11 and call/talk time limits](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-350d29a52de18c86f90bcecba956439878ae9387%2FSECHUB-intercom-sip-basip-05-call-settings.png?alt=media) ### 5. Device settings Under **Device Settings**, set video quality (up to 1920x1080), RTP data profile, and RTSP credentials. ![BAS-IP Device settings page showing video quality 1920x1080, RTP data profile, volume level and RTSP username](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-fefbe1b86aa363af27d899e545414cd24f37a8aa%2FSECHUB-intercom-sip-basip-06-device-settings.png?alt=media) Optionally set **Forward** (not tested): an Apartment number, for example `1010101`, from Panel Settings > Apartment Settings. ![BAS-IP Forward settings page with Mode set to One by one and a forward queue entry to sip:000@192.168.10.11:5060](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-f866b0cde6b00c7a356704f52a58689ee5f4a0d1%2FSECHUB-intercom-sip-basip-07-forward-settings.png?alt=media) ### 6. Install the Command Centre SIP Service Install the Command Centre SIP interface per the SIP integration release note, available from the Command Centre software media at: `vEL8.90.xxxx\Utilities\SIP Service 8.90.23\Release Note SIP Integration v8.90.pdf`. ### 7. Configure the SIP Device in Command Centre Create a **SIP Device** item. On the **General** tab, name it and assign a Division. ![Command Centre SIP Device Properties dialog, General tab, showing Item Type SIP Device and a Root Division assignment](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-928feff2a61909f41ca8fb165f8b917f0816ecb5%2FSECHUB-intercom-sip-basip-08-cc-sip-device-general.png?alt=media) On the **Setup** tab, set **Device Type** = Standard SIP Device, assign a **Door** if the intercom is at a door, and set the **Device URI**. The URI is built from the Building/Unit/Floor/Apartment/Device Number entered on the intercom. **Device URI construction, Example 1** (`sip:10001010101@192.168.10.60:5060`): Device Number = `1` (plus `00`); Building = `01`; Unit = `01`; Floor = `01`; Apartment = `01`. ![Command Centre SIP Device Setup tab with Device URI sip:10001010101@192.168.10.60:5060 for device number 1](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-d0b11962260608c138cdebd358333872a4bc5d6c%2FSECHUB-intercom-sip-basip-09-cc-sip-device-uri-example1.png?alt=media) **Device URI construction, Example 2** (`sip:20001010101@192.168.10.60:5060`): Device Number = `2` (plus `00`); Building/Unit/Floor/Apartment = `01` each (same site). The intercom's Device number is set to `2` in Apartment Settings to match. ![Command Centre SIP Device Setup tab with Device URI sip:20001010101@192.168.10.60:5060 for device number 2](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-b119f802775a301e72565888765634b354130222%2FSECHUB-intercom-sip-basip-10-cc-sip-device-uri-example2.png?alt=media) ![BAS-IP Apartment Settings page with Device number set to 2, matching Device URI Example 2](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-af6706dab9db5441f1e92f45c682fccf6ba8d189%2FSECHUB-intercom-sip-basip-11-apartment-settings-device-2.png?alt=media) ### 8. Enable SIP on the workstation On the FT Workstation item, **SIP Intercom** tab, tick **Enable SIP Functionality**, set the **Workstation IP Address** and **Workstation Listen Port**, and tick **Accept video from intercoms**. The status bar reads **Normal. Registered** when connected. ![Command Centre FT Workstation Properties, SIP Intercom tab, with Enable SIP Functionality ticked, a workstation IP and listen port 5000, and Accept video from intercoms enabled](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-5cb3b14f3327f6e5c84f3350ffd271f040a54737%2FSECHUB-intercom-sip-basip-12-cc-workstation-sip-intercom.png?alt=media) *** 🔗 **Related** * [Session Initiation Protocol (SIP)](/knowledge-hub/products/cc-software/configure/interface-options/session-initiation-protocol-sip.md). The SIP protocol interface. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://help.security.gallagher.com/knowledge-hub/products/integrations/intercoms/sip-integration/sip-bas-ip-device-setup.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.