Cisco SPA302D Wireless Handsets will not register to Cisco SPA232D

[fattmarrell]

Hello Community,

This is my first time working with these devices, I picked up the kit that included the SPA232D ATA adapter as well as a SPA302D wireless handset, as well as two additional SPA302D wireless handsets. I've configured the ATA per the instructions, even got my extensions communicating/registered with my SIP provider, but can't for the life of me get the handsets to pair/register to the ATA. I've searched as much as possible and can't find much help on it either.

The instructions state by default that the PIN is blank, and I even tried others to force an incorrect PIN error - still nothing as if the phones don't see the ATA at all. I am holding the pairing button for 7 seconds for it to begin blinking. I have not tried downstepping the firmware yet, because I'm affraid to run into other issues that others seem to have been having with previous versions.

I'm running SPA232D ATA Adapter Firmware: 1.3.5 (004_267) Jul 31 2014

I'm running SPA302D Handset Software Version: 2.50

Does anyone have any recommendation at all what I could be missing; maybe a setting in the ATA? Any help would be most grateful.

Thanks in advance,

[Dan Lukes]

I'm running SPA232D ATA Adapter Firmware: 1.3.5 (004_267) Jul 31 2014
I'm running SPA302D Handset Software Version: 2.50

Firmware versions of SPA232D and SPA302D are out of sync. It may cause a issue.

Downgrade SPA232D to ?.?.?(???_250) firmware, pair headset, then upgrade both.

But to say true. I never had problem to pair handset with base station. I did no special configuration. It just worked.

[NN HH]

Hi

I purchased 3 SPA302 phones plus SPA232 DECT ATA...

The documentation is hopeless. I am running 1.3.5 firmware on the ATA and have never updated the handsets as have never been able to even receive a call through the cordless handsets!!!

Q: How do you update ONLY the SPA302 phone firmware??

Q: Can you downgrade the firmware afterwards on SPA232? and on SPA302?

Q: Which firmware is most reliable???

Furthermore, I find the SPA232D needs to be rebooted every 1 to 2 days. I have an Asus RT-AC66u router and the same issue occurs on other networking equip for family and clients, e.g. Netcomm ADSL NB6xxx and Dlink, etc.

Could someone please help me with the cordless phones AND share their hints and tips to configure the SPA232 so that it is as Rock-Solid as my old SPA3102.

Perhaps someone could please share their device config?? (without user/pass and VOIP user/pass)

Thank you! Thank you!

[Dan Lukes]

How do you update ONLY the SPA302 phone firmware??

SPA302 firmware must follow SPA232D firmware. It mean SPA302 must be updated whenever SPA232D is updated. SPA302 can be updated from SPA232D only.

Can you downgrade the firmware afterwards on SPA232? and on SPA302?

Firmware downgrade is unsupported procedure unless you has been commanded to do it by Cisco SMB Support Center. It is possible most of time, but you are on your own.

Based on my experience, it's better to have device in factory-default configuration before downgrade.

Which firmware is most reliable???

The latest.

Could someone please help me with the cordless phones AND share their hints and tips to configure the SPA232 so that it is as Rock-Solid as my old SPA3102.

No way. Current SMB ATA product line is not as good as former Linksys devices. SPA112 is not as good as PAP2T. SPA3102 is not as good as SPA232D (moreover the SPA232D has been discontinued). Linksys has maintained their product with closed cooperation with customers and their support staff has been skilled. Cisco SMB developers never speak with customers and their support center staff doesn't understand even the technology basics.

Perhaps someone could please share their device config?? (without user/pass and VOIP user/pass)

Use the same configuration you has used for SPA3102 (of course it doesn't cover the DECT configuration part).

[NN HH]

Dan you are a champion. I was expecting to wait 7 days for a response! :)

Thumbs up mate! Really appreciate it.

It is fantastic to see someone so knowledgeable on these forums, willing to share their knowledge. I totally agree, there seems to be a lack of knowledge available on these devices. Is it just me or are Cisco holding their cards to their chest?  I sort of wish I had not gotten rid of the SPA3's and SPA5 handsets - despite being EOL/discontinued they operated fine!

So on my own with downgrades... does that mean permanent or just temporary issues on downgraded F/W version?

"SPA3102 is not as good as SPA232D" - I think you mean the other way around. Yes 232 discontinued like 90% of the Linksys/Cisco range of devices. Yet they still manufacture and sell them through their channel resellers!!!

Don't have the SPA3102's any more. That was Jan 2016 when they all went to charity.

