Russell Brown
2007-Jun-28 11:05 UTC
[asterisk-users] Asterisk 1.4.5 Inserting Random Digits in Dialed Number!
Eeeeck! Asterisk is inserting random digits in dialed numbers.
So far I've seen it insert a 2 after the STD (area) code and insert an
extra 6 or 7 in the STD code. It's pretty repeatable although the
inserted number changes.
My Config is: Asterisk 1.4.5, Zaptel 1.4.3, Digium TE205P (rev 02).
There's an ISDN PBX on the second span and a BRI euroisdn on the first.
Calls from the ISDN PBX (Network Alchemy Argent Office FWIW) get put
into the 'alchemy' context which contains:
[alchemy]
;
include => dial_pstn
;
; Dial Out to PSTN
;
[dial_pstn]
exten => _X.,1,Dial(Zap/g1/${EXTEN})
exten => _X.,2,Congestion
;
Pretty simple and didn't cause problems before I went to 1.4.4/5
Here's the console log from a failing call (non-significant numbers
obscured to protect the guilty!).
*CLI> -- Accepting overlap call from '1780471800' to
'0173' on channel 0/15, span 2
-- Starting simple switch on 'Zap/46-1'
[Jun 28 12:00:32] DTMF[6387]: channel.c:2297 __ast_read: DTMF end '3'
received on Zap/46-1, duration 0 ms
[Jun 28 12:00:32] DTMF[6387]: channel.c:2297 __ast_read: DTMF end '2'
received on Zap/46-1, duration 0 ms
[Jun 28 12:00:33] DTMF[6387]: channel.c:2297 __ast_read: DTMF end '3'
received on Zap/46-1, duration 0 ms
[Jun 28 12:00:33] DTMF[6387]: channel.c:2297 __ast_read: DTMF end '5'
received on Zap/46-1, duration 0 ms
[Jun 28 12:00:33] DTMF[6387]: channel.c:2297 __ast_read: DTMF end 'x'
received on Zap/46-1, duration 0 ms
[Jun 28 12:00:33] DTMF[6387]: channel.c:2297 __ast_read: DTMF end 'x'
received on Zap/46-1, duration 0 ms
[Jun 28 12:00:33] DTMF[6387]: channel.c:2297 __ast_read: DTMF end 'x'
received on Zap/46-1, duration 0 ms
-- Executing [017332235xxx at alchemy:1] Dial("Zap/46-1",
"Zap/g1/017332235xxx") in new stack
-- Requested transfer capability: 0x00 - SPEECH
-- Called g1/017332235xxx
-- Zap/1-1 is proceeding passing it to Zap/46-1
As you can see, the ISDN PBX passed 01733 235xxx but Asterisk decided to
dial 01733 2235xxx (an extra '2' after the STD code).
Arrrrrrgh!!! This is driving both us and the people who're getting
called incorrectly potty :-(
Can anyone help? Thanks in advance.
--
Regards,
Russell
--------------------------------------------------------------------
| Russell Brown | MAIL: russell at lls.com PHONE: 01780 471800 |
| Lady Lodge Systems | WWW Work: http://www.lls.com |
| Peterborough, England | WWW Play: http://www.ruffle.me.uk |
--------------------------------------------------------------------
Eric "ManxPower" Wieling
2007-Jun-28 15:07 UTC
[asterisk-users] Asterisk 1.4.5 Inserting Random Digits in Dialed Number!
Remove any relaxdtmf= options from your zapata.conf. Russell Brown wrote:> Eeeeck! Asterisk is inserting random digits in dialed numbers. > > So far I've seen it insert a 2 after the STD (area) code and insert an > extra 6 or 7 in the STD code. It's pretty repeatable although the > inserted number changes. > > My Config is: Asterisk 1.4.5, Zaptel 1.4.3, Digium TE205P (rev 02). > > There's an ISDN PBX on the second span and a BRI euroisdn on the first. > > Calls from the ISDN PBX (Network Alchemy Argent Office FWIW) get put > into the 'alchemy' context which contains: > > [alchemy] > ; > include => dial_pstn > ; > ; Dial Out to PSTN > ; > [dial_pstn] > exten => _X.,1,Dial(Zap/g1/${EXTEN}) > exten => _X.,2,Congestion > ; > > Pretty simple and didn't cause problems before I went to 1.4.4/5 > > Here's the console log from a failing call (non-significant numbers > obscured to protect the guilty!). > > *CLI> -- Accepting overlap call from '1780471800' to '0173' on channel 0/15, span 2 > -- Starting simple switch on 'Zap/46-1' > [Jun 28 12:00:32] DTMF[6387]: channel.c:2297 __ast_read: DTMF end '3' received on Zap/46-1, duration 0 ms > [Jun 28 12:00:32] DTMF[6387]: channel.c:2297 __ast_read: DTMF end '2' received on Zap/46-1, duration 0 ms > [Jun 28 12:00:33] DTMF[6387]: channel.c:2297 __ast_read: DTMF end '3' received on Zap/46-1, duration 0 ms > [Jun 28 12:00:33] DTMF[6387]: channel.c:2297 __ast_read: DTMF end '5' received on Zap/46-1, duration 0 ms > [Jun 28 12:00:33] DTMF[6387]: channel.c:2297 __ast_read: DTMF end 'x' received on Zap/46-1, duration 0 ms > [Jun 28 12:00:33] DTMF[6387]: channel.c:2297 __ast_read: DTMF end 'x' received on Zap/46-1, duration 0 ms > [Jun 28 12:00:33] DTMF[6387]: channel.c:2297 __ast_read: DTMF end 'x' received on Zap/46-1, duration 0 ms > -- Executing [017332235xxx at alchemy:1] Dial("Zap/46-1", "Zap/g1/017332235xxx") in new stack > -- Requested transfer capability: 0x00 - SPEECH > -- Called g1/017332235xxx > -- Zap/1-1 is proceeding passing it to Zap/46-1 > > As you can see, the ISDN PBX passed 01733 235xxx but Asterisk decided to > dial 01733 2235xxx (an extra '2' after the STD code). > > > Arrrrrrgh!!! This is driving both us and the people who're getting > called incorrectly potty :-( > > Can anyone help? Thanks in advance. >