Oct 6, 2010 Upgrade-Related Bugs

[FONGO_kris]

glassfish,

I will look into your issue as soon as I can tomorrow, however if I cannot I will appoint someone to do so - before this of course may I ask what troubleshooting you've done towards your internal network, such as port forwarding (function in your router), and making sure your firewalls or anti-virus software aren't blocking any crucial UDP communication ports?

[glassfish]

Hi Admin, thanks for your reply - actually I didn't have anything changed in my router settings and nor did I have in my ATA... - I've been using my FPL phone like this since the first day I purchased my ATA and the FPL configuration file - it was working good until recently after your upgrade... And I did see someone else on this forum posted for the same problem/symptom that I'm having(i.e. incmoing calls simply not taken/not going through, but outgoing calls are ok)... not sure if you need any other info but I'm sure there is nothing changed on my side... please check accordingly and thanks,

In case you need to conatc me, you have my alternative phone number in the PM and in the email I sent to support@freephoneline.ca.

Thanks.

glassfish,

I will look into your issue as soon as I can tomorrow, however if I cannot I will appoint someone to do so - before this of course may I ask what troubleshooting you've done towards your internal network, such as port forwarding (function in your router), and making sure your firewalls or anti-virus software aren't blocking any crucial UDP communication ports?

[Funkytown]

Update:
I have called my Internet provider today and everything seems fine through tests and all.. so the problem im having is lag or skipping issues can yah let me know if this been noticed since the upgrade on certain accounts? This has only started since the upgrade and before the upgrade I never had any of these issues what so ever.

Thanks

[mlaposta]

Don't think this was listed among the "official" bugs after the upgrade, but since the upgrade my phones don't have the VM dial tone, and the VM indicator on my phones aren't on, yet I know I have unchecked VMs.

I didn't even know I had VMs until I logged in to FPL today and checked my account online.
Any idea what's going on with this and if it's being looked into?

Thanks,
Mike

[FONGO_steve]

Don't think this was listed among the "official" bugs after the upgrade, but since the upgrade my phones don't have the VM dial tone, and the VM indicator on my phones aren't on, yet I know I have unchecked VMs.

I didn't even know I had VMs until I logged in to FPL today and checked my account online.
Any idea what's going on with this and if it's being looked into?

Thanks,
Mike

Yep - we have seen this come up with some isolated accounts which are now coming to our attention that users have been using it for a while to notice. I'm looking into this one and should have a better update from the programming team by morning.

[glassfish]

Hi FPL-steve, I just sent you a PM regarding the problem I'm having - the incoming calls not taken - one of your colleagues "Admin" replied back to me but so far I have never heard news back, can you please check my PM?


I believe I got same problem as this user UD3046 got - Please note I didn't change anything in my ATA and my router, the problem started after your upgrade. can you please check for me, it's not working for many days... thanks,

FPL - In coming calls can not be taken...
by UD3046 » Wed Oct 06, 2010 4:55 pm

Oct 6th, As reported to support - FPL - In coming calls can not get through. They also can not excess voice mail. (never makes it to voice mail). Out bound calls are okay. Hope is it fixed by morning!!.

[laurent]

Steve, Kris,

Just in case neither of you saw both my previous messages on this, I would like to report that message waiting indicator is STILL not working. My ATA attempts the subscribe command and it gets a server error:

Code: Select all

Oct 13 22:05:45 voip HT502: [00:0B:82:18:1A:2E][1.0.1.63] Subscribe transaction got code 0:501
Oct 13 22:05:46 voip HT502: [00:0B:82:18:1A:2E][1.0.1.63] Received 501 response for transaction 9302(SUBSCRIBE)
Oct 13 22:05:46 voip HT502: [00:0B:82:18:1A:2E][1.0.1.63] Request 9302 got status code 501, refCnt 2
Oct 13 22:05:46 voip HT502: [00:0B:82:18:1A:2E][1.0.1.63] Subscribe transaction got code 0:501
Oct 13 22:05:50 voip HT502: [00:0B:82:18:1A:2E][1.0.1.63] Kill NICT transaction 9301
Oct 13 22:05:51 voip HT502: [00:0B:82:18:1A:2E][1.0.1.63] Kill NICT transaction 9302
Oct 13 22:06:16 voip HT502: [00:0B:82:18:1A:2E][1.0.1.63] Received 501 response for transaction 9303(SUBSCRIBE)
Oct 13 22:06:16 voip HT502: [00:0B:82:18:1A:2E][1.0.1.63] Request 9303 got status code 501, refCnt 2
Oct 13 22:06:16 voip HT502: [00:0B:82:18:1A:2E][1.0.1.63] Subscribe transaction got code 0:501
Oct 13 22:06:17 voip HT502: [00:0B:82:18:1A:2E][1.0.1.63] Received 501 response for transaction 9304(SUBSCRIBE)
Oct 13 22:06:17 voip HT502: [00:0B:82:18:1A:2E][1.0.1.63] Request 9304 got status code 501, refCnt 2
Oct 13 22:06:17 voip HT502: [00:0B:82:18:1A:2E][1.0.1.63] Subscribe transaction got code 0:501
Oct 13 22:06:21 voip HT502: [00:0B:82:18:1A:2E][1.0.1.63] Kill NICT transaction 9303
Oct 13 22:06:22 voip HT502: [00:0B:82:18:1A:2E][1.0.1.63] Kill NICT transaction 9304
Oct 13 22:06:47 voip HT502: [00:0B:82:18:1A:2E][1.0.1.63] Received 501 response for transaction 9305(SUBSCRIBE)
Oct 13 22:06:47 voip HT502: [00:0B:82:18:1A:2E][1.0.1.63] Request 9305 got status code 501, refCnt 2
Oct 13 22:06:47 voip HT502: [00:0B:82:18:1A:2E][1.0.1.63] Subscribe transaction got code 0:501

