Mtt Cannon
2018-Apr-05 12:20 UTC
[asterisk-users] Asterisk / PRI and Outbound Overlap Dialing
I am trying to setup Asterisk to act like a PBX connected via a PRI gateway
to a voice netowrk where Asterisk is doing outbound
overlap dialing for calls that terminate via that PRI. AFter researching
through the archives and online dcocs, I thought I had
everyting setup right, dialplan configured for '_X!' and the
'overlapdial=yes' in the chan_dahdi.conf file, but when I try and
make a call, while the first digit triggers the outbound SETUP message,
that SETUP message always includes a 'Sending Complete'
parameter and any subsequent digits received from the originaing client
seem to be getting ignored as opposed to sent over in
subsequent ISDN INFORMATION messages.
Any idea what I might be missing here...i did restart both DAHDI and
Asterisk after making the changes to support overlap.
Logs and snippets are below..
Thanks
matt
localhost*CLI> core show version
Asterisk 15.2.0 built by root @ localhost.localdomain on a x86_64 running
Linux on 2018-02-21 19:10:36 UTC
chan_dahdi.conf
; Overlap dialing mode (sending overlap digits)
; Cannot be changed on a reload.
;
; incoming: incoming direction only
; outgoing: outgoing direction only
; no: neither direction
; yes or both: both directions
;
overlapdial=yes
DialPlan
localhost*CLI> dialplan show sippOrig
[ Context 'sippOrig' created by 'pbx_config' ]
'_X!' => 1. Dial(DAHDI/g1/${EXTEN})
[extensions.conf:697]
-= 1 extension (1 priority) in 1 context. =-
localhost*CLI>
Debug trace of the ISDN messaging
-- Executing [7 at sippOrig:1] Dial("PJSIP/5712391000-00000019",
"DAHDI/g1/7") in new stack
PRI Span: 1 -- Making new call for cref 32794
-- Requested transfer capability: 0x00 - SPEECH
PRI Span: 1
PRI Span: 1 > DL-DATA request
PRI Span: 1 > Protocol Discriminator: Q.931 (8) len=34
PRI Span: 1 > TEI=0 Call Ref: len= 2 (reference 26/0x1A) (Sent from
originator)
PRI Span: 1 > Message Type: SETUP (5)
PRI Span: 1 TEI=0 Transmitting N(S)=46, window is open V(A)=46 K=7
PRI Span: 1
PRI Span: 1 > Protocol Discriminator: Q.931 (8) len=34
PRI Span: 1 > TEI=0 Call Ref: len= 2 (reference 26/0x1A) (Sent from
originator)
PRI Span: 1 > Message Type: SETUP (5)
PRI Span: 1 > [04 03 80 90 a3]
PRI Span: 1 > Bearer Capability (len= 5) [ Ext: 1 Coding-Std: 0 Info
transfer capability: Speech (0)
PRI Span: 1 > Ext: 1 Trans mode/rate: 64kbps,
circuit-mode (16)
PRI Span: 1 > User information layer 1:
A-Law (35)
PRI Span: 1 > [18 03 a1 83 81]
PRI Span: 1 > Channel ID (len= 5) [ Ext: 1 IntID: Implicit Other(PRI)
Spare: 0 Preferred Dchan: 0
PRI Span: 1 > ChanSel: As indicated in following
octets
PRI Span: 1 > Ext: 1 Coding: 0 Number Specified
Channel Type: 3
PRI Span: 1 > Ext: 1 Channel: 1 Type: CPE]
PRI Span: 1 > [6c 0c 21 81 35 37 31 32 33 39 31 30 30 30]
PRI Span: 1 > Calling Party Number (len=14) [ Ext: 0 TON: National Number
(2) NPI: ISDN/Telephony Numbering Plan (E.164/E.163) (1)
PRI Span: 1 > Presentation: Presentation
allowed, User-provided, verified and passed (1) '5712391000' ]
PRI Span: 1 > [70 02 80 37]
PRI Span: 1 > Called Party Number (len= 4) [ Ext: 1 TON: Unknown Number
Type (0) NPI: Unknown Number Plan (0) '7' ]
PRI Span: 1 > [a1]
PRI Span: 1 > Sending Complete (len= 1)
PRI Span: 1 q931.c:6531 q931_setup: Call 32794 enters state 1 (Call
Initiated). Hold state: Idle
-- Called DAHDI/g1/7
PRI Span: 1
PRI Span: 1 < Protocol Discriminator: Q.931 (8) len=14
PRI Span: 1 < TEI=0 Call Ref: len= 2 (reference 26/0x1A) (Sent to
originator)
PRI Span: 1 < Message Type: CALL PROCEEDING (2)
PRI Span: 1 < [18 03 a9 83 81]
PRI Span: 1 < Channel ID (len= 5) [ Ext: 1 IntID: Implicit Other(PRI)
Spare: 0 Exclusive Dchan: 0
PRI Span: 1 < ChanSel: As indicated in following
octets
PRI Span: 1 < Ext: 1 Coding: 0 Number Specified
Channel Type: 3
PRI Span: 1 < Ext: 1 Channel: 1 Type: CPE]
PRI Span: 1 < [1e 02 80 88]
PRI Span: 1 < Progress Indicator (len= 4) [ Ext: 1 Coding: CCITT (ITU)
standard (0) 0: 0 Location: User (0)
PRI Span: 1 < Ext: 1 Progress Description:
Inband information or appropriate pattern now available. (8) ]
PRI Span: 1 Received message for call 0x7fa6e00070b0 on link 0x1b1a130
TEI/SAPI 0/0
PRI Span: 1 -- Processing IE 24 (cs0, Channel ID)
PRI Span: 1 -- Processing IE 30 (cs0, Progress Indicator)
PRI Span: 1 q931.c:9095 post_handle_q931_message: Call 32794 enters state 3
(Outgoing Call Proceeding). Hold state: Idle
Span 1: Processing event PRI_EVENT_PROCEEDING(13)
-- DAHDI/i1/7-1a is proceeding passing it to PJSIP/5712391000-00000019
-- DAHDI/i1/7-1a is making progress passing it to
PJSIP/5712391000-00000019
> 0x7fa6c0068f00 -- Strict RTP learning after remote address set to:
10.100.0.95:51670
> 0x7fa6c0068f00 -- Strict RTP switching to RTP target address
10.100.0.95:51670 as source
[Apr 3 14:29:49] WARNING[25444][C-0000001a]: sig_pri.c:8797
sig_pri_digit_begin: Span 1: Digit '0' may be ignored by peer. (Call
level:3(Proceeding))
[Apr 3 14:29:49] WARNING[25444][C-0000001a]: sig_pri.c:8797
sig_pri_digit_begin: Span 1: Digit '3' may be ignored by peer. (Call
level:3(Proceeding))
[Apr 3 14:29:51] WARNING[25444][C-0000001a]: sig_pri.c:8797
sig_pri_digit_begin: Span 1: Digit '4' may be ignored by peer. (Call
level:3(Proceeding))
> 0x7fa6c0068f00 -- Strict RTP learning complete - Locking on source
address 10.100.0.95:51670
[Apr 3 14:29:51] WARNING[25444][C-0000001a]: sig_pri.c:8797
sig_pri_digit_begin: Span 1: Digit '7' may be ignored by peer. (Call
level:3(Proceeding))
[Apr 3 14:29:51] WARNING[25444][C-0000001a]: sig_pri.c:8797
sig_pri_digit_begin: Span 1: Digit '6' may be ignored by peer. (Call
level:3(Proceeding))
[Apr 3 14:29:52] WARNING[25444][C-0000001a]: sig_pri.c:8797
sig_pri_digit_begin: Span 1: Digit '2' may be ignored by peer. (Call
level:3(Proceeding))
[Apr 3 14:29:52] WARNING[25444][C-0000001a]: sig_pri.c:8797
sig_pri_digit_begin: Span 1: Digit '0' may be ignored by peer. (Call
level:3(Proceeding))
[Apr 3 14:29:52] WARNING[25444][C-0000001a]: sig_pri.c:8797
sig_pri_digit_begin: Span 1: Digit '0' may be ignored by peer. (Call
level:3(Proceeding))
[Apr 3 14:29:53] WARNING[25444][C-0000001a]: sig_pri.c:8797
sig_pri_digit_begin: Span 1: Digit '0' may be ignored by peer. (Call
level:3(Proceeding))
PRI Span: 1
PRI Span: 1 < Protocol Discriminator: Q.931 (8) len=9
PRI Span: 1 < TEI=0 Call Ref: len= 2 (reference 26/0x1A) (Sent to
originator)
PRI Span: 1 < Message Type: DISCONNECT (69)
PRI Span: 1 < [08 02 80 83]
PRI Span: 1 < Cause (len= 4) [ Ext: 1 Coding: CCITT (ITU) standard (0)
Spare: 0 Location: User (0)
PRI Span: 1 < Ext: 1 Cause: No route to destination (3),
class = Normal Event (0) ]
PRI Span: 1 Received message for call 0x7fa6e00070b0 on link 0x1b1a130
TEI/SAPI 0/0
PRI Span: 1 -- Processing IE 8 (cs0, Cause)
PRI Span: 1 -- Found active call: 0x7fa6e00070b0 cref:32794
PRI Span: 1 q931.c:9345 post_handle_q931_message: Call 32794 enters state
12 (Disconnect Indication). Hold state: Idle
Span 1: Processing event PRI_EVENT_HANGUP_REQ(15)
-- Span 1: Channel 0/1 got hangup request, cause 3
PRI Span: 1 q931.c:7332 q931_hangup: Hangup other cref:32794
PRI Span: 1 q931.c:7089 __q931_hangup: ourstate Disconnect Indication,
peerstate Disconnect Request, hold-state Idle
PRI Span: 1 q931.c:6124 q931_release: Call 32794 enters state 19 (Release
Request). Hold state: Idle
PRI Span: 1
PRI Span: 1 > DL-DATA request
PRI Span: 1 > Protocol Discriminator: Q.931 (8) len=9
PRI Span: 1 > TEI=0 Call Ref: len= 2 (reference 26/0x1A) (Sent from
originator)
PRI Span: 1 > Message Type: RELEASE (77)
PRI Span: 1 TEI=0 Transmitting N(S)=47, window is open V(A)=47 K=7
PRI Span: 1
PRI Span: 1 > Protocol Discriminator: Q.931 (8) len=9
PRI Span: 1 > TEI=0 Call Ref: len= 2 (reference 26/0x1A) (Sent from
originator)
PRI Span: 1 > Message Type: RELEASE (77)
PRI Span: 1 > [08 02 81 83]
PRI Span: 1 > Cause (len= 4) [ Ext: 1 Coding: CCITT (ITU) standard (0)
Spare: 0 Location: Private network serving the local user (1)
PRI Span: 1 > Ext: 1 Cause: No route to destination (3),
class = Normal Event (0) ]
-- Hungup 'DAHDI/i1/7-1a'
== Everyone is busy/congested at this time (1:0/0/1)
-- Auto fallthrough, channel 'PJSIP/5712391000-00000019' status is
'CHANUNAVAIL'
PRI Span: 1
PRI Span: 1 < Protocol Discriminator: Q.931 (8) len=5
PRI Span: 1 < TEI=0 Call Ref: len= 2 (reference 26/0x1A) (Sent to
originator)
PRI Span: 1 < Message Type: RELEASE COMPLETE (90)
PRI Span: 1 Received message for call 0x7fa6e00070b0 on link 0x1b1a130
TEI/SAPI 0/0
PRI Span: 1 q931.c:9204 post_handle_q931_message: Call 32794 enters state 0
(Null). Hold state: Idle
PRI Span: 1 q931.c:7332 q931_hangup: Hangup other cref:32794
PRI Span: 1 q931.c:7089 __q931_hangup: ourstate Null, peerstate Null,
hold-state Idle
PRI Span: 1 Destroying call 0x7fa6e00070b0, ourstate Null, peerstate Null,
hold-state Idle
Span 1: Processing event PRI_EVENT_HANGUP_ACK(9)
localhost*CLI>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.digium.com/pipermail/asterisk-users/attachments/20180405/ebb50ca3/attachment.html>
Richard Mudgett
2018-Apr-05 16:34 UTC
[asterisk-users] Asterisk / PRI and Outbound Overlap Dialing
On Thu, Apr 5, 2018 at 7:20 AM, Mtt Cannon <mcannon9180 at gmail.com> wrote:> > > I am trying to setup Asterisk to act like a PBX connected via a PRI > gateway to a voice netowrk where Asterisk is doing outbound > overlap dialing for calls that terminate via that PRI. AFter researching > through the archives and online dcocs, I thought I had > everyting setup right, dialplan configured for '_X!' and the > 'overlapdial=yes' in the chan_dahdi.conf file, but when I try and > make a call, while the first digit triggers the outbound SETUP message, > that SETUP message always includes a 'Sending Complete' > parameter and any subsequent digits received from the originaing client > seem to be getting ignored as opposed to sent over in > subsequent ISDN INFORMATION messages. > > Any idea what I might be missing here...i did restart both DAHDI and > Asterisk after making the changes to support overlap. > > Logs and snippets are below.. > > Thanks > matt > > > localhost*CLI> core show version > Asterisk 15.2.0 built by root @ localhost.localdomain on a x86_64 running > Linux on 2018-02-21 19:10:36 UTC > > > chan_dahdi.conf > > ; Overlap dialing mode (sending overlap digits) > ; Cannot be changed on a reload. > ; > ; incoming: incoming direction only > ; outgoing: outgoing direction only > ; no: neither direction > ; yes or both: both directions > ; > overlapdial=yes >Where is this option set in the chan_dahdi.conf file? To have any effect on a particular channel the option MUST be set before the channel line that creates the channel. [channels] context=incoming switchtype=euroisdn signaling=pri_cpe overlapdial=yes ; All options currently set are used to create the specified channels on the next line. channel=1-15,17-31 ; Any options set AFTER the channel line above DO NOT affect those channels. context=other Richard -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20180405/b93c5102/attachment.html>
Mtt Cannon
2018-Apr-06 12:57 UTC
[asterisk-users] Asterisk / PRI and Outbound Overlap Dialing
Thanks Richard, That did the trick. I had the 'overlapdial=yes' line farther down in the chan_dahdi.conf file. Moving up before the channel line worked. Appreciate the help. matt On Thu, Apr 5, 2018 at 12:37 PM Richard Mudgett <rmudgett at digium.com> wrote:> On Thu, Apr 5, 2018 at 7:20 AM, Mtt Cannon <mcannon9180 at gmail.com> wrote: > >> >> >> I am trying to setup Asterisk to act like a PBX connected via a PRI >> gateway to a voice netowrk where Asterisk is doing outbound >> overlap dialing for calls that terminate via that PRI. AFter researching >> through the archives and online dcocs, I thought I had >> everyting setup right, dialplan configured for '_X!' and the >> 'overlapdial=yes' in the chan_dahdi.conf file, but when I try and >> make a call, while the first digit triggers the outbound SETUP message, >> that SETUP message always includes a 'Sending Complete' >> parameter and any subsequent digits received from the originaing client >> seem to be getting ignored as opposed to sent over in >> subsequent ISDN INFORMATION messages. >> >> Any idea what I might be missing here...i did restart both DAHDI and >> Asterisk after making the changes to support overlap. >> >> Logs and snippets are below.. >> >> Thanks >> matt >> >> >> localhost*CLI> core show version >> Asterisk 15.2.0 built by root @ localhost.localdomain on a x86_64 running >> Linux on 2018-02-21 19:10:36 UTC >> >> >> chan_dahdi.conf >> >> ; Overlap dialing mode (sending overlap digits) >> ; Cannot be changed on a reload. >> ; >> ; incoming: incoming direction only >> ; outgoing: outgoing direction only >> ; no: neither direction >> ; yes or both: both directions >> ; >> overlapdial=yes >> > > Where is this option set in the chan_dahdi.conf file? To have any effect > on a particular channel the option > MUST be set before the channel line that creates the channel. > > [channels] > context=incoming > switchtype=euroisdn > signaling=pri_cpe > overlapdial=yes > > ; All options currently set are used to create the specified channels on > the next line. > channel=1-15,17-31 > ; Any options set AFTER the channel line above DO NOT affect those > channels. > > context=other > > Richard > > -- > _____________________________________________________________________ > -- Bandwidth and Colocation Provided by http://www.api-digital.com -- > > Check out the new Asterisk community forum at: > https://community.asterisk.org/ > > New to Asterisk? Start here: > https://wiki.asterisk.org/wiki/display/AST/Getting+Started > > asterisk-users mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20180406/1a4029bf/attachment.html>