Firmware

SPA232D & SPA302D Firmware must be the same version. View firmware of phone via handset. Restore factory defaults and then upgrade/downgrade ATA to same version as handset. v1.41 I believe is latest...

Ta.

Can I share the XML file here and if you (or anyone else) have 5mins can look and see if any settings are *glaringly* obvious and should be changed? Or anything to be changed on the Router? Have you noticed that the Cisco Backup facility does not restore 100% of the settings? Maybe a 1.3.5 firmware issue...

Note: The reason I reset my device was that it suddenly stopped being web accessible. One week it just stopped and I've been crippled for weeks... Device was password protected so makes no sense!

e.g. One topic of heated argument at my work is around the the two NAT drop-downs fields under the Line(s). Whether they should be left disabled or both/one be enabled, etcetera...  Plus whether to use the 2 x "Handle via" and 2 x "Insert via" drop-downs.  Enable STUN?  Use DNS SRV / DNS SRV Auto Prefix?  Enable Symmetric RTP? etc... etc...

I use SIP Sorcery as my central SIP registration point, which allows me access to all my other VSPs from any device and calls are routed via lowest cost VSP or can be overridden via DTMF short-cuts. It is a *brilliant* service. 4 VSPs and over a dozen SIP accounts configured.

Really look forward to any feedback! Also happy to share and document my successful device config to help others.

Ciao!

[Dan Lukes]

SPA[35]xx are not EoL yet.

1.4.1 is the latest, the 2.82 firmware for SPA302 is embedded inside.

I never used embedded configuration backup function thus I have no experience with it. We configure devices from XML style provisioning file. We can re-load it anytime, so we have no reason to backup device's configuration.

Disclose your saved XML configuration (file name must have .txt, not .xml or you will not be allowed to attach it here), we will look at it, but don't expect so much. I have little experience with SPA232D - I have the one for testing purposes, but based on results we considered not to deploy it to production.

According Handle via" / "Insert via" - it depends on overall network topology as well as SIP proxy requirements (I'm not familiar with SIP Sorcery equipment). As generic advise (it apply to all settings) - if it work, don't change it from defaults.

[NN HH]

Thanks mate.

Weird. I have read several places now that SPA232D is EOL and there are still no products to replace its functionality. They are very hard to buy and source these days. Few resellers keep stock, as to retailers. This is down-under of course. May well be different elsewhere. SPA112 and SPA122 are widely available.

SipSorcery recommend to only configure the codec, SIP server and authentication. So no requirements on their side (e.g. Auth ID or Outbound Proxy etc)

Yes, provisioning is something I'd like to set-up from scratch. We have the DHCP option configured on the primary vlan. The only annoying thing is that test devices get wiped :P

.

Network: ADSL2+ >> Asus RT-AC66u, 2 x SPA901, SPA52x, 2 x YeaLink T46G, 1 x SPA232D + 3 SPA302D. However SPA52x and YeaLink handsets disconnected for simplicity. Then several computers and phones not running any services.

Peculiarities with SPA232's: Another strange thing about SPA232D. Three times now, I have not been able to receive calls. I've racked my brains, annoyed support and then found a cfwd destination in the User 1. WTF? So three times it has had a different number in the CFWD All - Croatia, somewhere and somewhere else in EU... Very strange!

Device Configuration:

Password isn't visible in XMLs - stripped DID. (/admin/config.xml or spacfg.xml)

I also have a QOS on the SPA232 with upstream reservation of 1000kbps (ADSL 1200kbps max) when phone in use. Disabling doesn't seem to make any difference. I guess that's the Router then.

.

Thanks again for your time. Let me know if you need any help with anything.

p.s. do you also find the SPA232 devices incredibly slow compared to the Linksys devices? It is excruciating waiting for page loads or reboots...

Cheers mate,

[Dan Lukes]

I'm unsure the Cisco have plans to produce a replacement. The EoL statement claim SPA122 to be replacement which is just lie. SPA122 have neither FXO port nor DECT interface.

Three times now, I have not been able to receive calls. I've racked my brains, annoyed support and then found a cfwd destination in the User 1. WTF? So three times it has had a different number in the CFWD All - Croatia, somewhere and somewhere else in EU... Very strange!

Unless authorized user has configured it, then it's unauthorized change. Note no SPA* device is hardened enough to be exposed to public Internet. Make sure no remote access from unauthorized sources is possible - intrusion is imminent otherwise.

do you also find the SPA232 devices incredibly slow compared to the Linksys devices? It is excruciating waiting for page loads or reboots

