This email is intended as the beginning of a discussion on the sipXecs users
list to benefit people that are looking for information on types of trunks
to connect to sipXecs.  Please consider adding to this document with
relevant facts, and I will make it a wiki document for the benefit of the
community.

PRI (Primary Rate Interface) is an ISDN based standard, that uses Channels
in the PRI for individual calls.   It is delivered over T1 and E1.  It
supports G711 calls.  It uses a common signaling channel (D-Channel) to
control the 23 voice calls (US).

SIP trunks are IP based, and use the Session Initialization Protocal for its
common signaling channel.  They support calls based on several codec,
including G711, G729, G726, etc.

These distinct technologies require a gateway between them to be able to
process calls from a PRI to SIP.

If you have a PRI that you need to connect to sipXecs, you will need a
Gateway to perform the translation from PRI to sipXecs' SIP implementation.
Patton and Audiocodes are the two most commonly used gateways within the
sipXecs discussion list.

If you have a connection to an ITSP that is providing SIP trunks, it will be
via an IP connection.  This connection can use either Username/Password
Authentication, or it can use a Static IP address configuration.  Both are
supported using the integrated sipxbridge.

In PRI and SIP trunk implementation, DID calls are accepted within sipXecs
by simply inserting the DID number into the Alias field of a given
extension, or matching the extension number to the digits delivered by the
service provider.  Both are acceptable methods.

*** Caution - Some ITSP implementations of SIP cause issues with DID
deliver.  As just one example, they must be able to accept Invites without
SDP.
In my experience, Broadvox requires a static IP address for correct DID
deliver on their legacy network (I'd love to have that proven wrong and see
a working configuration for it)

Comments on other ITSP's welcome and encouraged here
..........................................................

_______________________________________________
sipx-users mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users/

Reply via email to