This worked on the older server (prior to this upgrade), so I assume that this is another glitch to fix. Not urgent in my case, I get all my voicemails via email anyhow, but it's a nice feature that shouldn't be allowed to drop off the list of things to fix.

[Funkytown]

Update:
lag or skipping issues can yah let me know if this been noticed since the upgrade on certain accounts?

It seems that this has been fixxed on my end within the last time I posted, great to see things coming alone guys

[Funkytown]

Steve, Kris,

Just in case neither of you saw both my previous messages on this, I would like to report that message waiting indicator is STILL not working. My ATA attempts the subscribe command and it gets a server error:

Code: Select all

Oct 13 22:05:45 voip HT502: [00:0B:82:18:1A:2E][1.0.1.63] Subscribe transaction got code 0:501
Oct 13 22:05:46 voip HT502: [00:0B:82:18:1A:2E][1.0.1.63] Received 501 response for transaction 9302(SUBSCRIBE)
Oct 13 22:05:46 voip HT502: [00:0B:82:18:1A:2E][1.0.1.63] Request 9302 got status code 501, refCnt 2
Oct 13 22:05:46 voip HT502: [00:0B:82:18:1A:2E][1.0.1.63] Subscribe transaction got code 0:501
Oct 13 22:05:50 voip HT502: [00:0B:82:18:1A:2E][1.0.1.63] Kill NICT transaction 9301
Oct 13 22:05:51 voip HT502: [00:0B:82:18:1A:2E][1.0.1.63] Kill NICT transaction 9302
Oct 13 22:06:16 voip HT502: [00:0B:82:18:1A:2E][1.0.1.63] Received 501 response for transaction 9303(SUBSCRIBE)
Oct 13 22:06:16 voip HT502: [00:0B:82:18:1A:2E][1.0.1.63] Request 9303 got status code 501, refCnt 2
Oct 13 22:06:16 voip HT502: [00:0B:82:18:1A:2E][1.0.1.63] Subscribe transaction got code 0:501
Oct 13 22:06:17 voip HT502: [00:0B:82:18:1A:2E][1.0.1.63] Received 501 response for transaction 9304(SUBSCRIBE)
Oct 13 22:06:17 voip HT502: [00:0B:82:18:1A:2E][1.0.1.63] Request 9304 got status code 501, refCnt 2
Oct 13 22:06:17 voip HT502: [00:0B:82:18:1A:2E][1.0.1.63] Subscribe transaction got code 0:501
Oct 13 22:06:21 voip HT502: [00:0B:82:18:1A:2E][1.0.1.63] Kill NICT transaction 9303
Oct 13 22:06:22 voip HT502: [00:0B:82:18:1A:2E][1.0.1.63] Kill NICT transaction 9304
Oct 13 22:06:47 voip HT502: [00:0B:82:18:1A:2E][1.0.1.63] Received 501 response for transaction 9305(SUBSCRIBE)
Oct 13 22:06:47 voip HT502: [00:0B:82:18:1A:2E][1.0.1.63] Request 9305 got status code 501, refCnt 2
Oct 13 22:06:47 voip HT502: [00:0B:82:18:1A:2E][1.0.1.63] Subscribe transaction got code 0:501

This worked on the older server (prior to this upgrade), so I assume that this is another glitch to fix. Not urgent in my case, I get all my voicemails via email anyhow, but it's a nice feature that shouldn't be allowed to drop off the list of things to fix.

Hi, Im going to do some test with the HT502 with the voicemail indication on my end right now I will let you know the outcome

[kakgungor]