I assume it's because HTTPS access use larger keys, SHA instead of RC4 - in short - it's caused by cryptography. It require a lot of computing. Remember the primary device's goal is to serve calls, not to respond to your's browser requests.

spa232d_v1.3.5_2016.06.12_-_configured_2016.04.xx_settings_public.xml_.txt

After just quick review I found nothing wrong nor suspicious with your config. I have the only advice for you - RTP_Packet_Size=0.040 is neither default nor good choice. The most common public phone networks are using 0.020, so you should follow it to avoid transcoding. It may lower call quality.

[NN HH]

Hmm might have to see if SIP.ALG is enabled on the router after recent wipe and F/W upgrade. Plus upgrade device to v1.4.x

SPA302D:

S/W Version: v2.40 (Latest v2.6.7)

HID VID: v2.1.1 V01

.

How can you have the SPA302D on the same F/W version as ATA?  The SPA302's just upgrade over the internet via the handset interface and are v2+. Unless 2.4x = 1.4x?

[Dan Lukes]

Not "numerically same". Every casual SPA232D firmware have SPA302D firmware embedded inside. The SPA302D paired with particular SPA232D should run exactly this firmware.

According 20ms/40ms ptime - you are true. But there are also other factors you should take into consideration:

1. it's better to use same configuration for both directions of audio. ptime is fixed most of time on provider side, so you should consider to use the same value. I assume you provider is using 20ms on G.711a codec.

2. Maximum end-to-end (it mean mouth-to-ear) delay for standard quality call is 100ms. If you spend 40ms waiting for complete packet data, it's almost impossible to fulfill end-to-end delay requirements, thus it's not recommended configuration. Well, delay up to 500ms is considered acceptable for low quality long distance calls - so 40ms may be suitable for low bandwidth lines where low quality call is expected already.

3. Just stability issue - G.711a/20ms is most common configuration thus its well tested. 

[NN HH]

Great. just lost everything I wrote. Ctrl Shift-W instead of Ctrl-W in another tab! :P

