[Asterisk-Users] Sipura 3000 FXO

[Rich Adamson]

Just did a quick check using the fxs (line 1) phone, dialed *67 and a
local number. The call completed via the pstn interface, rang the
intended phone, but the callerid was not blocked as intended by the *67
(which is the correct code for our central office).

That would imply the spa3k is not actually doing anything with *67,
including passing it to the CO. Debug level 3 reflects "[0]Block Cid Always"
coming from the spa however.

Best guess in terms of * dialing via the spa would be the same; the spa
doesn't appear to be doing anything with it. Given the hugh number of
spa configuration options though, I could easily have missed something
important.

------------------------
> I just upgaded this one tonight  - it went very smooth, fast, and calls 
> worked fine when it was done.
> 
> If anyone has one that is working, on any firmware, I'd appreciate if 
> they'd try a *67 and see if it works for them, though.
> 
> -d
> 
> At 10:24 PM 10/1/2004, you wrote:
> > > I just sent my unit back.  I don't know if it was defective or not. I
> > > think it was working before firmware upgrade but after upgrade I
> > > couldn't call In or Out.
> > > Sipura technical support is not responding either. I emailed them twice,
> > > the store I bought it from emailed them once as well and didn't get any
> > > reply either.
> > > So the unit went back, in my opinion their tech. support is non
> > > existent.
> >
> >We just blew one up, apparently, as well.
> >
> >We had manually configured it onto our network (no DHCP) and all was fine,
> >and then we downloaded the Sipura firmware update (Windows), and ran it.
> >
> >It got about halfway through, just fine, and then blew.  The unit was then
> >toast...  it wouldn't answer the '****' login via phone, and (interestingly
> >enough) while it retained a functioning IP stack with the IP network
> >parameters we had previously configured, it wouldn't answer on port 80.
> >It happily answered PING but nothing else we could determine.  The phone
> >port remained connected to the POTS port, etc.
> >
> >I've updated firmware on hundreds of different kinds of devices, and while
> >I have occasionally made a mistake and blown something up, this is one of
> >a very small number of times where there was no obvious reason for it to
> >have gone awry.  Everything's on UPS power, so no glitches, it was
> >statically configured with an IP, so no reboot-then-lost-settings, etc.
> >The only thing that struck me as possibly a bit different from normal was
> >that we had configured the IP configuration manually.  And, boy, that
> >process is sure SWEET!  (coming from someone who's used to configuring
> >stuff like laser printers with a three button interface and a few hundred
> >button presses)
> >
> >... JG
> >--
> >Joe Greco - sol.net Network Services - Milwaukee, WI - http://www.sol.net
> >"We call it the 'one bite at the apple' rule. Give me one chance [and] then I
> >won't contact you again." - Direct Marketing Ass'n position on e-mail 
> >spam(CNN)
> >With 24 million small businesses in the US alone, that's way too many apples.
> >_______________________________________________
> >Asterisk-Users mailing list
> >Asterisk-Users at lists.digium.com
> >http://lists.digium.com/mailman/listinfo/asterisk-users
> >To UNSUBSCRIBE or update options visit:
> >    http://lists.digium.com/mailman/listinfo/asterisk-users
> 
> _______________________________________________
> Asterisk-Users mailing list
> Asterisk-Users at lists.digium.com
> http://lists.digium.com/mailman/listinfo/asterisk-users
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-users

---------------End of Original Message-----------------