Oct 6, 2010 Upgrade-Related Bugs
-
- Just Passing Thru
- Posts: 14
- Joined: 06/06/2010
- SIP Device Name: PAP2T NA
- Firmware Version: 5.1.6
- ISP Name: Rogers Cable
- Computer OS: Windows 7, XP, Ubuntu 10
- Router: Asus Rt-N16 (DDWRT)
Re: Oct 6, 2010 Upgrade-Related Bugs
Hows the Vm notification comming along
we have not seen any status updates
please advise
we have not seen any status updates
please advise
-
- *Go-To Guy*
- Posts: 532
- Joined: 08/06/2010
- SIP Device Name: Grandstream HT-502
- Firmware Version: 1.0.1.63
- ISP Name: DSL TekSavvy
- Computer OS: OSX Snow Leopard
- Router: Linksys WRT54GL w/tomato
Re: Oct 6, 2010 Upgrade-Related Bugs
Yes they did post an update, they're working on it. No ETA at the moment.
-
- Quiet One
- Posts: 27
- Joined: 06/23/2010
Re: Oct 6, 2010 Upgrade-Related Bugs
Does anyone at FPL have anything to say about my DTMF bug report?
-
- Just Passing Thru
- Posts: 14
- Joined: 06/06/2010
- SIP Device Name: PAP2T NA
- Firmware Version: 5.1.6
- ISP Name: Rogers Cable
- Computer OS: Windows 7, XP, Ubuntu 10
- Router: Asus Rt-N16 (DDWRT)
Re: Oct 6, 2010 Upgrade-Related Bugs
laurent wrote:Yes they did post an update, they're working on it. No ETA at the moment.
where did they post the update
i have been following this thread and so for only 1 post that says nothing more than they acknowlege the issue and are looking in to it
is there a new thread i can follow
-
- Just Passing Thru
- Posts: 3
- Joined: 10/14/2010
- SIP Device Name: Lynksis SPA2102
Re: Oct 6, 2010 Upgrade-Related Bugs
I am happy you find it funny Steve, but I have not been able to use my phone for over a week now. And it looks that something "has been set wrong" in this upgrade as my device had been working perfectly before it.FPL-steve wrote: Here's the funny part: we have a lot of SPA2102 users, and the vast majority of them are working just fine based on some comparison I did this morning. I'm not familiar with that device, but do we have any SPA2102 users with a working device here who'd like to share their configuration? There looks to be something set wrong in these affected devices that isn't in the working devices.
Alternatively, if any affected users are able to capture a wireshark trace that would also help. You should be able to see the invites coming into your network, but we need to see what's happening to them when they try to go to the device.
I am not a very advanced user, so if you could please explain how to "capture a wireshark trace", I will be more than happy to do it.
Thanks for your help.
-
- Technical Support
- Posts: 460
- Joined: 04/01/2010
- SIP Device Name: Cisco SPA112
- Firmware Version: 1.4.1 (SR5) Oct 14 2
- ISP Name: Cik Telecom
- Computer OS: Windows 10
- Router: Zyxel EMG2926
- Smartphone Model: LG G8 Thinq
- Android Version: Android Q
Re: Oct 6, 2010 Upgrade-Related Bugs
can you post a picture of this setting on here from your Voip ATA, so I can take a look at what options are there?kakgungor wrote:Does anyone at FPL have anything to say about my DTMF bug report?
Thanks
-
- Technical Support
- Posts: 460
- Joined: 04/01/2010
- SIP Device Name: Cisco SPA112
- Firmware Version: 1.4.1 (SR5) Oct 14 2
- ISP Name: Cik Telecom
- Computer OS: Windows 10
- Router: Zyxel EMG2926
- Smartphone Model: LG G8 Thinq
- Android Version: Android Q
Re: Oct 6, 2010 Upgrade-Related Bugs
Download wireshark from here http://www.wireshark.org/download.htmlkeolstep wrote:I am happy you find it funny Steve, but I have not been able to use my phone for over a week now. And it looks that something "has been set wrong" in this upgrade as my device had been working perfectly before it.FPL-steve wrote: Here's the funny part: we have a lot of SPA2102 users, and the vast majority of them are working just fine based on some comparison I did this morning. I'm not familiar with that device, but do we have any SPA2102 users with a working device here who'd like to share their configuration? There looks to be something set wrong in these affected devices that isn't in the working devices.
Alternatively, if any affected users are able to capture a wireshark trace that would also help. You should be able to see the invites coming into your network, but we need to see what's happening to them when they try to go to the device.
I am not a very advanced user, so if you could please explain how to "capture a wireshark trace", I will be more than happy to do it.
Thanks for your help.
-
- Quiet One
- Posts: 27
- Joined: 06/23/2010
Re: Oct 6, 2010 Upgrade-Related Bugs
Here is a screenshot Funkytown:Funkytown wrote:can you post a picture of this setting on here from your Voip ATA, so I can take a look at what options are there?kakgungor wrote:Does anyone at FPL have anything to say about my DTMF bug report?
Thanks
You do not have the required permissions to view the files attached to this post.
-
- Technical Support
- Posts: 460
- Joined: 04/01/2010
- SIP Device Name: Cisco SPA112
- Firmware Version: 1.4.1 (SR5) Oct 14 2
- ISP Name: Cik Telecom
- Computer OS: Windows 10
- Router: Zyxel EMG2926
- Smartphone Model: LG G8 Thinq
- Android Version: Android Q
Re: Oct 6, 2010 Upgrade-Related Bugs
For those having problems with incoming calls on your Spa2101..
Change your registration expire to 180!
Also take a look at Ring Waveform and see what it's set at.
By default it is set to trapezoid, PLEASE change it to sinusoid!
Sometimes this is the behavior of incoming calls not coming threw until you switch both of the above settings to what I suggested.
Change your registration expire to 180!
Also take a look at Ring Waveform and see what it's set at.
By default it is set to trapezoid, PLEASE change it to sinusoid!
Sometimes this is the behavior of incoming calls not coming threw until you switch both of the above settings to what I suggested.

