Jump to content

Scott1234

Members
 View Profile  See their activity

  • Posts

    207

  • Joined

  • Last visited

 Content Type 

Posts posted by Scott1234

  2. Unexpected ZOHO call behaviour.

    in Integrations

    Posted

    FYI, when using the Zoho connection I have noticed any Star Code that is dialled will get a call pop and it won't go away. It gets stuck on the screen as an in-progress call and stays that way in zoho call logs, and you get a huge pile of them. I found this out after using the Login/Logout BLF button type to do agent login/logout *605 XXX code and just get covered in call pops you can't remove, same is true for other star codes. 

    Don't Log Star codes on the domain has no effect. 

     

     

  8. Counterpath Bria no longer working ( RFC 5746)

    in VoIP Phones

    Posted

    On 9/1/2023 at 5:49 AM, Vodia PBX said:

    The thing is that the PBX does not pass security scans unless it supports RFC 5746. There is a vulnerability for MiM attacks that RFC 5746 resolves. I would be surprised that this would pose a problem for Bria, as practically all servers that use TLS support this RFC. Anyhow, maybe someone can pas a PCAP to us so that we can take a look what is going on. On a side note, we are starting to replace LE RSA certificates with ECDH certificates, which might also be worth testing e.g. with Bria. 

    All I can say is once the changes were made to 68.0.28 TLS and Bria worked on the mobile devices after their 6.12.1 update. 

  9. For any one thats AU

    in Dial Plan Setup

    Posted

    2 hours ago, Vodia PBX said:

    Looking at https://en.wikipedia.org/wiki/Telephone_numbers_in_Australia would it be safe to say that the PBX should return '+61' + number for anything that starts with "1" as long as the number is more than 5 digits?

    That would only resolve 1800 XXX XXX or 1300 XXX XXX and 13 XX XX , but not 11 XX or 12 XX (network and community services) I did not include them in my example as they are less frequently used, but if doing it properly it should accommodate them, the yealink dial now examples from above show you the variables for these numbers. 

    Example dial before you dig (1100) is a popular number that people ring to check if there are dangerous services buried under where they are going to dig. 

        <!-- Matches Australian 1300 or 1800 numbers -->
    <Data DialNowRule="^((1300|1800)[0-9]{6})" LineID="0"/>

    <!-- Matches Australian 13 numbers -->
    <Data DialNowRule="^(13[0-9]{4})" LineID="0"/>
      
  <!-- Matches Australian special numbers emergency 000, 106, or 112 -->
    <Data DialNowRule="^(?:000|106|112)" LineID="0"/>

    <!-- Matches Australian special access numbers (dial before you dig etc. 11 or 12) -->
    <Data DialNowRule="^((11|12)[0-9]{2})" LineID="0"/>

  10. Calls not captured in CDR's when trunking

    in CDR

    Posted

    FYI, 

    I have noticed the odd call here and there which looks like this on the pbx.

    image.thumb.png.f644e1f0ec6f5dd984f64439a0712c12.png

    image.png

     

    image.thumb.png.b67fff851833d4b09d98c8368d9d084a.png

    It shows no trunk was used, but there was as they had a 45 min phone call to an external number, when you inspect the billing CDR's there is no record of this call... a little concerning if relying on the cdr's for billing. I am only using filet:disk with /usr/local/pbx/cdr_billing/$c/$m/$d.csv so as it does not think it's a trunk call it does not show up. 

    I can't find a way to reproduce on demand other than spotting them like this randomly when doing other works, I have seen it happen on the previous version too. 

    Thoughts, what could it be? when the user makes a call right after it could be fine again. 

     

     

  12. Counterpath Bria no longer working ( RFC 5746)

    in VoIP Phones

    Posted

    Quote

    Thanks for the info on 68.0.28 / 68.0.32 . When you say RFC 5746 was enabled by default, does this imply that in earlier versions, RFC 5746 could be manually enabled by setting some parameter?

    My understanding was it's there in other versions but not the default, not sure what versions. 

    I could be wrong but that would be best answered by Vodia as to if you could enable it, maybe a custom entry in pbx.xml?

     

  13. For any one thats AU

    in Dial Plan Setup

    Posted

    I have arrived at this for theglobalNumber() function , untested on the system, next question can I run a custom format.js ? in webwebai this should correct the dial out from having the area code for these numbers. 

    I think this is all that needs to change until I see the results of it tested. 

      
    } else if (country == "61") {
//Start of insert
      	if (number.substr(0, 4) == '1800' ||
     		number.substr(0, 4) == '1300' ||  
      		number.substr(0, 2) == '13') {
    		return '+61' + number;
//End of insert
        if (number.substr(0, 4) == "0011")
            return "+" + number.substr(4);
        if (number.substr(0, 1) == "0")
            return "+61" + number.substr(1);
        if (area != "" && area != "-")
            return "+61" + area + number

     

  14. For any one thats AU

    in Dial Plan Setup

    Posted

    Can I run a custom js in pbxwebai for this? I might play on a test box.

    It might be to do with,  

    } else if (country == "61") {
    if (number.substr(0, 3) == "+61") {
        return "0" + number.substr(3)
    } else {
        return "0011" + number.substr(1)
    }
}

    Needing to be something like this, but not 100% sure without testing. 

    } else if (country == "61") {
    if (number.substr(0, 3) == "+61") {
        return "0" + number.substr(3)
    } else if (number.substr(0, 4) == "1300" || number.substr(0, 4) == "1800") {
        return "+" + number;
    } else {
        return "0011" + number.substr(1)
    }
}

    And or maybe this section, with my mod. 

    function localNumber(number, country, area) {
    if (number.length < 6) {
        return number;
    }

    if (number.substr(0, 1) == "+") {
        if (country === undefined)
            country = sessionStorage.getItem("country");
        if (area === undefined)
            area = sessionStorage.getItem("area");

        if (country == "1") {
            if (number.substr(0, 2) == "+1" && number.length == 12) {
                return number.substr(2);
            } else {
                return "011" + number.substr(1);
            }
        } else if (country == "61") {
            if (number.substr(0, 4) == "+6113" || number.substr(0, 4) == "+6118") {
                return "+" + number.substr(2);
            } else if (number.substr(0, 3) == "+61") {
                return "0" + number.substr(3);
            } else if (number.substr(0, 3) == "130") {
                return "13" + number.substr(3);
            } else {
                return "0011" + number.substr(1);
            }
        } else if (country == "81") {
            if (number.substr(0, 3) == "+81") {
                return "0" + number.substr(3);
            } else {
                return "010" + number.substr(1);
            }
        } else if (country != "") {
            if (number.substr(0, 1) == "+" && number.substr(1, country.length) == country) {
                if (area.substr(0, 1) == "0")
                    area = area.substr(1);
                var local = number.substr(1 + country.length);
                if (local.substr(0, 1) == "0")
                    local = local.substr(1);
                if ((area && local.substr(0, area.length) == area) || area == "-") {
                    return local.substr(area.length);
                } else {
                    return local;
                }
            } else {
                return "00" + number.substr(1);
            }
        }
    }

    return number;
}