I'm not sure if this is being reported elsewhere, but as of yesterday my FPL account does not seem to be responding properly to key presses when calling in to an automated system. I am even having problems with the PFL voicemail system not recognizing my key presses. Did the upgrade affect the DTMF mode I need to select? I have the options of: audio, SIP INFO, and RFC 2833 with my ATA. I should add that it seemed to work fine the first few days after the upgrade, but is not working any longer. I have not changed any settings on my end.

[charettepa]

has any progress been made
does FPL have any indications as to what the problem could be
i get the same error with my PAP2T
phone support keeps telling me that its not a problem on the FPL server
but clearly the problem is not at my end, other people have the issue

Just to be clear
-i have moved the ATA in front of the router directly on the modem
-i have tried to reset to factory settings
-i have tried a dlink ATA
-i have tried X-lite (PC)
-i have tried sipdroid (android)

if i can do anything to help test, please advise.
if possible please provide a status update

Steve, Kris,

Just in case neither of you saw both my previous messages on this, I would like to report that message waiting indicator is STILL not working. My ATA attempts the subscribe command and it gets a server error:

Code: Select all

Oct 13 22:05:45 voip HT502: [00:0B:82:18:1A:2E][1.0.1.63] Subscribe transaction got code 0:501
Oct 13 22:05:46 voip HT502: [00:0B:82:18:1A:2E][1.0.1.63] Received 501 response for transaction 9302(SUBSCRIBE)
Oct 13 22:05:46 voip HT502: [00:0B:82:18:1A:2E][1.0.1.63] Request 9302 got status code 501, refCnt 2
Oct 13 22:05:46 voip HT502: [00:0B:82:18:1A:2E][1.0.1.63] Subscribe transaction got code 0:501
Oct 13 22:05:50 voip HT502: [00:0B:82:18:1A:2E][1.0.1.63] Kill NICT transaction 9301
Oct 13 22:05:51 voip HT502: [00:0B:82:18:1A:2E][1.0.1.63] Kill NICT transaction 9302
Oct 13 22:06:16 voip HT502: [00:0B:82:18:1A:2E][1.0.1.63] Received 501 response for transaction 9303(SUBSCRIBE)
Oct 13 22:06:16 voip HT502: [00:0B:82:18:1A:2E][1.0.1.63] Request 9303 got status code 501, refCnt 2
Oct 13 22:06:16 voip HT502: [00:0B:82:18:1A:2E][1.0.1.63] Subscribe transaction got code 0:501
Oct 13 22:06:17 voip HT502: [00:0B:82:18:1A:2E][1.0.1.63] Received 501 response for transaction 9304(SUBSCRIBE)
Oct 13 22:06:17 voip HT502: [00:0B:82:18:1A:2E][1.0.1.63] Request 9304 got status code 501, refCnt 2
Oct 13 22:06:17 voip HT502: [00:0B:82:18:1A:2E][1.0.1.63] Subscribe transaction got code 0:501
Oct 13 22:06:21 voip HT502: [00:0B:82:18:1A:2E][1.0.1.63] Kill NICT transaction 9303
Oct 13 22:06:22 voip HT502: [00:0B:82:18:1A:2E][1.0.1.63] Kill NICT transaction 9304
Oct 13 22:06:47 voip HT502: [00:0B:82:18:1A:2E][1.0.1.63] Received 501 response for transaction 9305(SUBSCRIBE)
Oct 13 22:06:47 voip HT502: [00:0B:82:18:1A:2E][1.0.1.63] Request 9305 got status code 501, refCnt 2
Oct 13 22:06:47 voip HT502: [00:0B:82:18:1A:2E][1.0.1.63] Subscribe transaction got code 0:501

This worked on the older server (prior to this upgrade), so I assume that this is another glitch to fix. Not urgent in my case, I get all my voicemails via email anyhow, but it's a nice feature that shouldn't be allowed to drop off the list of things to fix.

Hi, Im going to do some test with the HT502 with the voicemail indication on my end right now I will let you know the outcome

[charettepa]

hi Steve

2 other people at my work have FPL
we all have the same issue since the upgrade
other people in the forum have also commented on this

someone even posted logs from their ATA in the thread that this is from showing that the VM request is going to your server and your server then generates an error in return.

i will assist in testing this in any way i can.
however at this point i truly think i have done everything possible and proven that the error is not user side.

as you can see in the posts many people are affected its just that many people like myself have not noticed until now that it wasnt working as we are receiving the email notification. this exact comment is also in the thread by a different user.

[FONGO_steve]

mis-understood your last post - thought it was about device not authentication, not MWI.

Message waiting indicator is being looked into - I'll update as needed. Let's try and keep posts about solved issues, or acknowledged issues, in this thread to a minimum now. It's starting to turn into a rambling of lots of unrelated problems and a lot of repeats of the same problem.

