Home » Forums » Vendor Forums - Certified » Sangoma

Repeating DTMF problem.

ah_clem
Posts: 74
 Member Since:
2007-09-16
Submitted by ah_clem on Fri, 11/20/2009 - 8:20am.

Just started trying to implement a Sangoma A200 card configured with FX0 and FXS (one each) modules. My issue is that I am getting inconsistent and intermittent results when trying to make an outbound call. Sometimes it's "All circuits are busy" from the Trixbox, sometimes it's "This call cannot be completed as dialed, you must dial "1" and the area code." from A.T.&T (PTSN provider) and other times it works fine.

In the "Must dial 1" scenario when I view the full.log file I see the complete dial string appearing in the log, but the PTSN acts as though it's incomplete.

"Sent deffered digit string: T1(area code and number)w"

I'm new to the whole Sangoma implementation, so please cut me some slack if I'm missing something...

trixbox CE current release is 2.8.0
Asterisk 1.4.20-1 RPM by vc-rpms@voipconsulting.nl built by root @ trixbuild-2.5
Not sure where to access the Sangoma, Zaptel, and Wanpipe versioning, sorry will supply if you'll tell me how to determine...

Thanks in advance.

‹ Log filling up with wanpipe3: Wanpipe Front End Interrupt Restart Timeout Unsupported SubVendor ›

&nbsp

ah_clem
Posts: 74
 Member Since:
2007-09-16
More information
Fri, 11/20/2009 - 2:47pm

I connected a butt set to the outbound line and from what I saw on the display, at one point the card dialed 88888888888888888888888...

Here is the log from that event:
[Nov 20 15:29:32] VERBOSE[10261] logger.c: -- Executing [s@macro-dialout-trunk:17] Macro("Zap/3-1", "dialout-trunk-predial-hook|") in new stack
[Nov 20 15:29:32] WARNING[10261] app_macro.c: Context 'macro-dialout-trunk-predial-hook' for macro 'dialout-trunk-predial-hook' lacks 's' extension, priority 1
[Nov 20 15:29:32] DEBUG[10261] app_macro.c: Executed application: Macro
[Nov 20 15:29:32] VERBOSE[10261] logger.c: -- Executing [s@macro-dialout-trunk:18] GotoIf("Zap/3-1", "0?bypass|1") in new stack
[Nov 20 15:29:32] DEBUG[10261] app_macro.c: Executed application: GotoIf
[Nov 20 15:29:32] VERBOSE[10261] logger.c: -- Executing [s@macro-dialout-trunk:19] GotoIf("Zap/3-1", "0?customtrunk") in new stack
[Nov 20 15:29:32] DEBUG[10261] app_macro.c: Executed application: GotoIf
[Nov 20 15:29:32] VERBOSE[10261] logger.c: -- Executing [s@macro-dialout-trunk:20] Dial("Zap/3-1", "ZAP/1/1-XXXXXXXXXX|300|") in new stack
[Nov 20 15:29:32] DEBUG[10261] chan_zap.c: Dialing '1-XXXXXXXXXX'
[Nov 20 15:29:32] DEBUG[10261] chan_zap.c: Deferring dialing...
[Nov 20 15:29:32] VERBOSE[10261] logger.c: -- Called 1/1-XXXXXXXXXX
[Nov 20 15:29:33] DEBUG[10261] chan_zap.c: Sent deferred digit string: T1-XXXXXXXXXXw
[Nov 20 15:29:34] DEBUG[10261] chan_zap.c: Started VLDTMF digit '8'
[Nov 20 15:29:34] DEBUG[10261] chan_zap.c: Ending VLDTMF digit '8'
...
The above 2 lines occur 32 times, then
...
[Nov 20 15:29:43] VERBOSE[10261] logger.c: -- Hungup 'Zap/1-1'


&nbsp

marc.sangoma
Posts: 373
 Member Since:
2008-04-08
Hi, As you can see here this
Mon, 11/23/2009 - 8:38am

Hi,

As you can see here this is an issue with Asterisk because you send "Dial("Zap/3-1", "ZAP/1/1-XXXXXXXXXX|300" which I am assuming you have replaced the number here with "XXXXXXXXXX". So you can see you run the command dial command and dial "XXXXXXXXXX" and then in the log it says its sending "8" 33 times. So if this is the case there is some sort of issue with Asterisk or your dial plan. I would suggest getting in contact with the Trixbox support; now the reason is the DTMF Asterisk is generating is all 8's. The only other thing it can be is the 8's are from the SIP phone. You can do a wireshark trace to have a look at this and see what is occurring there.

--

Marc


&nbsp

ah_clem
Posts: 74
 Member Since:
2007-09-16
Ah I'm not using a SIP Phone, in fact...
Wed, 11/25/2009 - 3:16pm

That is correct, the "XXXXXXXXXX" was done to mask the actual phone number which is correct in the log file.

This is not occurring when using a SIP phone. The phone that is being used is an analog phone (early ATT desk style) plugged into a FXO module on the same A200 card. Also I have tried a different analog phone with the same results. I do have a SIP phone connected to this system and so far I have not had the same problem when dialing out on the SIP phone. The analog ATT phone I have connected to the FXO module has in the past been connected to an analog POTS like and never used without any issues.

I am somewhat confused by your suggestion that it might be the phone given the fact that the correct number appears in the log file prior to the repeating digits from chan_zap.c

Also I had originally posted this to the general help area of the Trixbox forum and someone decided to move it here...


&nbsp

marc.sangoma
Posts: 373
 Member Since:
2008-04-08
Hi, Please enable SSH and
Thu, 11/26/2009 - 11:37am

Hi,

Please enable SSH and give me a call at 1-905-474-1990 x123 and I will have a look at this for you.

--

Marc


&nbsp

ah_clem
Posts: 74
 Member Since:
2007-09-16
I will call on Monday Nov. 30.
Sat, 11/28/2009 - 10:59pm

Wow what a trooper, working on Thanksgiving Day...

For some reason my subscription notification is not working here, I just got your message today (11/29)

Thank you, I will be contacting you on Monday Nov. 30th.


&nbsp

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.