SPA122 Fw 1.2.1-004 Stability

My company is about to deploy approximately 70 SPA122's and I'm looking for everyones opinions on the stability and operation of SPA122 firmware v1.2.1-004.

"My company is about to make a big mistake and deploy approximately 70 broken SPA122's"
There I fixed your question that you where asking.
I gave up the SPA122's (really I did) they are not ready for production use, even one year later after there release to market! They're way too many issues outstanding that affect these units in everyday use.
You've been warned

Similar Messages

SPA112 ATA CallerID issue causes device to hang

Hi Everyone,
I just thought I would share my experience with an issue setting up my SPA112 with voip.ms. Although I still do not have a solution, the Cisco technical support has been very helpful allowing us to track down and debug the issue.
Hardware: SPA112
Firmware: 1.1.0 (011) Feb 10 2012
ITSP: voip.ms
Service Number: SR 622048069
issue:
Inbound calls through the DID cause SPA112 to ring once. The ATA immediately drops the call and loses ethernet. The device is unresponseive until it is rebooted. If the device is not rebooted, there is no dial tone on the headset connected to the ATA.
The device hangs when I called it from my cell phone or from skype dialed to a phone number. The device works when I call it from another voip extension or through any softphone connected to my asterisk PBX on my local network.
The device works fine when the cisco representiative called from his companies voip phone and his companies analoge non-voip line.
We've tested the device with and without a NAT with the SIP connected directly to voip.ms (no asterisk server running).
After setting up some debug equipement, the cisco representative was able to determine that the cause of the hangup was related to incoming callerid errors. We are still invegstiating the issue and I will keep you posted as I get more information.
The device only seems to fail when it recieves calls from some numbers. I do not know which incoming numbers cause this issue at this point.
work around:
1) At this time the PAP2T, which uses the exact same settings as the SPA112, works without any problems.
2) We are also looking into alternatives, such as disabling the CallerID on the SPA112 until the firmware is upgraded or overriding the caller ID info using my asterisk server.
Justin

I recently purchased a SPA112 myself & I've discovered a very similar issue.
Inbound calls from my work (VoIP system) cause SPA112 to ring once. The ATA immediately drops the call and loses ethernet/internet. The device is unresponseive until it is rebooted. If the device is not rebooted, there is no dial tone on the handsets connected to the ATA.
I've updated my firmware to
Firmware for SPA112 and SPA122, Version 1.2.1(004)
Release Date: 15 Aug 2012 Release: 1.2.1(004)

SPA122 FW upgraded to 1.2.1 (004) now all incoming calls are droped

I upgraded my SPA122 to Version 1.2.1 (004) and Now all my incoming (inbound) calls are dropped "Status: 480 Temporarily Not available"
Outbound calls are working Ok.
With the same config and with FW 1.1.0 (011) all was working Fine.
Is there any way to donwgrade to the previous "working" FW version ?

I'm sorry, don't want be rude, but i can't post my config on a public forum.
I just want a "Working" way (Not the ones listed on admin guide) to Downgrade the FW to the previous "Working Good" version.
Thanks for your interest in my Problem.
Attached the "debug Log" from the SPA122

How to upgrade the spa122 firwmare to 1.2.1(004) using configurtion file

Hello,
Highly appreciate if anyone can let me know how to define the upgrade rule in configruation file to upgrade the firmware to 1.2.1(004) -
is it ok if I define it in upgrade rule as below
<Upgrade_Rule> (!1.2.1(004))?http://10.1.1.1/SPA112_SPA122_1.2.1_FW.bin </Upgrade_Rule>
if not, what is the correct one
Regards,
Denning

Yes, it's old legacy syntax. The recommended syntax is:
...Rule> ($SWVER != 1.2.1(004))?http ...
Unfortunately, such type of conditional doesn't work reliable most times for me (althougth I didn't tested the particular one from your example).
I don't know why.
I suspect, that firmware numbers like 7.4.9c or 7.5.2b may be source of problem - Cisco's Provisioning guide claim that version numbers take form of three non-negative numbers separated by periods followed by optional alphanuberic string in parthenses. It's not true for some released versions. May be, the comparsion logic doesn't handle those broken version numbers correctly.

SPA122 freezes when upgrading to 1.3.1(003) via provisioning

I've started pushing out the v1.3.1(003) upgrade to a few of our deployed devices via the provisioning file, but in a test I did last night, 5 out of the 6 SPA122s that I upgraded froze after applying the update.
The server's access logs look like this:
$ zgrep '71.238.**.***' logs/access20130116.log.gz
71.238.**.*** - - [16/Jan/2013:21:47:29 -0800] "GET /ccef4******* HTTP/1.0" 200 17490 "-" "Cisco/SPA122-1.1.0(011) (CBT1*******)"
71.238.**.*** - - [16/Jan/2013:21:48:21 -0800] "GET /firmware/SPA112_SPA122_1.3.1_003.bin HTTP/1.0" 200 9945472 "-" "Cisco/SPA122-1.1.0(011) (CBT1*******)"
71.238.**.*** - - [16/Jan/2013:21:48:35 -0800] "GET /firmware/SPA112_SPA122_1.3.1_003.bin HTTP/1.0" 200 9945472 "-" "Cisco/SPA122-1.1.0(011) (CBT1*******)"
$
I would have expected the ATA to provision again after upgrading, but it has to be rebooted before it will come back online. It's kind of scary to reboot a device manually after a firmware upgrade without something saying it's okay to do so.
Has anyone else observed this behavior?

