Fred Thompson wrote:I had (obviously incorrectly) concluded that the modem FXS port behaved exactly as a PSTN line.
Nope - Most Internet Telephone Service Providers don't even configure their devices with the correct UK parameters (Vonage springs to mind) let alone follow a set standard. Configuration varies from provider to provider! If Vodafone have altered the default gain settings on their hardware then you need to compensate for that on the Cisco SPA232D.
If one is using a UK PSTN line, then in almost all cases the following configuration will work just fine...
Both FXS Port Input Gain
and FXS Port Output Gain
is almost always 0
. I almost never need to change these!
SPA To PSTN Gain
and PSTN To SPA Gain
, I leave both set at their default settings which is 0
These should be good too:
- Voice > Regional > Control Timer Values (sec)
- Hook Flash Timer Min: .06
- Hook Flash Timer Max: .2
- Interdigit Long Timer: 6
- CPC Duration: .09
- Voice > Regional > Miscellaneous
- FXS Port Impedance: 370+620||310nF (or 270+750||150nF )
- FXS Port Input Gain: 0
- FXS Port Output Gain: 0
- Caller ID Method: ETSI FSK With PR(UK)
- Caller ID FSK Standard: v.23
- Voice > PSTN > PSTN Disconnect Detection
- Detect CPC: yes
- Detect Polarity Reversal: no
- Detect PSTN Long Silence: yes
- PSTN Long Silence Duration: 30
- PSTN Silence Threshold: High
- Min CPC Duration: 0.09
- Detect Disconnect Tone: yes
- Disconnect Tone: 400@-30,400@-30; 2(3/0/1+2)
- Voice > PSTN > International Settings
- FXO Country settings: UK
- Ring Validation Time: 256ms
- Ring Indication Delay: 512ms
- Ring Timeout: 640ms
If it was me, I would be looking at both the Gain
and DTMF Tx Method
settings. Without knowing what the Vodafone ATA is configured to use it will be a case of trial and error unfortunately! After all, It wouldn't be a delay issue otherwise you would be missing numbers and not gaining some, and it won't be a line noise issue either. Oh, It might be worth looking at the Obihai UK settings too as they are almost identical to the Cisco hardware (same people made them).
What's interesting is that the poster in the link I provided above had an identical issue to yourself. They said that they replaced the SPA232D, tried a different handset and yet still the issue persisted. That makes me wonder if there is a bug in the firmware... Are you using the latest firmware? If you do have the latest firmware, maybe try a lower revision and see if the problem goes away?