- Sending and receiving calls to other RTI devices that support VoIP.
- Sending and receiving calls to 3rd party devices that support peer-to-peer SIP
- Video intercom with devices that support H.264 video codec
- Custom incoming call ring sound.
- Flip to a page on incoming call.
- Auto Answer.
- Auto Answer Ring Once.
- Do Not Disturb.
- Optional Push To Talk.
- Speaker and Mic AGC (Automatic Gain Control) to amplify audio.
- System variables for : call in progress, incoming call, call duration and others.
- Integration Designer version 9.9 or higher
RTI devices with VoIP intercom support:
- KX10, KX7, KX3, CX10, CX7, T3x
- Door stations/intercom panels that support the SIP protocol.
- Audio is supported via either the G.711-ALaw or G.711-Ulaw codecs.
- Video is supported via the H.264 video codec.
- Devices must be connected to an Ethernet network.
- No other equipment (servers/processors) are required - Devices dial each other directly.
What is SIP?
- SIP stands for Session Initiation Protocol. It’s similar to HTTP and is the protocol used to setup calls between devices.
- More info: https://en.wikipedia.org/wiki/Session_Initiation_Protocol
What is SIP peer-to-peer?
- Peer-to-peer SIP is done without the SIP server.
- The devices need to know the IP address or Host Name of the device they wish to call.
- No additional hardware is required.
What video codecs are supported?
- H.264. Currently only the baseline profile of the codec is supported.
Why is video lagging?
- If video performance is poor its because the H.264 decoder is having a difficult time keeping up. Try reducing the frame rate, resolution or bit rate of the other device to see if that helps performance.
- If video is being sent from the device, it’s also possible the encoding and transmitting of frames is overwhelming the device, causing poor performance overall. Try reducing the frame rate and resolution of the outgoing video.
Do we plan to support SIP registration?
- Yes, see below for instructions.
Do we support broadcasting messages to multiple devices?
- Not currently. Possibly in a future release.
Does the T3x wake up when called?
- Not currently. Possibly in a future version. When the T3x goes to sleep WiFi is disabled, so it’s not aware of incoming calls, therefore, the T3x needs to be awake or docked (in which case WiFi isn’t disabled) in order to receive calls.
Device Setup and Programming
The device is configured via the VoIP tab of the Device Properties dialog in Integration Designer.
- If the IP address of a device is used to identify it on the network (instead of the Host Name) and the IP address changes, the other devices need to be updated to call the new IP address. Using a Host Name eliminates this requirement.
- RTI devices are setup to call other RTI devices with a pulldown menu in Integration Designer, so the IP address doesn’t need to be known at setup time. The IP address of the called RTI device is found at the time the call is placed because RTI devices can find each other automatically. This isn’t the case when calling 3rd party devices – they must have a known IP address or Host Name.