What's new
By:

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

Recent content by MDB_Knox

  1. M

    [Release] Asuswrt-Merlin 380.65 is now available

    A full reset was the first thing I tried following the upgrade -- it was a no go in terms of making any difference. I will check 63 and 64 over the weekend, but after perusing the forum a bit more, I have found two other threads with regards to SIP Passthrough/WiFi Calling/etc. problems that...
  2. M

    Wi‑Fi calling

    SIP Passthrough does not work properly in version 380.65 and possibly not in any version later than 380.62_1 (latest one I've tested that I know works right). The symptoms are that outbound calls work, but inbound calls do not. I have verified that SIP INIT's being sent over 5060 from my trunk...
  3. M

    Issue with SIP NAT passthrough disabled

    Something is broken in 380.65 with regards to SIP Passthrough. Specifically, for whatever reason, SIP INIT's are not getting passed back downstream (i.e. outbound calls work, but no notification of inbound calls ever gets received). I'm using a dedicated SIP Trunk tied to a FreePBX Asterisk...
  4. M

    [Release] Asuswrt-Merlin 380.65 is now available

    I've got a new and interesting bug with 380.65 on both an RT-N66 and an RT-AC68. Specifically, when I upgraded from 380.62_1 to 380.65 our VOIP (FreePBX) phone system quit being able to receive inbound calls. Outbound still worked fine, but all inbound SIP INIT's were being somehow blocked by...
  5. M

    PPTPD password restrictions/custom chap-secrets

    If you are speaking specifically of MS-ChapV2 then according to RFC2759 the input password specifically allows for 0-256 unicode characters -- which basically means that punctuation/special characters are allowed. And I can specifically attest that pptpd DOES handle the ampersand character among...
  6. M

    PPTPD password restrictions/custom chap-secrets

    Specifically, my question is why are certain special characters (notably ampersand) are prohibited from being used in the chap-secrets file for pptpd passwords? I am assuming that this is probably due to a limitation of the webgui handling, because if I hand edit chap-secrets and then restart...
See more
Back
Top