Okay, I tried the two-step upgrade process as Patrick's document suggested, but found that the ATA still froze, this time after upgrading from v1.1.0(011) to v1.2.1(004).
I was able to get syslog results this time, and the device seems to be freezing at the postupgrade handling.
Feb 13 23:31:27 c-ipaddress.hsd1.pa.comcast.net [FPRV] Upgrade status flags cleared
Feb 13 23:32:04 c-ipaddress.hsd1.pa.comcast.net IDBG: LS, 262-4fb
Feb 13 23:32:04 c-ipaddress.hsd1.pa.comcast.net IDBG: SOK
Feb 13 23:32:04 c-ipaddress.hsd1.pa.comcast.net IDBG: st-0
Feb 13 23:32:04 c-ipaddress.hsd1.pa.comcast.net get_dhcp_option66_67_info, voice interface is 'br0'
Feb 13 23:32:04 c-ipaddress.hsd1.pa.comcast.net uchInitDTMFTbl(), dtmf level -100
Feb 13 23:32:04 c-ipaddress.hsd1.pa.comcast.net uchEnableEchoCan(), lid 0 EP 2 enable
Feb 13 23:32:04 c-ipaddress.hsd1.pa.comcast.net uch_syncParameter(), uch_syncDTMFHoldOffTime(0)=0
Feb 13 23:32:04 c-ipaddress.hsd1.pa.comcast.net uchEnableEchoCan(), lid 1 EP 1 enable
Feb 13 23:32:04 c-ipaddress.hsd1.pa.comcast.net uch_syncParameter(), uch_syncDTMFHoldOffTime(1)=0
Feb 13 23:32:04 c-ipaddress.hsd1.pa.comcast.net CC: init after ether ...
Feb 13 23:32:04 c-ipaddress.hsd1.pa.comcast.net CC: init after ether ...
Feb 13 23:32:04 c-ipaddress.hsd1.pa.comcast.net sys_events_comm_start_named(spr_voip) = 18
Feb 13 23:32:05 c-ipaddress.hsd1.pa.comcast.net SCAPC_init(): provision_enable=1 prule=https://provserver/$MA tftp=
Feb 13 23:32:05 c-ipaddress.hsd1.pa.comcast.net #011going to sleep 20 csec
Feb 13 23:32:05 c-ipaddress.hsd1.pa.comcast.net #011going to sleep 20 csec
Feb 13 23:32:06 c-ipaddress.hsd1.pa.comcast.net fs: 060406:060731:262144
Feb 13 23:32:06 c-ipaddress.hsd1.pa.comcast.net fbr: 0:3000:3000:010b84:0002:0001:1.1.0(011)
Feb 13 23:32:06 c-ipaddress.hsd1.pa.comcast.net PLKUP: 2048, 633, 7, 1.3
Feb 13 23:32:06 c-ipaddress.hsd1.pa.comcast.net [SCAPC]WaitTime: 10
Feb 13 23:32:06 c-ipaddress.hsd1.pa.comcast.net [SCAPC]WaitTime: 10
Feb 13 23:32:07 c-ipaddress.hsd1.pa.comcast.net [SCAPC]WaitTime: 20
Feb 13 23:32:07 c-ipaddress.hsd1.pa.comcast.net [SCAPC]WaitTime: 20
Feb 13 23:32:08 c-ipaddress.hsd1.pa.comcast.net [SCAPC]WaitTime: 40
Feb 13 23:32:08 c-ipaddress.hsd1.pa.comcast.net [SCAPC]WaitTime: 40
Feb 13 23:32:09 c-ipaddress.hsd1.pa.comcast.net [SCAPC]WaitTime: 80
Feb 13 23:32:09 c-ipaddress.hsd1.pa.comcast.net [SCAPC]WaitTime: 80
Feb 13 23:32:09 c-ipaddress.hsd1.pa.comcast.net [LVS]Cannot resolve LVS_PROXY. Read lvs address from flash. IP =
Feb 13 23:32:09 c-ipaddress.hsd1.pa.comcast.net sysstatus_set_led_status_payton(), led_id: 0, statusCode:0, systemEvent: 0xfffe
Feb 13 23:32:09 c-ipaddress.hsd1.pa.comcast.net sysstatus_set_led_status_payton(), led_id: 1, statusCode:0, systemEvent: 0xfffe
Feb 13 23:32:09 c-ipaddress.hsd1.pa.comcast.net sysstatus_set_led_status_payton(), led_id: 2, statusCode:0, systemEvent: 0xfffe
Feb 13 23:32:10 c-ipaddress.hsd1.pa.comcast.net [0]Reg Addr Change(0) 0:0->a2e0148:6060
Feb 13 23:32:10 c-ipaddress.hsd1.pa.comcast.net [0]Reg Addr Change(0) 0:0->a2e0148:6060
Feb 13 23:32:10 c-ipaddress.hsd1.pa.comcast.net [0]RegOK. NextReg in 3570 (1)
Feb 13 23:32:10 c-ipaddress.hsd1.pa.comcast.net CC_eventProc(), event: CC_EV_SIG_REGISTER_OK(0x3A), lid: 0, par: 0, par2: (nil)
Feb 13 23:32:10 c-ipaddress.hsd1.pa.comcast.net AUD_ccEventProc: event 58 vid 0 par 0x0 par2 0x0
Feb 13 23:32:10 c-ipaddress.hsd1.pa.comcast.net sysstatus_set_led_status_payton(), led_id: 1, statusCode:1, systemEvent: 0x100093
Feb 13 23:32:12 c-ipaddress.hsd1.pa.comcast.net [0]CID: CID_initGen() >>> offhook 0 delay 0 phone - name -
Feb 13 23:32:12 c-ipaddress.hsd1.pa.comcast.net CID: OSI
Feb 13 23:32:12 c-ipaddress.hsd1.pa.comcast.net [0]CID CID_ST_OSI
Feb 13 23:32:12 c-ipaddress.hsd1.pa.comcast.net CID: OnHookTx Pol
Feb 13 23:32:12 c-ipaddress.hsd1.pa.comcast.net [0]CID CID_ST_OSI_POST_DELAY
Feb 13 23:32:12 c-ipaddress.hsd1.pa.comcast.net uchDisplayCIDFSK(), EP 2 lid 0 buflen 66 overhead 60 SZ_MAX_USERDATA 200
Feb 13 23:32:13 c-ipaddress.hsd1.pa.comcast.net [0]CID Start DTMF/FSK, CID_ST_ACTIVE
Feb 13 23:32:13 c-ipaddress.hsd1.pa.comcast.net [0]CID CID_ST_FSK_COMP_DELAY
Feb 13 23:32:13 c-ipaddress.hsd1.pa.comcast.net [0]CID CID:DONE
Feb 13 23:32:13 c-ipaddress.hsd1.pa.comcast.net [0]CID CID_ST_ACTIVE_POST_DELAY
Feb 13 23:32:13 c-ipaddress.hsd1.pa.comcast.net [0]CID CID_ST_IDLE
Feb 13 23:32:16 c-ipaddress.hsd1.pa.comcast.net fs: 060421:060731:262144:112812327999
Feb 13 23:32:16 c-ipaddress.hsd1.pa.comcast.net [fprv_test_download_file]test download url
Feb 13 23:32:16 c-ipaddress.hsd1.pa.comcast.net [fprv_test_download_file] get dn_schema 3 path=/firmware/SPA112_SPA122_1.2.1_FW.bin ip ipaddress
Feb 13 23:32:16 c-ipaddress.hsd1.pa.comcast.net [fprv_test_download_file] http(s) upg url provserver:443
Feb 13 23:32:18 c-ipaddress.hsd1.pa.comcast.net ok=0
Feb 13 23:32:29 c-ipaddress.hsd1.pa.comcast.net sysstatus_set_led_status_payton(), led_id: 0, statusCode:17, systemEvent: 0xffff
Feb 13 23:32:30 c-ipaddress.hsd1.pa.comcast.net ok=0
Feb 13 23:32:50 c-ipaddress.hsd1.pa.comcast.net sysstatus_set_led_status_payton(), led_id: 0, statusCode:0, systemEvent: 0xfffe
Feb 13 23:33:06 c-ipaddress.hsd1.pa.comcast.net [0]Reg Addr Change(0) 0:0->a2e0148:6060
Feb 13 23:33:06 c-ipaddress.hsd1.pa.comcast.net [0]Reg Addr Change(0) 0:0->a2e0148:6060
Feb 13 23:33:06 c-ipaddress.hsd1.pa.comcast.net ** postupgrade handling (1, 0)
Feb 13 23:33:06 c-ipaddress.hsd1.pa.comcast.net ** postupgrade handling (1, 0)