-
- *Go-To Guy*
- Posts: 532
- Joined: 08/06/2010
- SIP Device Name: Grandstream HT-502
- Firmware Version: 1.0.1.63
- ISP Name: DSL TekSavvy
- Computer OS: OSX Snow Leopard
- Router: Linksys WRT54GL w/tomato
Re: Oct 6, 2010 Upgrade-Related Bugs
Two suggestions for the dtmf problem:
1. Try moving the RFC item to the top of the enabled list.
2. Try the "all enabled" function just to see.
Also, what is your outgoing audio codec? The "in audio" dtmf method can only work with certain codecs.
1. Try moving the RFC item to the top of the enabled list.
2. Try the "all enabled" function just to see.
Also, what is your outgoing audio codec? The "in audio" dtmf method can only work with certain codecs.
-
- Technical Support
- Posts: 460
- Joined: 04/01/2010
- SIP Device Name: Cisco SPA112
- Firmware Version: 1.4.1 (SR5) Oct 14 2
- ISP Name: Cik Telecom
- Computer OS: Windows 10
- Router: Zyxel EMG2926
- Smartphone Model: LG G8 Thinq
- Android Version: Android Q
Re: Oct 6, 2010 Upgrade-Related Bugs
Take out (disable) audio and rfc and leave ONLY "SIP INFO" for (enable)kakgungor wrote:Here is a screenshot Funkytown:Funkytown wrote:can you post a picture of this setting on here from your Voip ATA, so I can take a look at what options are there?kakgungor wrote:Does anyone at FPL have anything to say about my DTMF bug report?
Thanks
-
- Lightly Seasoned
- Posts: 202
- Joined: 10/17/2009
Re: Oct 6, 2010 Upgrade-Related Bugs
Set you codec to G711u and DTMF mode to INBAND.'kakgungor wrote:Does anyone at FPL have anything to say about my DTMF bug report?
Edit: checked your other posts and looks like you don't have INBAND as option. Then try AUDIO or AUTO if you have that.
-
- Technical Support
- Posts: 460
- Joined: 04/01/2010
- SIP Device Name: Cisco SPA112
- Firmware Version: 1.4.1 (SR5) Oct 14 2
- ISP Name: Cik Telecom
- Computer OS: Windows 10
- Router: Zyxel EMG2926
- Smartphone Model: LG G8 Thinq
- Android Version: Android Q
Re: Oct 6, 2010 Upgrade-Related Bugs
Spa2101 common issues is when your incoming calls goes to VoiceMail or busy signal and this is because the Spa2101 ATA is normaly behind a router/modem like most Voip ATA's. After your Spa2101 registers with FPL proxy server a port is opened for 5060 or 5070 to accept inbound connections and after a certain time the port will close automatically by your router/modem.
Changing the registration expire time to a shorter registration is one method and the other is to activate NAT Keep Alive which the ATA will send a packet by default every so many seconds to keep port 5060 or 5070 open and active. The NAT Keep Alive feature on the Spa2101 can be found on the Voice tab then choose the admin login and choose the advanced menu. From there choose eathier line 1 or line 2 that you are working with and the option will be available to choose to turn on or not.Make sure to always save and reboot after changing settings.
Remember people VOIP requires a little bit of patiance and networking skills.
Changing the registration expire time to a shorter registration is one method and the other is to activate NAT Keep Alive which the ATA will send a packet by default every so many seconds to keep port 5060 or 5070 open and active. The NAT Keep Alive feature on the Spa2101 can be found on the Voice tab then choose the admin login and choose the advanced menu. From there choose eathier line 1 or line 2 that you are working with and the option will be available to choose to turn on or not.Make sure to always save and reboot after changing settings.
Remember people VOIP requires a little bit of patiance and networking skills.
-
- Quiet One
- Posts: 27
- Joined: 06/23/2010
Re: Oct 6, 2010 Upgrade-Related Bugs
With those settings I can get the FPL voicemail to work fine, but other lines don't work. For example, calling a customer service number for a bank of mobile phone company doesn't work because it won't recognize the key presses that I enter for my account number. I have it set to use either G711 (u-law) or G729a depending if I'm on Wi-Fi or not.laurent wrote:Two suggestions for the dtmf problem:
1. Try moving the RFC item to the top of the enabled list.
2. Try the "all enabled" function just to see.
Also, what is your outgoing audio codec? The "in audio" dtmf method can only work with certain codecs.
-
- Quiet One
- Posts: 27
- Joined: 06/23/2010
Re: Oct 6, 2010 Upgrade-Related Bugs
Same issue with those settings. Key presses work with FPL voicemail but no other automated system I call in to.Funkytown wrote: Take out (disable) audio and rfc and leave ONLY "SIP INFO" for (enable)
-
- Lightly Seasoned
- Posts: 202
- Joined: 10/17/2009
Re: Oct 6, 2010 Upgrade-Related Bugs
kakgungor disable all DTMF modes except AUDIO and set your codec to G711u. Then post the results.
-
- Quiet One
- Posts: 27
- Joined: 06/23/2010
Re: Oct 6, 2010 Upgrade-Related Bugs
Using the G711u codec and setting the DTMF mode to "audio" doesn't work on FPL voicemail, nor does it work on other automated phone systems.zombie999 wrote:Set you codec to G711u and DTMF mode to INBAND.'kakgungor wrote:Does anyone at FPL have anything to say about my DTMF bug report?
Edit: checked your other posts and looks like you don't have INBAND as option. Then try AUDIO or AUTO if you have that.
-
- Technical Support
- Posts: 460
- Joined: 04/01/2010
- SIP Device Name: Cisco SPA112
- Firmware Version: 1.4.1 (SR5) Oct 14 2
- ISP Name: Cik Telecom
- Computer OS: Windows 10
- Router: Zyxel EMG2926
- Smartphone Model: LG G8 Thinq
- Android Version: Android Q
Re: Oct 6, 2010 Upgrade-Related Bugs
You do not have the required permissions to view the files attached to this post.
-
- Quiet One
- Posts: 27
- Joined: 06/23/2010
Re: Oct 6, 2010 Upgrade-Related Bugs
@Funkytown: what app is that?Funkytown wrote:
-
- Lightly Seasoned
- Posts: 202
- Joined: 10/17/2009
Re: Oct 6, 2010 Upgrade-Related Bugs
Interesting. Can you try another provider to isolate the issue with your device?kakgungor wrote:Using the G711u codec and setting the DTMF mode to "audio" doesn't work on FPL voicemail, nor does it work on other automated phone systems.zombie999 wrote:Set you codec to G711u and DTMF mode to INBAND.'kakgungor wrote:Does anyone at FPL have anything to say about my DTMF bug report?
Edit: checked your other posts and looks like you don't have INBAND as option. Then try AUDIO or AUTO if you have that.
-
- Quiet One
- Posts: 27
- Joined: 06/23/2010
Re: Oct 6, 2010 Upgrade-Related Bugs
Here are a few other screen shots to provide some context on my current settings. Please note that prior to the FPL upgrade I had DTMF working without any problems, so while I appreciate everyone suggesting that I change my codecs, I don't think it should be necessary.
You do not have the required permissions to view the files attached to this post.
-
- Quiet One
- Posts: 27
- Joined: 06/23/2010
Re: Oct 6, 2010 Upgrade-Related Bugs
Sorry I'm not sure what you mean by trying another provider. I don't have any other VoIP accounts.zombie999 wrote:Interesting. Can you try another provider to isolate the issue with your device?
-
- Technical Support
- Posts: 460
- Joined: 04/01/2010
- SIP Device Name: Cisco SPA112
- Firmware Version: 1.4.1 (SR5) Oct 14 2
- ISP Name: Cik Telecom
- Computer OS: Windows 10
- Router: Zyxel EMG2926
- Smartphone Model: LG G8 Thinq
- Android Version: Android Q
Re: Oct 6, 2010 Upgrade-Related Bugs
can you maybe switch applications and try this one ?? http://www.fring.com/download/iphone/
I heard you can use this for any voip carrier
I heard you can use this for any voip carrier
-
- Quiet One
- Posts: 27
- Joined: 06/23/2010
Re: Oct 6, 2010 Upgrade-Related Bugs
Interestingly, Fring gives the exact same results. FPL voicemail works for key presses, but other automated systems do not. The two non-FPL numbers I've tried are TD Bank and Bell Mobility. Anyone else having this issue?Funkytown wrote:can you maybe switch applications and try this one ?? http://www.fring.com/download/iphone/
I heard you can use this for any voip carrier
-
- Active Poster
- Posts: 80
- Joined: 10/16/2010
- SIP Device Name: Softphone, GS ATA HT286
- Firmware Version: 3.0.1
- ISP Name: Shaw
- Computer OS: XP, Win7
- Router: DLink
- Smartphone Model: Iphone 4S
- iOS Version: 5.1.1
Re: Oct 6, 2010 Upgrade-Related Bugs
For newly registered users after Oct 6, 2010, the following features are not working.
1. Not able to set the "personal greeting" in the voice mail although the system respond with OK but your callers always get the "Standard Greeting".
2. Not able to set the voicemail forwarding to e-mail option. No matter how hard you try to set it up in your web site account (Forward, Copy), it always bounced back with "none" and it is really "none". When your callers left messages into your voice mail box, you will never noticed by e-mail until you check your voice mail message on your softphone or ATA.
3. You cannot set up your PIN for the voice mail again although the *98 voice mail setup prompt you that is OK. When you perform remote access using say local number 778-803-4001, no matter what PIN you entered after you entered your mail box number (your FPL phone number), it will say invalid PIN.
It is definitely are server upgrade bugs that need FPL's attention to fix it ASAP.
I spoke with many of my friends that they registered before Oct 6, 2010 and have no problem on the above issues.
Therefore, the problems only applied to newly sign up user after Oct 6, 2010 I believe
1. Not able to set the "personal greeting" in the voice mail although the system respond with OK but your callers always get the "Standard Greeting".
2. Not able to set the voicemail forwarding to e-mail option. No matter how hard you try to set it up in your web site account (Forward, Copy), it always bounced back with "none" and it is really "none". When your callers left messages into your voice mail box, you will never noticed by e-mail until you check your voice mail message on your softphone or ATA.
3. You cannot set up your PIN for the voice mail again although the *98 voice mail setup prompt you that is OK. When you perform remote access using say local number 778-803-4001, no matter what PIN you entered after you entered your mail box number (your FPL phone number), it will say invalid PIN.
It is definitely are server upgrade bugs that need FPL's attention to fix it ASAP.
I spoke with many of my friends that they registered before Oct 6, 2010 and have no problem on the above issues.
Therefore, the problems only applied to newly sign up user after Oct 6, 2010 I believe
