IP PBX

Introduction: Adding a SIP emergency intercom to an existing IP phone system comes down to four connection points: network reachability, SIP registration, PoE power, and dry contact wiring.

When a customer asks you to mount a one-button emergency call box in a corridor, a stairwell, or a parking level, the first question is not what the device looks like. It is whether the site can support it. Before you quote labor or promise a completion date, check the network path to the intercom, the SIP account it will register against, the power source at the mounting point, and the external devices you plan to trigger through its dry contact input and output. Working through these four threads in order lets you turn a vague request into a clear statement of what needs to be configured, what needs to be tested, and what the customer must provide before the hardware goes on the wall.

What Network Setup a SIP Emergency Intercom Needs Before Installation

A SIP emergency intercom is an Ethernet endpoint first and a voice device second. It has a 10/100 Mbps Ethernet port and registers as a SIP client, so the whole deployment starts with the LAN drop at the mounting point. Walk the site with these four network checks:

• IP reachability between the call box and the IPPBX.  The intercom and the PBX can sit on the same subnet or on different subnets, as long as routing and firewall rules allow SIP and RTP traffic in both directions. If the PBX is hosted off-site, confirm that the call box can resolve the registrar address and reach it through any security policies.

• VLAN and QoS policy.  If the customer separates voice and data traffic, place the intercom on the voice VLAN and tag the switch port accordingly. The EQ-i11S supports VLAN and QoS configuration, so you can mark the device's SIP and RTP traffic for priority. On an emergency help point, a call that competes with file transfers for bandwidth is not acceptable.

• DHCP reservation or static IP.  A wall-mounted call box should not receive a new address after a switch or router reboot. Reserve its DHCP lease, or assign a static IP and record it in the provisioning file. The EQ-i11S supports static IP, DHCP, and PPPoE, so the choice depends on the customer's network management style.

• Auto-Provisioning and TR-069 reachability.  For projects with more than a few help points, confirm that the provisioning server and the TR-069 management platform are reachable from the device's network. Auto-Provisioning and TR-069 let you push configuration changes, update firmware, and check registration status remotely, which saves a site visit when the customer later asks for a speed-dial change.

Network preparation is the cheapest issue to fix during the design phase and the most expensive to fix after the boxes are mounted and cables are dressed.

How to Register the Intercom as a SIP Endpoint on the IPPBX

Once the network path is confirmed, treat the intercom as a standard SIP endpoint. RFC 3261 defines the flow: the device sends a REGISTER request to the registrar, receives a response, and later establishes calls through the SIP proxy. In practice, the call box appears in the PBX's extension list just like an IP phone, and troubleshooting follows the same routine you already use for desk phones. Start by creating an extension on the IPPBX for each SIP line. The EQ-i11S supports two SIP lines, so decide whether the point needs one active account or a second one for a backup number, such as a security desk and a mobile response team. Then enter the SIP server address, registrar, credentials, and transport protocol in the intercom's web interface. SIP 2. 0 over UDP suits most local deployments; TCP adds reliability over lossy networks; TLS is the right choice when the customer requires encrypted signaling. Any standards-based server can handle this, including an Equiinet IP Phone System, because the unit registers as a generic SIP client rather than a proprietary endpoint. Next, set the one-button behavior. The EQ-i11S is built around a single call button, and its speed-dial function is the setting that makes the unit useful in an emergency: pressing the button can place a call to a predefined extension, a hunt group, or an attendant. If the customer wants several people to be notified at once, point the speed-dial target at the PBX's group or queue instead of one person's number. After configuring the account, test registration from the intercom's web interface, make a call, and verify that the PBX shows the correct calling and called numbers. Also test the audio path in both directions from the actual mounting location, because a help point that registers but cannot produce clear two-way audio will fail when it matters. If firewall ports had to be opened, confirm that media flows after the call is answered, not just that the phone rings.

How PoE Power and Dry Contact Wiring Affect the Final Installation