SPA122 SIP484 response causes excessive NOTIFY event: reserve-trunk

I've noticed when the SPA122 dials a call and receives a SIP 484 "Address Incomplete" response from the call agent, the call agent plays an announcement "call cannot be completed as dialed" and then the SPA plays what sounds like a dial-tone. It's actually playing the "Prompt tone" instead of a re-order or busy signal type of tone. During the "prompt tone" the SPA is sending out extremely excessive "NOTIFY event: reserve-trunk" messages to the call agent. Within 5 seconds it had send 25x NOTIFY messages and received 25x 404 not found messages. I have never seen the event "reserve-trunk" nor has google....
I have observed this issue under the newest firmware version 1.3.1-003 and the old 1.2.1-004 release. It sure sounds like this mass amount of NOTIFY messages sent out could've added to the catatonic-ness of v1.2.1-004.
Here's the part of the call flow where I observed the behavior:
21:46:19.871105 - From Metaswitch Call Agent
<---------------------------------------------
SIP/2.0 484 Address Incomplete
Call-ID: xxxx-xxxxxxx10.11.15.24
CSeq: 102 INVITE
From: "xxxxxxxxxx" <sip:xxxxxxxxxx@callagent.
voice.com>;tag=xxxxxxxxxxxxxx
To: <sip:[email protected]>
;tag=sip+xxxxxxxxxxxxxxx
Via: SIP/2.0/UDP 10.11.15.24:5060;
received=10.11.15.24;branch=xxxxxxxxxxxx
Content-Length: 0
Supported: resource-priority
Contact: <sip:10.1.81.180:5060>
Server: DC-SIP/2.0
Organization: MetaSwitch
21:46:19.925989 - From SPA122
--------------------------------------------->
ACK sip:xxxxxxxxxx@callagent.
voice.com:5060 SIP/2.0
Via: SIP/2.0/UDP 10.11.15.24:5060;branch=xxxxx
From: "xxxxxxxxxx" <sip:xxxxxxxxxx@callagent.
voice.com>;tag=xxxxxxxxxx
To: <sip:xxxxxxxxxx@callagent.
voice.com>;tag=sip+xxxxxxxxxxxxx
Call-ID: [email protected]
CSeq: 102 ACK
Max-Forwards: 70
Authorization: Digest username="xxxxxxxxxx",re
alm="callagent.voice.com",nonce="xxxxxxxxxxxx
",uri="sip:[email protected]
:5060",algorithm=MD5,response="xxxxxxxxxxxx
",qop=auth,nc=xxxxxx,cnonce="xxxxxxx"
Contact: "xxxxxxxxxx" <sip:[email protected]
:5060;ref=xxxxxxxxxx>
User-Agent: Cisco/SPA122-1.3.1(003)
Content-Length: 0
21:46:20.225619 - From SPA122
--------------------------------------------->
NOTIFY sip:callagent.voice.com:5060
SIP/2.0
Via: SIP/2.0/UDP 10.11.15.24:5060;branch=xxxxxx
From: "xxxxxxxxxx" <sip:xxxxxxxxxx@callagent.
voice.com>;tag=xxxxxxxxxxxx
To: <sip:callagent.voice.com>
Call-ID: [email protected]
CSeq: 20699 NOTIFY
Max-Forwards: 70
Event: reserve-trunk;call-id=xxxxxxxxxxxxxxxxx
@10.11.15.24;expires=10
User-Agent: Cisco/SPA122-1.3.1(003)
Content-Length: 0
21:46:20.227915 - From Metaswitch Call Agent
<---------------------------------------------
SIP/2.0 404 Not Found
Call-ID: [email protected]
CSeq: 20699 NOTIFY
From: "xxxxxxxxxx" <sip:xxxxxxxxxx@callagent.
voice.com>;tag=xxxxxxxxxxxx
To: <sip:callagent.voice.com>;tag=sip
+1+xxxxxxxxxxxxxx
Via: SIP/2.0/UDP 10.11.15.24:5060;received=10.11.
15.24;branch=xxxxxxxxxxxxxxxxx
Content-Length: 0
Server: DC-SIP/2.0
Organization: MetaSwitch
Has anyone else noticed this? I see this as an issue because it plays the wrong tone and it sends a mass amount of messages to the Call Agent that don't really apply to anything. Why are tnese being sent at all? What does "reserve-trunk" really do? Maybe it was meant for UC540 or CME??
I have a TAC case open for this issue.
Message was edited by: George Spanos

