Channels

From Taridium

(Difference between revisions)
Jump to: navigation, search
(New page: Channels specify how an end-point communicates with ipbx. == SIP Channels == The SIP Channel Module enables ipbx to communicate via VOIP with SIP telephones and exchanges. These are us...)
Line 1: Line 1:
-
 
+
Channels specify how an end-point communicates with ipbx.
-
Channels specify how an end-point communicates with ipbx.  
+
== SIP Channels ==
== SIP Channels ==
The SIP Channel Module enables ipbx to communicate via VOIP with SIP telephones and exchanges. These are usually SIP clients. Trunks and other static end-points are usually configured separately.
The SIP Channel Module enables ipbx to communicate via VOIP with SIP telephones and exchanges. These are usually SIP clients. Trunks and other static end-points are usually configured separately.
 +
 +
 +
== IAX Channels ==
== IAX Channels ==
The IAX Channel Module enables ipbx to communicate via VOIP with IAX telephones and exchanges. Only IAX2 communication is supported at this point. Trunks and other static end-points are usually configured separately.
The IAX Channel Module enables ipbx to communicate via VOIP with IAX telephones and exchanges. Only IAX2 communication is supported at this point. Trunks and other static end-points are usually configured separately.

Revision as of 15:20, 2 December 2008

Channels specify how an end-point communicates with ipbx.

SIP Channels

The SIP Channel Module enables ipbx to communicate via VOIP with SIP telephones and exchanges. These are usually SIP clients. Trunks and other static end-points are usually configured separately.



IAX Channels

The IAX Channel Module enables ipbx to communicate via VOIP with IAX telephones and exchanges. Only IAX2 communication is supported at this point. Trunks and other static end-points are usually configured separately.

Personal tools
Namespaces
Variants
Actions
Toolbox