When I send a call from my TE410P using E&M, the legacy PBX answers
the call but doesn't route it. Any idea what this could be? I assume the
digits aren't being delivered properly to the legacy pbx. Any
suggestions on what config settings to muck with?
Asterisk SVN-branch-1.2-r40901 built by root @ pbx04 on a i686 running
Linux on 2007-01-14 14:05:02 UTC
zaptel.conf
e&m=1-24
span=1,1,0,esf,b8zs,yellow
e&m=49-72
span=3,3,0,esf,b8zs,yellow
# Global data
loadzone = us
defaultzone = us
zapata.conf
[trunkgroups]
spanmap => 1,1,1
spanmap => 3,2,3
[channels]
switchtype=5ess
signalling=em_w
group=1
channel => 1-24
group=2
channel => 49-72
usecallerid=yes
cidsignalling=dtmf
Any suggestions?
> When I send a call from my TE410P using E&M, the legacy > PBX answers the call but doesn't route it.> Any suggestions on what config settings to muck with?Do you have PRI ISDN or inband signaling trunks? Either way, it would be zapata.conf configs that would be the issue.> zapata.conf > [trunkgroups] > spanmap => 1,1,1 > spanmap => 3,2,3 > > [channels] > switchtype=5ess > signaling=em_wIf it is inband signaling trunks, have you tried to use 'em' instead of 'em_w'? The 'w' is telling asterisk to wait for a wink before sending the digits. Perhaps the legacy PBX is not sending the wink. Also, I believe (but may be wrong) that the 'trunksgroups' section is for ISDN. Switchtype is only for PRI ISDN so is not needed for inband signaling. Don Pobanz
Seemingly Similar Threads
- Astersik CVS HEAD + T1 e&m wink + IAX client doesnt detect call answered on Zap channel
- Asterisk and Mitel SX 200 Slip and Frame Errors causing Major Ala rms
- TDM400 FXO stops handling outgoing calls, but still accepts incoming?
- E&M Tie Line
- Asterisk 1.0.5 won't pick up incoming calls