[aam]

Sipura have released firmware 3.1.7 (GWc) for the SPA3000.

[craig]

Anyone have any feedback on the echo issue? Does this revision fix it? (I'm having a bit of an issue upgrading mine and was wondering if it's worth the effort....)

[daryll]

Here's the release notes:
http://www.sipura.com/Documents/rnote/rn3k-3.1.7c.htm

No mention of the echo problem in the release notes. I guess we just have to try it and find out.

- |Daryll

[vsantiago]

After upgrading to this firmware, my SPA3000 continuously reboots every approx. 6 minutes. Does anybody experience the same problem?

Virgilio

[aam]

I haven't used 3.1.7 extensively yet, but I haven't noticed any reboots like you described.

[SuperCPA]

The release notes do not mention the echo problem, but after ungrading to 3.1.7, the echo found in 3.1.5 is gone.

[vsantiago]

Originally Posted by aam

I haven't used 3.1.7 extensively yet, but I haven't noticed any reboots like you described.

The 6min reboot cycle stopped after putting back 3.1.3a. I wonder if it has anything to do with my fxs-fxo strapped together since i'm using it to route voip-voip.

Virgilio

[thehothit]

I upgraded to 3.1.7 and had to downgrade again. I made a few test calls to my cellphone and a couple of landlines, and noticed that my outgoing CallerID info. was blocked. I tried forcing CallerID through with *65, but it just wouldn't go through.

I downgraded to 3.1.3 again and outgoing CallerID is fine. My SPA3000's hardware version is 2.0.1(96a3).

Is anyone else experiencing this problem?

Thanks,

Mike

[kendfw]

voip to pstn gateway functionality seems to be broken. After pin authentication, I received a fast busy signal tone. I can dial out using @gw0 from Line 1 and able to do pstn to voip call.

updates:
If I use outbound proxy in the pstn side, I could get the pstn gateway to dial out from the land line. Testing using two FWD accounts.

[thehothit]

Originally Posted by thehothit

I upgraded to 3.1.7 and had to downgrade again. I made a few test calls to my cellphone and a couple of landlines, and noticed that my outgoing CallerID info. was blocked. I tried forcing CallerID through with *65, but it just wouldn't go through.

I downgraded to 3.1.3 again and outgoing CallerID is fine. My SPA3000's hardware version is 2.0.1(96a3).

Is anyone else experiencing this problem?

Thanks,

Mike

Well - I took the plunge and upgraded to 3.1.7 again. It turns out that numbers in the User 1 speed dial settings are now processed through the Line 1 dialplan instead of being sent to the VOIP provider directly.

A little background...

My provider ViaTalk allows subscribers to force all outgoing calls as private, but you cannot selectively reveal your number, so I don't use that privacy feature - I created my own...

I have my dialplan setup to prefix my outgoing calls with *67, unless I dial a *65 in front of the number which I am dialing. In that case, the *67 is not dialed. It's kind of a hack, but it works beautifully.

User 1 speed dials in firmware versions prior to 3.1.7 bypassed the line 1 dialplan and thus outgoing CallerID info was revealed. 3.1.7 changed that and thus, because none of my speed dials had a *65 in front of the number, the dial plan prefixed the outgoing call with a *65. The solution was to stick a *65 in front of my speed dial numbers!

Did I miss this change to speed dial processing in the release notes?