Just for completeness - I tried to replay such scenario and I discovered that loop doesn't occur when the NOTIFY is rejected by "489 Bad event" response from PBX (it's more appropriate response for unknown events, of course, device should not flood network in any case). And/or "expires=0" in original NOTIFICATION may affect it.
Dan
<<<
SIP/2.0 484 Address incomplete
From: "6018" ;tag=8773d4554ea7044fo0
To: ;tag=as13c4f5f8
Call-ID: [email protected]
CSeq: 102 INVITE
Server: Asterisk PBX 1.8.20.1
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Reason: Q.850;cause=28
>>>
NOTIFY sip:A.B.250.1:5060 SIP/2.0
From: "6018" ;tag=d0e0a73c447c60bco0
To:
Call-ID: [email protected]
CSeq: 8816 NOTIFY
Max-Forwards: 70
Event: reserve-trunk;call-id=[email protected];expires=0
User-Agent: Cisco/SPA112-1.3.1(003)
Content-Length: 0
<<<
SIP/2.0 489 Bad event
From: "6018" ;tag=d0e0a73c447c60bco0
To: ;tag=as1965bbda
Call-ID: [email protected]
CSeq: 8816 NOTIFY
Server: Asterisk PBX 1.8.20.1
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Content-Length: 0

SPA122 FW 1.2.1 NAT-Bridge switching via IVR

Hi,
obviously the switching between bridge and NAT mode, using the IVR code 201# still isn't working in the latest firmware.
201 lets you chose between NAT (0) and bridge (1) for the yellow ethernet port - at least on the SPA-2102 and SPA-3102.
The SPA122 accepts the code (at least the friendly voice prompt lady says so) the device is then rebooting, but the setting itself remains unchanged.
Am I doing something wrong or can anyone recreate the behaviour?
Computers are like dachshounds - never do what they ought to ;-)
Eik