As it stands, right now message waiting indicator is the last major issue being looked into.
Some users are unable to update their voicemail greeting, which is linked to the above MWI bug - also being looked into.

[laurent]

Let's try and keep posts about solved issues, or acknowledged issues, in this thread to a minimum now. It's starting to turn into a rambling of lots of unrelated problems and a lot of repeats of the same problem.

That's because of all the threads about all the issues people have, it's really hard to know which problem you guys have acknowledged and are working to resolve. I've been reading every new post and I believe this is the first time you've actually acknowledged the MWI problem, despite my postings about it 3 times, and several other users.

Perhaps a pinned locked thread with a list of currently worked on problems would serve as a central source so we'd know what not to complain about

[Funkytown]

I have the options of: audio, SIP INFO, and RFC 2833 with my ATA.

im using this and it works SIP INFO

[Funkytown]

Ok, MWI=Message Waiting Indication was NOT working last night so laurent my friend we now know Steve of FPL is working on this, great to hear!

Im wishing for all of us to have back the option Call Privacey= *67 or *30. [Any Updates]
Rememeber this was working fine before the upgrade! Now it doesnt work when we try and block our phone number.
Thanks

[Funkytown]

hi i'm new to this and i'm using freephoneline. everything was working fine and now i can't hear the person on the other line. its not my mic or headset i can hear the phone ring but when the other party picks up i can't hear them. is there anyone on here that are having the same problems? and of so call someone PLEASE help me. libby p.s i tried everything on my side

[Update] This problem seems to be fixxed now, as I have spoken with her directly

[kakgungor]

I have the options of: audio, SIP INFO, and RFC 2833 with my ATA.

im using this and it works SIP INFO

@Funkytown, using SIP INFO I can get the FPL voicemail to accept my key presses, however if I call another number (such as TD EasyLine) it does not recognize the key presses. Does SIP INFO work for you when calling everything or have you only tested it with the FPL voicemail?

[keolstep]

I have not been able to receive any incoming calls since the upgrade, just a busy signal every time someone is trying to call my FPL number. I tried resetting my router and ATA (Linksys SPA2102), forwarded ports on router again. Nothing works. FPL support, are you working on this issue? As far as I see, I'm not the only one experiencing these problems.

[laurent]

Does SIP INFO work for you when calling everything or have you only tested it with the FPL voicemail?

My ATA (Grandstream HT502) is currently set for this:
Priority 1: RFC2833
Priority 2: in audio
Priority 3: in audio

And my preferred codec is 729.

With this, I can use my phone's keypad to navigate the menus of my office phone system, so it works properly. (Just tested it)

[areby51]

i haven't been able to receive any incoming calls since the upgrade (everything was working fine prior to that) and I haven't changed any router or ata settings. every time someone calls, they get a busy signal. there have been occasional times where the call will come through, but it is quite intermittent and variable. pls look into this.

[Funkytown]

I have the options of: audio, SIP INFO, and RFC 2833 with my ATA.

im using this and it works SIP INFO

@Funkytown, using SIP INFO I can get the FPL voicemail to accept my key presses, however if I call another number (such as TD EasyLine) it does not recognize the key presses. Does SIP INFO work for you when calling everything or have you only tested it with the FPL voicemail?

it works for banks,voicemail,auotmated machines ...everything so far

[Funkytown]

i haven't been able to receive any incoming calls since the upgrade (everything was working fine prior to that) and I haven't changed any router or ata settings. every time someone calls, they get a busy signal. there have been occasional times where the call will come through, but it is quite intermittent and variable. pls look into this.

This is what libby did, she uninstalled the old FPL app softphone and rebooted and then reinstalled the softphone app and it worked not long after. Try this...

[glassfish]

Hi there, I got exactly same problem - incoming calls just can't get through, only busy signal... I bought configuration file from FPL and using my own Linksys wrt54gp2 ATA, it was always working good before FPL upgrade and I never changed my ATA/router settings... not sure what's going on??? it's been many days like this...

not sure if someone from FPL can please list this as an official bug and please fix it...

Btw I conatcted my ISP, they didn't change anything either...

I have not been able to receive any incoming calls since the upgrade, just a busy signal every time someone is trying to call my FPL number. I tried resetting my router and ATA (Linksys SPA2102), forwarded ports on router again. Nothing works. FPL support, are you working on this issue? As far as I see, I'm not the only one experiencing these problems.

[FONGO_steve]

So far the inability to receive incoming calls since the upgrade is only affecting SPA2101 users. The post above with the wrt54gp2 is the first non-SPA2102 device, but, the wrt54gp2 is very similar to the SPA2102 and likely uses the same coding for it's voice port setup.

Here's what we see on our end: SIP invites are being sent to these devices the same as before. Each call has several invites being sent to the device, but the device never acknowledges or responds to any of them.

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.