Dear Voxilla members,

I am using the SPA-3000 firmware 3.1.7g. I can make and receive calls through both voip and pstn alright. But whenever I pick up the handset and make a call through pstn, i hear a pre-dial ringing tone right after i dial.

Assuming the local PSTN number 2345678 I am calling is busy, and the following are the steps I made that call.

1) pick up the headset, hear a dial tone.
2) Dial the local pstn number 23456789
3) I hear an Instant “Pre-Dial Ringing Tone” almost right after I dial the number. The tone is a single 1 sec ring. Just like a connecting signal.
4) Silent for 2 seconds
5) Get busy tone

Everything sounds normal to me except the Pre-Dial Ringing tone in step 3. It looks like a tone indicating the phone number is accepted by SPA to dial pstn, but to the user , it’s confusing. You know, you got a ringing tone and then followed by a busy tone. Isn’t that weird ?

Is there a way to get rid of the confusing “Pre-Dial Ringing Tone” ? sorry, I have no idea what that is called..

Noticed that it is DIFFERENT from the double ring-back tone as discussed in some of the forums and also if i use my gw1 VOIP to dial to other sip phones, the "Pre-Dial Ringing Tone" will disappear.

Here’s my dialplan in Line1 tab

( [23689]xxxxxxxS0<:@gw0> | <#1,:> xx. <:@gw1> )

many thanks for any kind of assistance.

- Alex

Having just bought a Sipura 3000, I skimmed through the manual and saw a setting called 'two-stage dialing'. This may be the setting to play with. It determines if the Sipura holds the digits and dails when you're done dialing, or sends your digits directly to the PSTN line.

BTW. Where did you get firmware 3.1.7g?

1-stage and 2-stage dialing are for VOIP-PSTN Gateway, meaning you remote call-into the SPA from an outside sipphone and then to call out a local pstn phone number thru the PSTN line. That part is working perfectly for me already.

but for my case where i have the problem (mentioned above), i simply use my analog phone connected to FXS to make a local Hong Kong PSTN call.

you can find 3.1.7g at
http://www.myphonecall.co.uk/support...e/default.aspx

thanks for your attempt to help though !!

any other ideas dear members...

- Alex

edokter,
i tried your suggestion anyways. Whether 1 stage or 2 stage, it doesn't solve my problem.
:-( -alex

I don't know where the ring comes from then... I have it set up so that when I dial 00, I get the outside dialton directly from the outside line. Put the following in front of your dialplan.

(<00:>S0 <:@gw0>|...

Also, *clear* Dialplan 1 on the PSTN page, otherwise you get the 'outside dialtone' generated by the Sipura.

I 've tried clear everything in dialplan1 PSTN tab. that strange tone is still there. but correct me if i am wrong, i thought the dialplans in PSTN tab are for VOIP callers remote access PSTN gateway only. In this case, why does it matter to me ??

May i ask , let say, if the pstn number you are calling doesn't even exist. when you pick up the analog phone, then hear a dial tone, then hit 00, then hear another dial tone, then dial a the number. what do you hear then?? do you hear 1 tone only, that is the tone of a nonexistence number. or you hear an extra ringtone right before ?

Also, can you just try a dialplan of
(<00:>xx. <:@gw0>

Now, do you hear that extra tone ??

Thanks !

- Alex

There's a setting somewhere in the web interface for a warning tone when calls are routed to PSTN.

I don't remember where it is or what it's called and I gotta run right now but if you have trouble finding it post again.

Dear ArgMeMatey,

The PSTN warning tone is at the Regional Tab. I've tried cleared out the field, but the tone is not getting away. any other ideas ?? are you getting the same thing ?

-Alex

Hmmm. Unfortunately I backpedaled to 3.1.3 because I had echo issues with 3.1.7.

But, when I was using 3.1.7, I was able to stop the warning tone by toggling that field.

Did you power cycle?

Hi ArgMeMatey,

yes, i did a complete power recycle. but still not working.

Anymore suggustion ?? I am clueless. I tried almost anything I can think of.

Do you mean after you downgrade to Firmware 3.1.3, you are not experiencing the problem at all ??

- Alex