Option 66 is dedicated to name of TFTP server. If some CIsco devices allow full URL here, then it is non-standard extension. And undocumented, as far as I know. It is dangerous to depend on undocumented behavior.
Unfortunatelly, TFTP (only standard interpretation of option 66) offer no authentication nor encryption. It mean it can be used for provisioning of "Profile Rule" only. Separate HTTPS server is required for full provisioning then.
Options 159 and 160 are used by Cisco for "full URL" provisioning on many devices (including, for example SPA50xG phones). It's very bad news that the SPA1[12]2 doesn't support them.
HTTPS client is implemented within device already, so it's not software limitation nor computing power issue.
I would like to see support for options 159/160 (with https method allowed) on SPA1x2. Simple (e.g. no maintenance of TFTP server just for purpose of bootstrap provisioning of SPA1x2 devices, even it is easy) and unified (same system of secure bootstrap provisioning for all Cisco's SIP client devices) system reduce total cost of ownership.
Don't be confused by product specification ( http://www.cisco.com/en/US/prod/collateral/voicesw/ps6790/gatecont/ps10024/ps10029/datasheet_C78-691107.html . Yes, it mention the support of options 159 and 160, but it's not what we are speaking of here.
DHCP server within SPA122 can send those options to DHCP clients on LAN side.
But internal DHCP client doesn't ask those options from DHCP server on WAN side. Even worse - internal DHCP client will will fail at all when server inserts unsolicited option 160 to it's reply (i tried it with "https://test-provisioning.......cz/Cisco/Provisioning.php?PRVST=-2" URL, firmware 1.2.1(004) ).
Dan

Stabilité et précision mesure tension NI9205

Bonjour,
J'ai un problème de stabilité sur des mesures avec mon compactDaq et mon Ni9205
http://sine.ni.com/nips/cds/view/p/lang/fr/nid/208800
Mon soucis est que quand je fait l'acquisition d'un signal de 5V par exemple. Sur un Multimètre étalonné externe je relève bien les 5V qui varie très peu. 5.01 4.99..etc mais avec le NI9205 j'ai des variations énormes voir même des pics anormaux ! 5.32, 5.12,etc
La varation selon les calculs effectués grâce à la notice ne devrait être que de 0.004 max...
Je ne comprend pas pourquoi ma tension n'est pas stable. La source ne semble pas être en cause...
Merci pour vos lumières

Bonjour,
Quelle mode de connection utilises-tu? RSE, NRSE, Diff?? As-tu bien vérifié que la configuration de ta tâche correspondait au cablage que tu as choisi?
As-tu essayé de mettre une résistance de bias entre ta source et la masse? autour de 10 kohm?
Olivier L. | Certified LabVIEW Developer

SPA122/112 Report Rule Fw 1.3.1-003

Has anyone been able to get the SPA122/112 Report Rule function working on firmware v1.3.1-003? I just tried it and got no results. It looks like it works fine on a SPA525G2 with the same SIP notify request...
My report rule is set to:
[ --status]tftp://10.4.2.1/$MA_status.xml
On the SPA122 In the syslogs I don't see anything showing that it's sending out the report but on the SPA525G2 IP phone it's showing "
<159>Reporting current profile to server (pldlen=84050)" in the syslogs and sending out the report just fine.
Here's my notify message that works fine with the SPA525 IP phone.
"NOTIFY sip:[email protected] SIP/2.0
Via: SIP/2.0/UDP 10.11.84.22:6;rport;branch=z9hG4bK518551
From: <sip:[email protected]>;tag=21090
To: <sip:[email protected]>
Authorization: Digest username=""xxxxxxx"", realm=""xxxxxxxx"", nonce=""xxxxxxx"", uri=""sip:[email protected]"", response=""xxxxxxxxxxxx"", algorithm=MD5, qop=""auth"", nc=""00000001"", cnonce=""xxxxxxxxxxxxxxxxxxxx""
Call-ID: [email protected]
CSeq: 21 NOTIFY
Contact: <sip:[email protected]:6>
Max-Forwards: 70
User-Agent: PHP SIP
Event: report status
Content-Length: 0
Edit: I just tried this on firmware v1.2.1-004 (which by the way is a horrible release), the report rule function doesn't work either.

As far as I know, the correct event name is just 'report', not "report status".
Your's SIP NOTIFY packet should not work even with SPA525G2. Well, the syslog message "Reporting current profile ..." is suspicious somewhat.
All at all, I tried to trigger Report and it worked for me on both 1.2.1 and 1.3.1. The only difference in my configuration is the event name (as mentioned above) and the report destination. I'm using https://.../... not tftp://

SPA122 QoS doesn't work

i'm currently using my spa122 as router, the calls are always lagging, i can't understand any single word of who i'm calling.
If i'm calling and while i try to ping google.com the packet loss increases up to 80%
I've an ADSL connection with 512kbps in upload
If i set this value in qos settings the call quality is poor, while if i set it to a number bigger than 5000 the call become to be normal
Firmware Version: 1.2.1 (004) Jul 27 2012
Speedtest: http://www.speedtest.net/result/2334650222.png
What is wrong with this qos?

I have problem with QoS SPA 122 too. I have a Cable modem. Internet connection is 7 Mbs down/ 250 kbs up. SPA 122 is plugged directly into my cable modem. My PC is plugged into the SPA122 - which is working in a router mode. When I am not using internet calls are cristal clear. When internet is in use words are getting cut off or lost. Upload or transmission seems to be the biggest problem. People can not hear me well. It is worse with higher QoS upload speed settings. It somehow works betterw ith lower values (160-190) kbs- but - far from perfect. BUT - at those low settings my download speeds are getting severly restricted as well - to about 160 kbs down.
Firmware ver: 1.2.1 Jul 27 2012
What is wrong with QoS??

Stability of server, USB 2.0 devices

Hi all,
I am using an old box as a server and it appears that it has a stability problem when I connect a USB tv tuner adapter to it. I have 2 USB wireless adapters connected to the machine and hostapd is broadcasting wireless through them (one is on a 32' USB extension to provide some separation between the 2). I have a Hauppauge tv tuner which I've used on my laptop plenty of times before to record tv shows.
I have 8 USB ports in total I believe, 2 in the front which I used for diagnostics occasionally, 4 in the back for connecting most devices and 2 spares.
This is my lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 1307:0169 Transcend Information, Inc.
Bus 001 Device 003: ID 1a40:0101 TERMINUS TECHNOLOGY INC. USB-2.0 4-Port HUB
Bus 001 Device 004: ID 1307:1169 Transcend Information, Inc. TS2GJF210 JetFlash 210 2GB
Bus 001 Device 007: ID 13b1:0031 Linksys AM10 v1 802.11n [Ralink RT3072]
Bus 001 Device 005: ID 0cf3:9271 Atheros Communications, Inc. AR9271 802.11n
If the 2 wireless devices are USB 2 and the tv tuner is USB 2, will that work, or will there be issues? How many USB 2 devices can I connect to the machine? Can I connect 8?
I tried disconnecting the tv tuner adapter for the time being, as I suspect having 3 USB 2.0 devices is the culprit. I'll know in another 24 hours (not sure why it takes so long for it to suddenly die, it might be mythtv is attempting to access the device then). I only have a screenshot of the output because the system completely hangs / locks and cannot be used whatsoever.
Walter

pjg,
Did you have the same problem with your T500? I did not ever to seem to have this problem until recently. I am trying to figure out if I am missing something inside windows that would detect all of the USB components plugged into it. I don't remember having this problem with Vista. I would not think that there should be much of a difference, with respect to this issue, from Vista to 7.
I bought my machine when Vista was available and I did not notice a long lag time for USB devices, so I upgraded to 7 and I just re-installed all of the software that Lenovo puts on their machines (the preloaded factory stuff) and there was no change. I am running out of ideas to try and fix this.

Various 4G / 5G stability problems and now my iPod is USB 1.1 only!

Hi,
I bought a brand new iPod a week or two ago and it worked fine for one sync. Then the battery was running low (because I'd been using it!) so I plugged it in and iTunes synced automatically and the battery charged. after the sync I hit "eject" in iTunes so that the battery would just charge.
I returned to find that the iPod was still mounted! Very strange. I ejected again..... and it seems that what was happening was when the iPod was ejected it simply rebooted and when it came back up was mounted automatically again!
I ejected and unplugged the iPod and it was no longer stable - I would get to the menu and almost to play a song and it would reset. It seemed like my speed was the limiting factor (i.e. the iPod would only stay up for n seconds), rather than it crashing because I tried a particular function.
I saw this unstable behaviour with my old iPod (4G, firewire on this same machine) too where I had to reflash it to get it working again reliably.
So, I reflash the (new) device with the iPod Updater software downloaded for me by Software Update. It resets, and all seems well, with the rather catastrophic exception that now the iPod is only recognised as a USB 1.1 device according to System Profiler! The transfer speed is very very slow.
This is really a bit of a showstopper for my user experience. I have tried:
- Resetting my computer
- Changing the cable (I have two USB2.0 cables and 1 USB2.0/Firewire cable which I have tried all of)
- Changing USB ports (including taking ALL my USB devices away and plugging the iPod directly into the back of the desktop machine)
- Reflashing the iPod again
I have NOT tried:
- re-downloading the iPod Updater from Apple and using that (I'm downloading it now)
So.... the questions are:
- Has the firmware updater somehow made my iPod appear to be a USB1.1 device?
- Or is this a hardware fault and I need to return the iPod to be fixed?
- Is this stability problem a commonly observed one?
- If so what can I do to avoid it?
Thanks in advance,
Neil.
Powermac G4 MDD Mac OS X (10.4.7)

Cannot reproduce presumed fixed

I used #004# to deactivate my iphone 4s voice mail. How do I get it back on?

I used #004# to deactivate my iphone 4s voice mail. How do I get it back on?

contact your carrier

Apple Releases Security Update 2006-004 (PowerPC and Intel)

From Macfixit................
Apple has released Security Update 2006-004 for Mac OS X in both PowerPC and Intel versions. This update requires Mac OS X 10.4.7 for either PowerPC or Intel, Mac OS X 10.3.9 or Mac OS X 10.3.9 Server.
This is the fourth major standalone security update for Mac OS X released this year.
Update procedure recommendation First, avoid performing any other operations (in Mac OS X or third-party applications) while the update process is occurring. In addition, before installing this security update, make sure all Apple-installed applications and utilities are in their original locations. Moving one of these applications to a different location on your hard drive can lead to an incomplete update. Also, disconnect any FireWire/USB devices before applying the update (except for your startup drive, if it is FireWire or USB, and your keyboard/mouse), then re-connect the devices one by one (checking for issues created by any particular device) after the update process is complete and the system has restarted.
Enhancements in this release
Of most interest to general end-users:
a fix that prevents maliciously crafted Zip archives from causing condition where arbitrary code can be execute. In other words, prior to Security Update 2006-004 you could download a specially crafted file ending in .zip from a Web site or other location, and it could trigger the execution of malicious code.
a fix that disallows maliciously crafted Canon RAW images from creating a buffer overflow, potentially leading to arbitrary code execution. Prior to Security Update 2006-004, you could download or otherwise receive a Canon RAW file that could allow execution of malicious code on your system.
similar to the above, a fix that prevents maliciously crafted GIF images from causing an integer overflow, potentially leading to arbitrary code execution.
new download validation that will catch certain HTML files defined by Safari as "safe" that may actually contain malicious JavaScript code. After applying Security Update 2006-004, these files will not be automatically opened.
Protection against maliciously crafted HTML documents that can also open the door for arbitrary code execution by accessing deallocated objects.
A full list of enhancements is as follows:
AFP Server
An issue in the AFP server allows search results to include files and folders for which the user performing the search has no access. This may lead to information disclosure if the names themselves are sensitive information. If the permissions of the items allow it, the contents may also be accessible. This update addresses the issue in Mac OS X v10.3.9 by ensuring that search results only include items for which the user is authorized. For Mac OS X v10.4 systems, the issue was addressed in Mac OS X v10.4.7. Available for: Mac OS X v10.3.9, Mac OS X Server v10.3.9:
The AFP server contains an integer overflow that can be triggered by an authenticated user. A malicious user with access to the AFP server may be able to cause a denial of service attack or arbitrary code execution with system privileges. The AFP server is not enabled by default on Mac OS X. This update addresses the issue by performing additional validation. Credit to Dino Dai Zovi of Matasano Security for reporting this issue. Available for: Mac OS X v10.3.9, Mac OS X Server v10.3.9, Mac OS X v10.4.7, Mac OS X Server v10.4.7.
On Mac OS X Server, the AFP server supports reconnection of file sharing sessions after a network outage. The storage of reconnect keys is world-readable. It may be possible for an authenticated local user to read the reconnect keys, use them to impersonate another user over AFP, and access files or folders with the privileges of the impersonated user. This update addresses the issue by protecting the reconnect keys with appropriate file system permissions. This issue only affects Mac OS X Server. Available for: Mac OS X Server v10.3.9, Mac OS X Server v10.4.7.
An unchecked error condition exists in the AFP server that may lead to a crash. By carefully crafting an invalid AFP request, an attacker may be able to trigger this condition and cause a denial of service. This update addresses the issue by handling the formerly unchecked error condition. Available for: Mac OS X v10.3.9, Mac OS X Server v10.3.9, Mac OS X v10.4.7, Mac OS X Server v10.4.7
Bluetooth
The security of the Bluetooth Setup Assistant has been improved in this update for Mac OS X v10.4.7. The length of the automatically generated passkey used for pairing has been increased from six characters to eight characters. Available for: Mac OS X v10.4.7, Mac OS X Server v10.4.7
Bom
An issue in Bom's compression state handling may cause heap corruption. By carefully crafting a corrupt Zip archive and persuading a victim to open it, an attacker may be able to trigger this condition which could lead to an application crash or arbitrary code execution. Note that Safari will automatically open archives when "Open `safe' files after downloading" is enabled. This update addresses the issue by properly handling such malformed Zip archives. Credit to Tom Ferris of Security-Protocols.com for reporting this issue. Available for: Mac OS X v10.3.9, Mac OS X Server v10.3.9, Mac OS X v10.4.7, Mac OS X Server v10.4.7.
DHCP
A stack buffer overflow exists in bootpd's request processing. By carefully crafting a malicious BOOTP request, a remote attacker may be able to trigger the overflow and cause arbitrary code execution with the privileges of the system. Note that bootpd is not enabled by default in Mac OS X, and must be manually configured in order to be enabled. This update addresses the issue by performing additional bounds checking. Available for: Mac OS X v10.3.9, Mac OS X Server v10.3.9, Mac OS X v10.4.7, Mac OS X Server v10.4.7.
dyld
Malicious local system users may specify dynamic linker options that cause output to standard error. This output contains informational content and potentially user-specified content. As a result, privileged applications that parse or reuse standard error may be influenced inappropriately. This update addresses the issue by ignoring the problematic dynamic linker options in privileged applications. Credit to Neil Archibald of Suresec LTD for reporting this issue. Available for: Mac OS X v10.3.9, Mac OS X Server v10.3.9, Mac OS X v10.4.7, Mac OS X Server v10.4.7.
An improperly handled condition in the dynamic linker may lead to including dangerous paths when searching for libraries to load into privileged applications. As a result, malicious local users may cause the dynamic linker to load and execute arbitrary code with elevated privileges. This update addresses the issue by properly selecting search paths when executing privileged applications. Credit to Neil Archibald of Suresec LTD for reporting this issue. Available for: Mac OS X v10.4.7, Mac OS X Server v10.4.7
fetchmail
Several issues in the fetchmail utility were discovered. The most serious issue could lead to arbitrary code execution when fetching mail from a malicious POP3 mail server. All issues are described at the fetchmail website (fetchmail.berlios.de). This update addresses the issues by updating fetchmail to version 6.3.4. In addition, fetchmail is no longer distributed as a privileged utility. Available for: Mac OS X v10.3.9, Mac OS X Server v10.3.9, Mac OS X v10.4.7, Mac OS X Server v10.4.7.
gunzip
A race condition may allow a malicious local user to modify the permissions of files owned by another user executing gunzip. This issue is only exploitable when executing gunzip on files in directories that are modifiable by other users. This update addresses the issue by properly handling files while decompressing. Available for: Mac OS X v10.3.9, Mac OS X Server v10.3.9, Mac OS X v10.4.7, Mac OS X Server v10.4.7.
A directory traversal vulnerability is present in the command line utility gunzip when it is used with the non-default "-N" option. By carefully crafting a malicious compressed file and persuading a user to open it with "gunzip -N", an attacker may replace or create arbitrary files with the privileges of the victim. This update addresses the issue by properly stripping paths from files when decompressing. Available for: Mac OS X v10.3.9, Mac OS X Server v10.3.9, Mac OS X v10.4.7, Mac OS X Server v10.4.7
Image RAW
By carefully crafting a corrupt Canon RAW image, an attacker can trigger a buffer overflow which may lead to an application crash or arbitrary code execution. This update addresses the issue by performing additional validation of Canon RAW images. This issue does not affect systems prior to Mac OS X v10.4. Available for: Mac OS X v10.4.7, Mac OS X Server v10.4.7.
ImageIO
By carefully crafting a corrupt Radiance image, an attacker can trigger an integer overflow which may lead to an application crash or arbitrary code execution. This update addresses the issue by performing additional validation of Radiance images. This issue does not affect systems prior to Mac OS X v10.4. Available for: Mac OS X v10.4.7, Mac OS X Server v10.4.7
By carefully crafting a corrupt GIF image, an attacker can trigger an undetected memory allocation failure which may lead to an application crash or arbitrary code execution. This update addresses the issue by performing additional validation of GIF images. This issue does not affect systems prior to Mac OS X v10.4. Available for: Mac OS X v10.4.7, Mac OS X Server v10.4.7.
By carefully crafting a corrupt GIF image, an attacker can trigger an integer overflow which may lead to an application crash or arbitrary code execution. This update addresses the issue by performing additional validation of GIF images. This issue does not affect systems prior to Mac OS X v10.4. Credit to Tom Ferris of Security-Protocols.com for reporting this issue. Available for: Mac OS X v10.4.7, Mac OS X Server v10.4.7
LaunchServices
Download Validation may erroneously identify certain files containing HTML as "safe". If such a file is downloaded in Safari and Safari's "Open `safe' files after downloading" option is enabled, the HTML document will automatically be opened from a local URI. This would allow any JavaScript code embedded in the document to bypass access restrictions normally imposed on remote content. This update provides additional checks to identify potentially malicious file types so that they are not automatically opened. This issue does not affect systems prior to Mac OS X v10.4. Available for: Mac OS X v10.4.7, Mac OS X Server v10.4.7
OpenSSH
Attempting to log in to an OpenSSH server ("Remote Login") using a nonexistent account causes the authentication process to hang. An attacker can exploit this behavior to detect the existence of a particular account. A large number of such attempts may lead to a denial of service. This update addresses the issue by properly handling attempted logins by nonexistent users. This issue does not affect systems prior to Mac OS X v10.4. Credit to Rob Middleton of the Centenary Institute (Sydney, Australia) for reporting this issue. Available for: Mac OS X v10.4.7, Mac OS X Server v10.4.7
telnet
When connected to a TELNET server, the client may send the contents of arbitrary environment variables to the server if the server requests them. Some environment variables may contain sensitive information that should not be sent over the network. This update addresses the issue by ensuring that only non-sensitive variables and variables that the user has explicitly requested are are shared with the server. Credit to Gael Delalleau and iDEFENSE for reporting this issue. Available for: Mac OS X v10.3.9, Mac OS X Server v10.3.9, Mac OS X v10.4.7, Mac OS X Server v10.4.7.
WebKit
A maliciously-crafted HTML document could cause a previously deallocated object to be accessed. This may lead to an application crash or arbitrary code execution. This update addresses the issue by properly handling such documents. Credit to Jesse Ruderman of Mozilla Corporation for reporting this issue. Available for: Mac OS X v10.3.9, Mac OS X Server v10.3.9, Mac OS X v10.4.7, Mac OS X Server v10.4.7
AppKit, ImageIO
Buffer overflows were discovered in TIFF tag handling (CVE-2006-3459, CVE-2006-3465), the TIFF PixarLog decoder (CVE-2006-3461), and the TIFF NeXT RLE decoder (CVE-2006-3462). By carefully crafting a corrupt TIFF image, an attacker can trigger a buffer overflow which may lead to an application crash or arbitrary code execution. This update addresses the issue by performing additional validation of TIFF images. Systems prior to Mac OS X v10.4 are affected only by the TIFF NeXT RLE decoder issue (CVE-2006-3462). Credit to Tavis Ormandy, Google Security Team for reporting this issue. Available for: Mac OS X v10.3.9, Mac OS X Server v10.3.9, Mac OS X v10.4.7, Mac OS X Server v10.4.7./

Right after installing Security Update 2006-004 (Intel) on my macbook pro I am having troubles with my wireless connectivity. Here is the dump from the console:
Aug 3 15:49:43 x-ray /System/Library/PrivateFrameworks/Apple80211.framework/Resources/airport: Error: WirelessAssociate2() = 88001006 for network RadioActive
Aug 3 15:49:43 x-ray /System/Library/PrivateFrameworks/Apple80211.framework/Resources/airport: Error: (had password)
Aug 3 15:49:51 x-ray /System/Library/PrivateFrameworks/Apple80211.framework/Resources/airport: Error: WirelessAssociate2() = 88001006 for network RadioActive
Aug 3 15:49:51 x-ray /System/Library/PrivateFrameworks/Apple80211.framework/Resources/airport: Error: (had password)
Aug 3 15:49:59 x-ray /System/Library/PrivateFrameworks/Apple80211.framework/Resources/airport: Error: WirelessAssociate2() = 88001006 for network RadioActive
Aug 3 15:49:59 x-ray /System/Library/PrivateFrameworks/Apple80211.framework/Resources/airport: Error: (had password)
I can reboot and it will work, but if I put my macbook to sleep it, when I wake it, it will do the same thing again.
I am also getting timeouts waiting for results of 1st wireless scan to complete in console.
Anyone else having this issue?
MBP15-2GHZ Mac OS X (10.4.7)

Problems with n8-response time , stability and use...

ive been using n8 for a couple of months now and some times i really think this can do better
the text editor for messages has the keyboard options just bellow space. i so want that to change because space is a very frequently hit and if i type fast then almost always end up getting the keyboard changed to qwerty .i use alpha numeric off course but why cant this be the same as the s60 one....used to work great on my 5800
2nd the response gets annoyingly slow if i hit the applications folder
and again by instinct i end up pressing it double and entering the video editor. i know it can be optimized and would love to see it in the update cause its a matter of quick response. applications and folders should open quick and stability still needs work after the 2 minor updates nokia gave
3rd its not stable. some times the notification widget stops notifying although there have been missed events. the WLAN connection widget is bonkers , i was at home and it was showing connection to my uni's AP which is miles away. and it has a mind of its own. also the connection is some how suspended and pages just wont open,same in the case of ovi store. Nokia need to fix that
if nokia just work on the interface so the fone just flows with fingers then its a damn good fone. im having issues but dont want to let go of it
camera is great but the interface needs work
symbian3 is new and the is room for a lot of improvment

the N8 is a great phone and I'm happy whit it but I must agree with the 2nd part....the respons is sometimes really slow but not painfully and it's really not that offten..
and I fully agree what you said about camera interface, the camera itself is a great, picures are great in the dark sometimes can be better but the interface is not that good and the cameraphone as N8 shuld have a interface that match camera
sorry but bad english

SPA122 Fw 1.2.1-004 Stability

Similar Messages

Maybe you are looking for