The power decision is usually the easiest way to simplify an installation. The EQ-i11S supports Power over Ethernet, so a single Cat5e or Cat6 cable carries both network data and DC power to the wall-mounted unit. That removes the need for a separate power adapter at the help point, which is a real advantage in corridors, parking areas, stairwells, and outdoor locations where mains wiring is inconvenient. The EQ-i11S supports PoE; the exact 802. 3 power class is not published, so verify that the switch port delivers enough power budget for the intercom, especially on older PoE switches. Dry contact I/O is what connects the intercom to the rest of the customer's safety infrastructure. The EQ-i11S provides one dry contact input and one dry contact output. The output reacts to an intercom action, such as starting an emergency call: it can trigger a strobe beacon, chime, door release, or an input on a third-party alarm panel. The input works in reverse, letting an external device such as a panic button, a motion sensor, or a relay from another system close the contact and cause the intercom to start a call or send an event. This is where an SOS intercom becomes more than a telephone: it turns a wall-mounted help point into a trigger for the surrounding security equipment. Wiring the contacts is simple, but the load question has to be answered before installation. If the existing switch cannot provide PoE, a PoE injector on the switch side solves the problem without running a separate power line to the unit. For the dry contacts, confirm the electrical ratings with the supplier before connecting anything that draws significant current; for a beacon or siren, install an external relay between the intercom and the load. That keeps the call box contacts isolated and makes future maintenance easier, because the intercom can be replaced without rewiring the high-power side. This is where the four connection threads come together. The network path decides whether the call box can reach the PBX. The SIP account decides whether it registers and rings. PoE decides whether it powers up from one cable. The dry contact wiring decides whether it talks to the surrounding safety devices. When a customer asks about adding a SIP emergency intercom, checking these four areas in order will tell you whether the project is straightforward or needs additional infrastructure.

Conclusion

For an integrator, adding a SIP the product to an IP phone system is a network project as much as a hardware installation. Verify the LAN drop, the VLAN and QoS policy, the DHCP reservation, the SIP account, the PoE budget, and the dry contact wiring before you promise a timeline. The EQ-i11S shows what a practical SIP SOS call box should offer on paper: two SIP lines, SIP 2. 0 over UDP/TCP/TLS, 10/100 Mbps Ethernet, PoE, one dry contact input and one dry contact output, and Auto-Provisioning with TR-069 for remote management. Site conditions still decide the final effort, but these four checks give you a reliable way to scope it. If you are evaluating the EQ-i11S for a customer project, send the PBX model, the number of help points, and your PoE switch details to the Equiinet team, and confirm the SIP transport, power class, and dry contact ratings before you quote the job.

FAQ

 Q：What do I need to prepare before connecting a SIP the product to an IPPBX?

A：Before connecting, verify four things: the LAN drop at the mounting point can reach the IPPBX over the network, the voice VLAN and QoS policy are configured, the DHCP reservation or static IP is ready, and the SIP account has been created as an extension on the PBX. If the same cable will carry power, confirm that the PoE switch port has enough power budget.

 Q：Does a wall-mounted the product need a PoE switch or a separate power supply?

A：With the EQ-i11S, a PoE switch port that delivers power over the same Ethernet cable is the cleanest way to power a wall-mounted the product. This avoids installing a separate power adapter at the help point, which matters in corridors, parking areas, and outdoor locations where mains wiring is inconvenient. The EQ-i11S supports PoE; the exact 802. 3 class is not listed, so check the switch model and port power budget during planning.

 Q：How are dry contact inputs and outputs used with a SIP intercom?

A：The dry contact output is a switch that closes when the intercom performs an action, such as starting an emergency call. It is commonly used to trigger a strobe light, a chime, a door release, or an input on a separate alarm panel.

Sources / References

RFC 3261 - SIP: Session Initiation Protocol

What Is Power over Ethernet (PoE)?

Technical Library (TR-069)

Related Examples

EQ-i11S One-button Intercom (no camera)