// Test cases
function testNumber(number) {
    console.log(`Input: "${number}" => Output: "${localNumber(number)}"`);
}

testNumber("1800444444");            // Output: "1800 444 444"
testNumber("1300444444");            // Output: "1300 444 444"
testNumber("611800444444");          // Output: "+61 1800 444 444"
testNumber("611300444444");          // Output: "+61 1300 444 444"
testNumber("+611800444444");         // Output: "+61 1800 444 444"
testNumber("+611300444444");         // Output: "+61 1300 444 444"

testNumber("131313");                // Output: "13 13 13"
testNumber("61131313");              // Output: "+61 13 13 13"
testNumber("+61131313");             // Output: "+61 13 13 13"

testNumber("0443388777");            // Output: "0443 388 777"
testNumber("61443388777");           // Output: "+61 443 388 777"
testNumber("+61443388777");          // Output: "+61 443 388 777"

testNumber("0295618006");            // Output: "02 9561 8006"
testNumber("61295618006");           // Output: "+61 2 9561 8006"
testNumber("+61295618006");          // Output: "+61 2 9561 8006"

testNumber("0395618006");            // Output: "03 9561 8006"
testNumber("61395618006");           // Output: "+61 3 9561 8006"
testNumber("+61395618006");          // Output: "+61 3 9561 8006"

testNumber("0795618006");            // Output: "07 9561 8006"
testNumber("61795618006");           // Output: "+61 7 9561 8006"
testNumber("+61795618006");          // Output: "+61 7 9561 8006"

testNumber("0895618006");            // Output: "08 9561 8006"
testNumber("61895618006");           // Output: "+61 8 9561 8006"
testNumber("+61895618006");          // Output: "+61 8 9561 8006"

