editor
698
edits
VoIP - Technical Information: Difference between revisions
m
→FireBrick technical features: clean up, typos fixed: each others → each other's
(Created page with "__NOTOC__<indicator name="Configuring">link=:Category:VoIP Features|30px|Back up to the VoIP Features Category</indicator> ==Multiple servers== We opera...") |
m (→FireBrick technical features: clean up, typos fixed: each others → each other's) |
||
|
*SIP/2.0 UDP control messages using IPv4 or IPv6 are supported up to approximately 1900 bytes (fragmented if necessary).
The FireBrick always acts as an audio media endpoint, i.e. it is always in the media path. This minimises call routing and firewalling issues. The FireBrick uses the same IP for media and control messages on each call.
*The FireBrick always acts as a SIP protocol endpoint and not as a relaying proxy. This minimises incompatibility between end devices being a party to a call as they do not see each
*Only RTP audio using a-law 20ms is supported. This is generally compatible with all carriers and devices and provides high quality audio.
*Out of band DTMF is accepted using SIP INFO or RFC2833. DMTF can be sent using RFC2833 or generated a-law in-band audio.
| |||