Hi,
This seems to be an issue of terminology,
On Thu, Sep 24, 2015 at 05:08:24PM -0500, Jeff LaCoursiere wrote:
>
> Hi,
>
> I have a client that has a 24 channel voice T1 that I have been using e
> signalling over for a number of years. The local telco finally got an ISDN
> switch and wants
On 09/30/2015 07:47 AM, Tzafrir Cohen wrote:
[snip]
Right. For Sangoma cards, lsdahdi can't tell if the port is E1 or T1 and
thus calls it "PRI". Note that "PRI" here is a poor name that refers to
the port type itself and not to the signalling in it (which don't have
to be ISDN).
Suggestions?
Hi,
I have a client that has a 24 channel voice T1 that I have been using
e signalling over for a number of years. The local telco finally got
an ISDN switch and wants to move them to PRI. I didn't see this as a
big problem - I've done a few others on this particular Caribbean island
[snip]
So what about system.conf would cause lsdahdi to show "T1" instead of
"PRI" in column two? Just trying to head off any additional problems
once they get their patching sorted out.
The issue is probably with the wanpipe configuration and not with
DAHDI or Asterisk. Run the
On 2015-09-24 17:08, Jeff LaCoursiere wrote:
Hi,
I have a client that has a 24 channel voice T1 that I have been using
e signalling over for a number of years. The local telco finally
got an ISDN switch and wants to move them to PRI. I didn't see this
as a big problem - I've done a few others