testNumber("000");                   // Output: "000"
testNumber("+61000");                // Output: "+61 000"

    ¯\_(ツ)_/¯

    edit, also I think have gone down too many rabbit holes, I have analysed the script in more details and can see it would pass it to showNanpaNumber and format things a little differently.  So i will review more of the script before offering suggestions to adjustments.

    Either way currently as it stands it does not handle the 1800 1300 correctly as first mentioned. 

  15. Manage call recordings

    in Call Recording

    Posted

    I tested this and have the same issue. 

    When setting the scope to All Accounts, you can see all recordings, but when you define other accounts and/or include ring groups in case permission is needed, you don't get them. 

    Even if you do the inverse. 'All except specific accounts' are the same deal.

     

  16. Counterpath Bria no longer working ( RFC 5746)

    in VoIP Phones

    Posted

    I had noticed this issue a few months ago, your users must have only just updated the iOS app? The issue came out in this release. Bria Enterprise 6.12.1 (May 26, 2023)

    Quote

    Bria Enterprise 6.12.1 (May 26, 2023)

     

    Click here to see details.

    OpenSSL 3.0 Support

    The Bria app uses OpenSSL 3.0. Ensure your service provider supports secure renegotiation as per RFC 5746. Support for RFC 5746 secure renegotiation is now required by default for SSL or TLS connections to succeed.

    No Logout Button for End User Portal

    The Logout button is now removed from End User Portal when accessing it from within the app.

    Resolved issues

    • Fixed an issue where a missed call notification didn't appear properly on iOS 15.

    68.0.28 was supposedly when RFC 5746 was enabled by default.

    What version are you on? 

    It does work in 68.0.32

  17. For any one thats AU

    in Dial Plan Setup

    Posted

    @Vodia PBX

    Do we have any control over how the PBX interprets numbers for its auto-rewriting? Based on country code and area code? Australia is not set up right; when the domains are set with country code 61 most are auto-formatted correctly except a few. 

    The presentation for these numbers, which is how they are dialled, should be,

    1800 XXX XXX or (1800) XXX XXX

    1300 XXX XXX or (1300) XXX XXX

    13 XX XX or (13) XX XX 

    The problem is it thinks it needs an area code; these are the only numbers here that don't need that.

    To get the PBX to format it correctly, it has to be inputted as 01800 XXX XXX

    Once you set the domain area code to get the nice local number presentation, it will break the 1800/1300/13 dialling as it uses +61 7 1800 XXX XXX. 

    Numbers can go out as +61 1800 XXX XXX, just no area code for them.

    Even with the dial plan set to 'Don't rewrite', it still changes when processing. Luckily, it does not match how people dial them, so it only causes a problem once you set the domain area code.

    The PBX also like to format it like, 1800 XXXXXX

    Ideally, I would like to set the area code because the local number presentation and the app look much nicer.

    Thanks 

  18. Change view? Widen the Calls in domain to show more information? Improve WAC responsiveness?

    in PAC and WAC

    Posted

    7 hours ago, Brandywine said:

    Hello . 

    the interface can be customized if you have a working level of understanding of Jscript, HTML and CSS as well as the inner workings of the Vodia XML file structure  . We spent a few months on our version of the interface , you can see an example here https://brandywine.tech/video-tutorials/ 

    I have been working with Vodia for many years and very familiar, Vodia will not have the time or resources to show you how to do this, so be prepared to do some reading and trial and error , I would be glad to share a few tips with you or engage you in project services if its that important to you to edit as you like, but wont be inexpensive . might be good to start with some minro tweaking on a test system with a backup for changes that "break" the syste. 

    for now I would advise using the web panel and not the Windows App ., for now you will get the best results . thats just my opinion , Yori 

    Nice! I like it, one day I will venture in deeper, for now I have just done a clean login screen and matching top banner colour on the inner page.

    image.thumb.png.f35fbfc4e6790bc64fcc3f97ea73ec92.png

    image.thumb.png.e4725c9a9dcb8ba13bf7864cb04df0a3.png

     

     

  20. Custom page for when using "Ignore packets that do not match a domain on the system"

    in Web Interface

    Posted

    1 hour ago, Vodia PBX said:

    That is actually a good point. Why not having an error page — it might show the same content like now but should be customizable. The main concern here are robots trying the PBX out, and we want to provide as little information as possible and as little overhead as possible as well.

    Yeah, I was thinking to remove any content on it totally or redirect any requests that don't match to main business webpage, which would be off the pbx system, or is there a way to have it totally drop the request if nonmatching. Currently It spends some time loading a non-matching request before that page spits out. 

  21. Custom page for when using "Ignore packets that do not match a domain on the system"

    in Web Interface

    Posted

    I notice when using "Ignore packets that do not match a domain on the system" you eventually get this page after some time.

    Can we customize this? I don’t see it in the customization options, but if we put the appropriately named file in pbxwebai will it work? and if so, what is the naming for this file.  

     404 Not Found
Content-Type: text/html
Cache-Control: no-cache
Cache-Control: no-store
Content-Length: 186

<html><head>
<title>Error</title>
</head><body>
<h1>Please use a valid domain name.</h1>
<b></b>
<p>Please ask your system administrator to check the log file.</p>
</body></html>

     

  25. Dial Plan digit replacement

    in Dial Plan Setup

    Posted

    21 hours ago, MattJ said:

    Hi Everyone, 

    I am trying to write an entry for a dial plan, that will strip the first digit from a number - then append 2 other digits. 

    For example, I need my client to be able to dial 07xxxxxxxx and then the call go out as 617xxxxxxxx

    Can anyone tell me how to do that in Vodia please?

    Thanks

    Matt

    Sharing is caring. Just create a dial plan for each state replacing +613 with +612 etc.  And or remove + depending on what you are doing.  

    2;o-trk1;;000;+61000;;false
20;o-trk1;;^([0-9]{8})@;+613*;;false
22;o-trk1;;^0([0-9]{9})@|^61([0-9]{9})@;+61*;;false
24;o-trk1;;^([18,13][0-9]{9}|13[0-9]{4})@;+*;;false
80;o-trk1;;+*;+*;;false
82;o-trk1;;0011*;+*;;false

     

×
×
  • Create New...