[Home]

Summary:ASTERISK-16168: No transfer or MOH activated for AMI D4 circuit
Reporter:David Hansen (applexpanther)Labels:
Date Opened:2010-05-28 14:22:13Date Closed:2011-06-07 14:05:00
Priority:MinorRegression?No
Status:Closed/CompleteComponents:Channels/chan_dahdi
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:
Description:I have 2 circuits coming into a dahdi card with exact same settings.  Placing Calls coming in the D4/AMI circuit on hold, do not activate MOH.  It doesnt show up on the console. Nor can I transfer.   The same scenario coming in on a PRI, MOH and transfers work just fine.
Comments:By: David Hansen (applexpanther) 2010-05-28 14:23:13

[trunkgroups]

[channels]
echocancel=yes
transfer=yes
threewaycalling=yes
cancallforward=yes
callwaiting=yes
usercallerid=no
usecallingpres=yes
canpark=yes
language=en
relaxdtmf=yes
;usecallerid=yes
hidecalleridname=no
;pridialplan=dynamic
;prilocaldialplan=national
callerid=asreceived
;immediate=no


;group=0
;signalling=em_w
;context=att_t1
;channel => 1-24

;grm circuit
group=1
context=grm_t1
signalling=em_w
channel => 25-48

;pri g2
group=2
signalling=pri_net
switchtype=dms100
context=nortel_grm
channel => 49-71

;regular t1 g3
group=3
signalling=em_w
context=nortel_grm
channel => 73-96
By: David Hansen (applexpanther) 2010-05-28 14:27:21

Sorry they arent the exact same settings, ones a pri and ones a d4/ami.  but there are no setting that apply to one group specifically beyond that.
By: Leif Madsen (lmadsen) 2010-06-02 10:10:14

You'll need to provide some debug information that shows what is going on with the channels. You haven't described the scenario or the topology and what end point is placing the calls on hold.

Please provide debugging information for each of the channels involved in the call.
By: Paul Belanger (pabelanger) 2010-06-10 15:01:48

Suspended due to lack of activity. Please request a bug marshal in #asterisk-bugs on the IRC network irc.freenode.net to reopen the issue should you have the additional information requested.

Further information can be found at http://www.asterisk.org/developers/bug-guidelines