qizhong wrote: 04/02/2025
A: Yes. I did factory reset and updated the to newest Firmware.
Appreciate your support! I have learned a lot.
I was told that you may have made a typo:
Fongo admin wrote:They may have an extra space or something like L instead of an i or a zero instead of a capital O.
That is almost verbatim what I stated earlier in this thread.
from
viewtopic.php?p=82260#p82260.
Liptonbrisk wrote:I'm seeing 403 Auth Failed in response to your outbound call requests in your syslog capture.
That suggests the Authenticate Password in your ATA is wrong. Possibly you've copied and pasted extra blank spaces (before the first character of the password or after the last character of the password).
Manually type your SIP password shown after logging in at https://www.freephoneline.ca/showSipSettings into the "Authenticate Password" field in your ATA's webUI. Disable password and form autofillers (browser app extensions) that may be filling in the wrong password automatically.
Even a single incorrect character (e.g., O vs 0, l vs 1), incorrect case (passwords are case-sensitive), or an accidental leading/trailing space can cause failure. If the password was copied and pasted, sometimes hidden characters or formatting can be included. Ensure it's the SIP Password provided by Freephoneline, not the password used to log into the Freephoneline web portal.
Fongo admin wrote: The user can request that Fongo's support team generate a new sip password for the Freephoneline account. This may help resolve the issues.
Afterwards you'd have to enter the new SIP password in your ATA.
You can submit a ticket here:
https://support.fongo.com/hc/requests/new
Choose "My Account Inquiry" for the final issue type.
If you're focused on hardware failure, possibly non-volatile flash memory, where the HT-701 stores the SIP password, became corrupted. In that case, the ATA might be reading incorrect password data. If it reads corrupted data and uses it to calculate the authentication response hash, that hash would not match what the server expects, leading to the 403 Auth failure. That's purely speculative/guessing though because there's no easy way for me to test whether the ATA's flash memory is corrupted.
This is how the MD5 hash (the response value) is generated by your HT-701 when authenticating with PortaSIP's server (Freephoneline), based on the standard SIP Digest process:
1. Initial Request
Your HT-701 sends its request (e.g., an INVITE to make a call to sip:
437xxxxxxx@voip4.freephoneline.ca:6060)
2. Server Challenge
The PortaSIP server responds with "401 Unauthorized". This message contains two important pieces of information for the calculation:
- A realm (e.g., sip-12.FSFEN-wsFongo)
- A unique nonce (a random string generated by the server)
3. Your HT-701 now gathers all the information it needs:
- Its configured SIP User ID (e.g., 1416xxxxxxx)
- The Authenticate Password stored in its configuration.
- The Realm received from the server (e.g., sip-12.FSFEN-wsFongo)
- The Nonce received from the server
- The SIP Method used in the original request (e.g., INVITE).
- The Request URI from the original request (e.g., sip:
437xxxxxxx@voip4.freephoneline.ca:6060)
4. Calculation Step 1 (Internal Hash 1):
The HT-701 takes the Username, Realm, and Password and uses MD5 to hash them together in a specific way. Let's call this internal result Hash 1 or HA1.
5. Calculation Step 2 (Internal Hash 2):
The HT-701 takes the SIP Method and the Request URI and uses MD5 to hash them together. Let's call this internal result Hash 2 (HA2).
6. Calculation Step 3 (Final Hash)
The HT-701 takes HA1, the Nonce (from the server), and HA2, and uses MD5 to hash these items together in a specific sequence.
Specifically, the HT-701 takes the hexadecimal representation of HA1, the Nonce value received from the server, and the hexadecimal representation of HA2, and concatenates them into a single string, using colons (:) as separators.
The string looks like this: HA1_hex:nonce_value:HA2_hex
The HT-701 then applies the MD5 hash function to this entire concatenated string.
7. Result
This final MD5 hash is the response value (such as 9d52ceasdkfjh298y4212h1asdfa. This isn't the real response from your syslog).
8. Send Back:
The HT-701 sends this calculated response value back to the PortaSIP server in the Authorization header of its second INVITE request.
The server then performs the same steps 4, 5, and 6 using the correct password it has stored for the user. If the final hash it calculates matches the response sent by the HT-701, authentication succeeds. If not, the server sends "403 Auth Failed".
Another possibility that might make sense is a firmware bug in the ATA, but that's extremely unlikely. There could be a bug in the HT-701's firmware causing it to incorrectly calculate the MD5 hash required for digest authentication, even if all the input values (SIP User ID, Authenticate password, realm, and nonce) are correct. That is highly improbable compared to simply having made a typo when entering the Authenticate password in the ATA. If there is a firmware bug (unlikely) that's causing this problem, you could try using an earlier firmware version if that's allowed by Grandstream (depending on the firmware version, switching to older firmware versions may be blocked). If there were a firmware bug, I'm sure others would have reported the exact same issue by now.
The cause is far more likely to be not having the SIP Password entered correctly in the ATA.
--
(General Info)
Visit
https://status.fongo.com/.
If "Support System" indicates "Partial Outage" or "Degraded Performance", ticket response time can take up to a week (or longer).
You can check your ticket status by logging in at
https://support.fongo.com/hc/requests. That's an account for tickets
(zendesk) only and is completely separate from your Freephoneline account or
any other Fongo account you may have. If you don't have a zendesk account yet, click "Sign Up" after visiting the link.
Use the same email address that you use to submit tickets. Do not use the same password as your Freephoneline or Fongo Mobile
account. Again, these accounts are unrelated.
Support staff does not respond to tickets on weekends or Canadian holidays.
Support hours are 9 a.m. until 4 p.m. EST.
Fongo does have
https://twitter.com/Fongo_Support. I'm not sure if anyone
there responds to direct messages.
Similarly, they appear to be on Facebook:
https://www.facebook.com/FongoMobile/. I don't know whether they'll respond to you there.
