j8van wrote:Same here!
I have a pbxes account worked with Freephoneline. From Thursday, May 16 afternoon the Freephoneline lost registration and has since never restored.
I have been using pbxes+FPL for almost 2 years, I purchased the Voip Unlocked Key, been noticed the latest Setup Guideline, but you know, being a pbxes account holder we have nowhere to change any setting variables but our VoIP credentials, I don't think we are those who abused FPL's system and made it heavily loaded.
I didn't make any changes since day 1, but from last December on, so often the registration drops! and the worse thing is no official suggestions were ever released to help us (I might have missed any), I really feel that we pbxes users are ignored and kind of "marginized".
Any helpful instructions to save us from stucking services are greatly appreciated.
Fongo Support wrote:Hi there,
Please contact system admin at pbxes.org and ask them to ensure that FPL trunks are setup as per FPL guidelines.
To review the guidelines please visit the link below:
http://support.freephoneline.ca/entries ... redentials
This should resolve the reported issue.
For now, please setup your account directly on the ATA until the issue will be resolved at pbxes.org.
Please try my suggestion and let me know.
Thanks,
j8van wrote:Fongo Support wrote:Hi there,
Please contact system admin at pbxes.org and ask them to ensure that FPL trunks are setup as per FPL guidelines.
To review the guidelines please visit the link below:
http://support.freephoneline.ca/entries ... redentials
This should resolve the reported issue.
For now, please setup your account directly on the ATA until the issue will be resolved at pbxes.org.
Please try my suggestion and let me know.
Thanks,
Thanks for the quick respond.
pbxes admin claimed he had changed nothing and he won't make any change specificly for FPL settings.
No offence, but I'm pretty sure the connection problems are from FPL side. part of my pbxes friends are having the same issue while the rest are OK, however the "having issue group" is growing!!
voip.freephoneline.ca is the only server name can be used by pbxes free account holders however, ironicly, voip.freephoneline.ca is right the server which is forbidding "multi-users with same IP" from using FPL services.
In such case I can't do anything no matter how many times FPL staffs saying "your setup is not following our guideline"... Anyway anyway, above all, limiting users from same IP to avoid system being abused sounds right, but it also does harm to innocent people.
Please investigate and fix the problem intensively, thanks a lot.
Pegasus wrote:I want to confirm that my account it is showing disconnected since last Thursday using pbxes. After 5 days without phone line, I find this unacceptable.
I want also to highlight that if you do restrictions for users on pbxes, a mail dated from March when I buy the unlock key shows pbxes as provider. Please be consistent and reliable.
Dear Customer,
Because you purchased a VoIP Unlock Key from Dell Voice or Freephoneline, we're writing to let you know that the configuration settings for your VoIP Unlock Key are now available online for easy reference. We recommend you review the required settings and best practices for your third party SIP clients (such as ATAs, softphones, or PBXes).
Fongo Support wrote:j8van wrote:Fongo Support wrote:Hi there,
Please contact system admin at pbxes.org and ask them to ensure that FPL trunks are setup as per FPL guidelines.
To review the guidelines please visit the link below:
http://support.freephoneline.ca/entries ... redentials
This should resolve the reported issue.
For now, please setup your account directly on the ATA until the issue will be resolved at pbxes.org.
Please try my suggestion and let me know.
Thanks,
Thanks for the quick respond.
pbxes admin claimed he had changed nothing and he won't make any change specificly for FPL settings.
No offence, but I'm pretty sure the connection problems are from FPL side. part of my pbxes friends are having the same issue while the rest are OK, however the "having issue group" is growing!!
voip.freephoneline.ca is the only server name can be used by pbxes free account holders however, ironicly, voip.freephoneline.ca is right the server which is forbidding "multi-users with same IP" from using FPL services.
In such case I can't do anything no matter how many times FPL staffs saying "your setup is not following our guideline"... Anyway anyway, above all, limiting users from same IP to avoid system being abused sounds right, but it also does harm to innocent people.
Please investigate and fix the problem intensively, thanks a lot.
H there,
Have you tried contacting sys admin at pbxes.org? Please send me a PM with the details.
Thanks,
Twinkie wrote:Maybe if a Fongo engineer (not Fongo Support) could chime in on how the block rules are set up, it could be better determined where to resolve it.
*IF* they are just counting how often an offending IP is attempting registration, then yes, Fongo should whitelist PBXes, SipSocery, Etc IP's.
*IF* they are counting how often a user (as determined from the SIP URI) is attempting registration, then yes, the onus would be on PBXes etc to modify the reg. time. Good luck with that. I tried to change it for just one trunk with no luck.
Because of FPL/Fongo's whacky rule/setup, which didn't play nicely with my other trunks, I removed FPL from my primary pbx, brought up a new pbx in a VM and FPL is registered there and IAX trunked to my primary system. Not ideal for everyone, I know.
Hi there,
Please send me PM with your trunk(s) details and I will have a look.
There are several users running pbx with 3+ trunks and have no issues.
On a side note- if you have any contacts from pbxes.org- please send me PM with the details.(direct line, email, etc)
Thanks,
Fongo Support wrote:Twinkie wrote:Maybe if a Fongo engineer (not Fongo Support) could chime in on how the block rules are set up, it could be better determined where to resolve it.
*IF* they are just counting how often an offending IP is attempting registration, then yes, Fongo should whitelist PBXes, SipSocery, Etc IP's.
*IF* they are counting how often a user (as determined from the SIP URI) is attempting registration, then yes, the onus would be on PBXes etc to modify the reg. time. Good luck with that. I tried to change it for just one trunk with no luck.
Because of FPL/Fongo's whacky rule/setup, which didn't play nicely with my other trunks, I removed FPL from my primary pbx, brought up a new pbx in a VM and FPL is registered there and IAX trunked to my primary system. Not ideal for everyone, I know.
Hi there,
Please send me PM with your trunk(s) details and I will have a look.
There are several users running pbx with 3+ trunks and have no issues.
On a side note- if you have any contacts from pbxes.org- please send me PM with the details.(direct line, email, etc)
Thanks,
Hi there,
Just to give everyone an update, Sys admins at pbxes and sorcery.com have been contacted to resolve this issue.
Once I have an update from them, I will update the thread.
Thanks,
Fongo Support wrote:Hi there,
Just to give everyone an update, Sys admins at pbxes and sorcery.com have been contacted to resolve this issue.
Once I have an update from them, I will update the thread.
Thanks,
Hi there,
Update at 6:25 PM- Sys admin from Pbxes.org has responded and the issue should be resolved for all Pbxes.org users.
Sip sorcery- still awaiting for Sys admin to reply.
I will update the thread once I have more information.
Thanks,
I tested my pbxes account right after seeing the above update and it seems all good now.
I wasn't expecting this could be solved so quickly (I thought pbxes admin would not answer FPL's request, needless to say answering our user's individual request).
You've done a good job Fongo Support, and I apologize for any blaming on you (and FPL) in my post.
And thanks to Jake.
domptg wrote:The problem with Pbxes.org still exists. My FPL number lost the registration for no reason today and I had to manually reboot it my Pbx account to reregister my number back.
pmarsteau wrote:Since a few days, the issue occurred again with pbxes.org. They blame FPL again, despite we mention that support link where they had to adjust their config. The symptoms observed is a TOO MANY REQUEST error received at pbx level from FPL. Error is sporadic and particularly occur during peak usage during eastern daytime.
Could you check with same contact details used last time to check settings and rules for blocking registrations?
Thanks,
--Phil
Users browsing this forum: No registered users and 12 guests