* You are viewing Posts Tagged ‘PRI’

Real T1 trunk group…

Hey all!

I’m not sure if this went out the first time I sent it so I apologize now
if it’s a duplicate.

I’ve been banging my head against the wall for a while (almost 18 hours
today alone) with this one… I migrated our incomming T1′s from the Option
11 to our Asterisk box this morning. We have 1 local T1 and 2 long distance
T1′s. The local T1 went over with out a hitch. The problem is with my 2
long distance T1′s. The switch on the other end is a DMS250 I’m told so I
set Asterisk to DMS100 and got the timing, framing, etc all set. Well, the
D channels came up so thats good. I started getting dropped calls every
once in a while. I did a debug on the spans and saw the following:

PRI Span: 3
PRI Span: 3 < Protocol Discriminator: Q.931 (8) len=40
PRI Span: 3 < TEI=0 Call Ref: len= 2 (reference 857/0x359) (Sent from
originator)
PRI Span: 3 < Message Type: SETUP (5)
PRI Span: 3 < [04 03 80 90 a2]
PRI Span: 3 < Bearer Capability (len= 5) [ Ext: 1 Q.931 Std: 0 Info
transfer capability: Speech (0)
PRI Span: 3 < Ext: 1 Trans mode/rate: 64kbps,
circuit-mode (16)
PRI Span: 3 < User information layer 1:
u-Law (34)
PRI Span: 3 < [18 04 e9 80 83 08]
PRI Span: 3 < Channel ID (len= 6) [ Ext: 1 IntID: Explicit Other(PRI)
Spare: 0 Exclusive Dchan: 0
PRI Span: 3 < ChanSel: As indicated in following
octets
*PRI Span: 3 < Ext: 1 DS1 Identifier: 0
*PRI Span: 3 < Ext: 1 Coding: 0 Number Specified
Channel Type: 3
PRI Span: 3 < Ext: 0 Channel: 8 Type: CPE]
PRI Span: 3 < [20 02 00 e2]
PRI Span: 3 < Network-Specific Facilities (len= 2) [ Toll Free MEGACOM ]
PRI Span: 3 < [6c 0c 21 83 37 32 37 34 3033 34 30 37 34]
PRI Span: 3 < Calling Number (len=14) [ Ext: 0 TON: National Number (2)
NPI: ISDN/Telephony Numbering Plan (E.164/E.163) (1)

The key part is the “*Ext: 1 DS1 Identifier: 0*” part. That’s when calls
fail. Right now, all calls are coming in on span 3 and want to talk to
Identifier 0 (span 2). If a call comes in on span 2 and requests “*Ext: 1
DS1 Identifier: 1*”, it fails. I called Verizon and asked them what was
going on. Turns out, its configured as a trunk group. The tech mentioned
that I need to figure out how to set my identifiers on the group and I
should be good to go. I’ve done a ton of research about chan_dahdi.conf and
dahdi-channels.conf and I think the answer is trunk groups.

I tried configuring a trunkgroup and set the primary dch to 24 and the bdch
to 72 and then then spanmap’ed span 2 and 3 into group 1 (e.g. 2,1,0 and
3,1,1) but I don’t see anything when I do a “dahdi show channels” or a “pri
show spans” or a “pri show channels”, not even the channels not in the
group. If I delete the trunkgroup, all three commands return all the
channels.

I’m just curious if I’m going down the right path with trunkgroups for this
or if there is something else to take care of the DS1 Identifier issue.

So another quick look… when a sucessful call comes in it goes to DS1
Identifier 0… the Asterisk CLI shows the following:

Streaming Music to 75 callers ..

Hi

I want to play streaming music from an internet lp like
http://114.23.245.234:9000 . there will be maximum of 75 callers at a time.
Is combination of SetMusicon Hold and WaitMusiconHold command the best
option ? All callers would be calling on PRI lines. The streaming source
would be from a seminar and can run upto 2 hours.

Asterisk 1.8 – BRI D Channel going up and down every few seconds

Dear all,

I have the following challenge using Asterisk 1.8, using a Digium B410P
card on BRI (The Netherlands, KPN ISDN) .

DAHDI is running, dahdi_tools indicates OK on my span and light on back of
card is green.

However, in Asterisk i get the following warnings every few seconds:

[Jan 2 20:33:17] == Primary D-Channel on span 1 up
[Jan 2 20:33:26] == Primary D-Channel on span 1 down
[Jan 2 20:33:26] WARNING[1671]: sig_pri.c:1095 pri_find_dchan: Span 1:
D-channel is down!
[Jan 2 20:33:27] == Primary D-Channel on span 1 up
[Jan 2 20:33:37] == Primary D-Channel on span 1 down
[Jan 2 20:33:37] WARNING[1671]: sig_pri.c:1095 pri_find_dchan: Span 1:
D-channel is down!
[Jan 2 20:33:38] == Primary D-Channel on span 1 up
[Jan 2 20:33:47] == Primary D-Channel on span 1 down
[Jan 2 20:33:47] WARNING[1671]: sig_pri.c:1095 pri_find_dchan: Span 1:
D-channel is down!
[Jan 2 20:33:48] == Primary D-Channel on span 1 up

Result is I cannot dial out or in into Asterisk.

The asterisk module states the D Channel is going up and down every few
seconds. Some googling on Asterisk, BRI, and this warning indicates that
there might be an issue with Aterisk 1.8.x and euro BRI, version of LibPRI
etc.
has anybody experienced these problems on BRI? Any suggestions with regards
to these warnings are welcome!

Debugging call quality issues in Asterisk

Hola Asterisk Gurus,

We have a telephony server in India which runs CentOS release 5.7 (Final)
version with four-span Digium Card, one of which has two E1 PRI line
terminating on the server.

$ dahdi_hardware
pci:0000:07:08.0 wct4xxp+ d161:1420 Wildcard TE420 (5th Gen)

For the last couple of weeks on some calls, we’ve been experiencing call
quality issues, specifically on outbound calls. We haven’t had any
complaints on inbound call quality, and I’m forced to conclude that the
issue exists only for outbound calls.

We haven’t seen a pattern on call quality drops, except that it happens
during daytime, when the call volumes are good. A quick look at the system
stats(sar) do not report an increase in system activity coinciding with the
bad quality calls.

$ cat /proc/interrupts; sleep 10; cat /proc/interrupts
reports that there are 10k interrupts generated over a period of 10s. So, I
guess the issue is probably not with the resources. I might also be looking
at all the wrong parameters, being an asterisk/telephony n00b.

Would you folks give me pointers on the best way to figure out if the issue
is with the PRI line or with the server. Also, why does it happen
specifically for outbound calls? Greatly appreciate the help.

Set Caller Number in E1 PRI ISDN Lines

Hi,

I am having an E1 PRI ISDN Lines with 30 bearer channels and 1 D Channel
with hundred DIDs (Direct Inward Dialing) numbers attached to a Sangoma PRI
Card on the server,
I am using asterisk 1.8.5 on CentOS 5.6.

How can i configure DIDs so that if i make an outgoing call the DID number
should go to the caller not the pilot number

For example

PRI Numbers Range -> 31303000 – 31303099
Pilot Number -> 31303000

So if i need to set caller number as 31303008 for example and not as
31303000, is there a way to set this in dial plan (extensions.conf)

Please guide and let me know if anyone needs more information and have
questions.

Regards,

Kaushal