So from what I understand of packet timing (ptime), 30ms (default) is stupid as I think has compatibility issues (or results in excessive traffic/data and not ideal for some Codecs. So real-world values would be:

• G711 at 0.040 / 40ms packet size time is approx. ~70 - 79 KB/s (inc. encapsulation and headers) and approx. ~25 larger packets per second (more efficient network connections)... Thus susceptible to higher latency and suffer from dropped  voice packets (more data in each packet).
• G711 at 0.020 / 20ms packet size time is approx. ~85 - 95 KB/s (inc. encapsulation and headers) and approx. ~50 smaller packets per second (higher load network connections).. Thus lower latency and less likely to suffer from dropped voice packets (less data in each packet).

40ms packet time results in larger packets, more efficient network connection utilisation due to lower packet overhead and encapsulation.  However, 20ms packet timing results in smaller packets, therefore lower latency and between callers. .. .. ... I think?

So they both have their advantages. i.e. 20ms if there are multiple Voice devices on a network transmitting data. 40ms if only one Voice device on the network.

I use Beyond Compare and Araxis Merge for comparison. Two invaluable purchases to compare files and changes.
I disabled HTTPS and updated ptime to 20ms on the device... Thanks for your time and feedback!  

Ta.

.

For example:

• G729 call with payload of 20 Bytes (0.020 / 20 ms) = (8 bits x 50 packets/s) x (40 bytes of I.P. headers [or UDP/RTP] + 20Byte payload) = 24 Kbps

• G729 call with payload of 40 Bytes (0.040 / 40 ms) = (8 bits x 25 packets/s) x (40 bytes of I.P headers [or UDP/RTP] + 40 Byte payload) =  16 Kbps

.

So 8 x 50 = 400 x (40 + 20) =  .... 24,000 Bytes = 24 KB per Sec if you use 0.020.  or (8 x 25) x (40 + 40) = ... 16,000 = 16 KB per sec bandwidth on 0.040.

So yeah... Packet size / PTime determines the delay and bandwidth required for calls.

0.020 for high bandwidth LAN VOIP devices. 0.040 for mobile / low bandwidth VOIP devices.

[NN HH]

I am glad you said G711a as everyone seems to just say G711u. However I always first enable allow remote codec when testing or checking for issues. Every VSP has a different default.

Q: Do you recommend using RTP port range as only 16384 to 16482?  Or would you increase this range to a max of 30,000?

Q: Do you know how to use the additional Gateway Accounts under Line 1?

 .

Connected handsets again, replaced batteries with new AAA's. But I cannot get outbound nor inbound routed calls.  Jsut "Error L128". Check boxes are all ticked for Handset 1-5 under Quick Setup... Under PSTN "Incoming Handset List" i've entered "fxs,1,2,3,4,5".

I am unsure what needs to be put under DECT 1, 2, 3, .... Seems pointless having to configure more SIP accounts when I have over 10 SIP accounts connected via Line 1.

 .

 .

Further CODEC information... I wish the SPA232 supported G722, G723 and G726. Thanks Cisco!

CODEC	Audio Quality	CPU Req.	Base Rate	Total inc. Padding
G711	Good	Very Low	64 KB/s	95 to 106 KB/s
G722	Very Good	Low	64 KB/s	95 KB/s
GSM	Average	Average	13 KB/s	44 to 46 KB/s
G729	Low	Very High	8 KB/s	39 to 42 KB/s

This is with 20ms / 0.020 packet timing.

Overhead padding consists of RTP, Ethernet, IP and UDP equal to approx. ~31KB/s.  These are:

- RTP: ~5KB/s;

- Ethernet: ~15KB/s;

- IP: ~8KB/s; and

- UDP: ~3KB/s.

I am not sure how they differ when over TLS or TCP, similar I am sure...

Good article on 3CX's site somewhere for VOIP over PPPoA xDSL connections. If comparing to PPPoE, it is approx. 5-8% "heavier".  Found the article: http://www.3cx.com/blog/docs/bandwidth-dsl-atm-isp/

.

Gezus, after all these DECT phone issues, I feel like a triple Panasonic phone set plus SPA3102 would be more reliable!!!  Cisco! What are you guys doing???

[Dan Lukes]

G.711u is basic codec for Japan and USA (+ some territories). G.711a is basic codec for rest of world. Its also default codec for international trunks.

I cannot get outbound nor inbound routed calls.  Jsut "Error L128". Check boxes are all ticked for Handset 1-5 under Quick Setup... Under PSTN "Incoming Handset List" i've entered "fxs,1,2,3,4,5".

Well, I have limited experience with SPA232D - I have just one SPA302D and I used the device for test only,  no production deployment.

Turn on voice module syslog&debug (highest level) and catch them. It may reveal the cause.

I am unsure what needs to be put under DECT 1, 2, 3, .... Seems pointless having to configure more SIP accounts when I have over 10 SIP accounts connected via Line 1.

I'm unsure I understand. What you mean 'X SIP accounts via Line 1" ?

Note the SPA232D is not PBX. It's just POTS or DECT <-> SIP gateway.

[NN HH]

Hi Dan,

Under "PSTN" (fall back) and "DECT1", 2, 3, 4, 5, 6 ....., there is authentication and SIP Server fields. DECT phones should have some sort of option to tell them which account to use for Auth and calls. However you can only choose from 1 to 8 for example. Nothing like "fxs".

These correspond with the DECT lines and not the Line 1 (FXS) or PSTN (GW0).

PSTN phone line = Offers fallback capability if internet is offline. GW0 is the POTS or PSTN - whatever you want to call it.  Also it offers the ability to receive calls on a PSTN telephone number you may wish to receive calls on.

So SPA232D offers consolidation of handsets. Not having to have separate PSTN phones. Dial #0 to make call via FXO/GW0 PSTN or dial normally for FXS.

Then SIP phone line = VoIP call functionality when Internet is online. It has the SIP authentication and SIP server. So I configure SIP Sorcery there. And on the SIP Sorcery server, I have 10+ SIP accounts, so i can have all DID's enter via 1 registration and have rules based on numbers dialed depend on which VSP to dial out with.

This is how the device is configured:

So the 1,2,3,... are the DECT choices. Under PSTN (normally Phone 1) for (FXO/PSTN/Fallback - I have " Incoming Handset List: " with: fxs,1,2,3,4,5

Dial plan for Line 1 (Voip) is:

(<#0,:>xxx.S3<:@gw0>|<#1,:>xxx.S3<:@gw1>|<#2,:>xxx.S3<:@gw2>|12[34]!|190[02]!|x[*#x][*#x]xx.S0|[*#]xx.|xxx.S4)

...

Does that make more sense?

Appreciate your time mate!

[Dan Lukes]

@gw0 trick seems to work - I tried it in the past.

But if I remember correctly, it's undocumented behavior (for this model) so such feature may be removed anytime.