SPA-3000 sends DTMF 23 instead of # to gw0 (FXO/PSTN) since 3.1.20(GW)

Unanswered Question
Jul 11th, 2009
User Badges:

The SPA-3000 after upgrading from firmware 3.1.18 to 3.1.20 can no longer send a DTMF # tone out its gw0 port: It instead incorrectly replaces any # characters in the dial string with the numbers 2, 3.


I would appreciate if someone on this forum could report this to development as a bug.


This problem was introduced into 3.1.20 as a side effect of the following bug fix documented in the 3.1.20 release notes: "SPA should escape occurrences of '#' in the dial string with %23 in outbound INVITE".


23 is the hexadecimal ASCII code for #, and if a dialled # sign is to become part of a SIP INVITE it is appropriate to escape it, but if it is to be re-dialled still as DTMF by the SPA to the PSTN or whatever is connected to its gw0/FXO port, it is A MAJOR BUG to escape it.


As a workaround I've downgraded back to 3.1.18 which is still available at: http://www.linksys.com/servlet/Satellite?c=L_CASupport_C2&childpagename=US%2FLayout&cid=1169083367861&packedargs=sku%3DSPA3000&pagename=Linksys%2FCommon%2FVisitorWrapper&lid=6786167861B01&displaypage=download#versiondetail


Steps to reproduce:


1) Connect the gw0/FXO port of the SPA to the PSTN

2) Set the Line 1 Dial Plan to something that allows dialing # such as:

    [0-9*#].<:@gw0>

    (The above allows any sequence of one or more standard DTMF digits to be dialled, and they are all supposed to get passed through verbatim to gw0.)

3) Dial someting with a # such as 1 #9 643 6400

4) Notice how the SPA incorrectly dials 1 239 643 6400 (which happens to go to CableUSA in Naples, FL)

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Alberto Montilla Mon, 07/13/2009 - 07:23
User Badges:
  • Cisco Employee,

Dear Sir;


Thanks for the information. Actually SPA3000 is end of sale, so no further development on this. My suggestion is that you keep using 3.1.18.


Regards
Alberto

pwestess Mon, 07/13/2009 - 14:04
User Badges:

Got a bunch of these in 2007... was hoping they wouldn't be bricked already. Nice device most of the time. If I were in product management and found out that one of the former flagship products has a silly little software bug that actually breaks on of the buttons on the attached phone, I'd see if there wasn't something that could be done about it. You know, it may affect how confident a potential customer would be investing in another product from that supplier...


Anyway, anyone know of an analog telephone to SIP adapter with POTS fall-back out there that supports all buttons on the attached phone? No router needed, just an ATA. But all of 0-9, * and # has to work whether operating in SIP or POTS mode.


For now I am indeed using 3.1.18 on the SPA-3000 boxes as a stop-gap, but 3.1.18 cannot send a proper # "tone" in a SIP invite (as %23). 3.1.20 can do that at the expense of not being able to send a # code as DTMF.

Patrick Born Mon, 07/13/2009 - 14:48
User Badges:
  • Cisco Employee,

Hi pwestess,


You make a good point. I've forwarded your comments to the product management team so that they are aware of the issues.


Regards,



Patrick

-----------

Hello .. this problem was solved ?, because currently I have the same problem.

I have the following scenario:

Panasonic PBX (analog extension port) <=====> SPA3102 <===== LAN ===== > SPA112 <=====> Phone

I can make and receive calls to PBX extensions, but when I try to take the PSTN and dial 49xxxx# 9 and then the phone number, the Panasonic PBX don´t make de call to the PSTN because the SPA sends 49<passwod>239 <phone number>.

Dan Lukes Wed, 01/21/2015 - 15:48
User Badges:
  • Red, 2250 points or more
  • Cisco Designated VIP,

    2017 Small Business

Cisco experts like amontill or Patrick Born are no longer responding here. You should call SMB support for help. But don't put so much hope on it even if you have valid support contract.

Actions

This Discussion