Jump to content

Logicwrath

Customers
  • Posts

    578
  • Joined

  • Days Won

    21

Posts posted by Logicwrath

  1. It would be great if we could get an enabled/disabled option for allowing USB call recording on supported Yealink phones.  A very quick search provides the following models support USB call recording as of V81.  There could be more and this feature supports older firmware as well.

    SIP-T48G/S
    SIP-T46G/S
    SIP-T29G
    SIP-T27G
    SIP-T41S
    SIP-T42S

    features.usb_call_recording.enable = 1

    It is easy enough to manually enable this on the phone through the web interface by uploading a CFG file.  However, it would save some time to have this in the "Advanced Provisioner" as a simple Boolean option.

  2. Hello,

    I am doing this using Pivot and X-Lite.  Grab your apache logs to see the exact URI getting sent to your PHP file and use it to test the pivot script in a browser.  It should return JSON.  In this pivot $callerid gets set based on the dialed numbers area code.  I replaced my numbers with +15555555555.

    Setup a call flow using the API that uses a pattern.  I think in my call flow I am just matching * + 11 digits.

    <?php
    	
        function left($str, $length) {
            return substr($str, 0, $length);
        }
    
        function right($str, $length) {
            return substr($str, -$length);
        }
        
        //enable logging
        $logging = false;
        
        
        
        if ($logging) {
    
            $req_dump = print_r($_REQUEST, TRUE);
          
            $fp = fopen('dynamic_set_cid.log', 'a');
            fwrite($fp, $req_dump);
            
        }
    
        // set destination number to variable   
        $to = $_REQUEST['To'];
        
        //find area code, set to $areacode
        if (strlen($to) > 11) {
        
            $areacode = right(left($to,5),3);
            
            } else {
                
                $areacode = right(left($to,4),3);
            }
        
    	if ($logging) {
            fwrite($fp, '$to = ' . $to."\r\n");
            fwrite($fp, '$areacode = ' . $areacode."\r\n");
        }
        
        //select outbound callerid based on area code
        switch ($areacode) {
            
        case "231":
            $callerid = "+15555555555";
            break;
    
        case "248":
            $callerid = "+15555555555";
            break;
    
        case "586":
            $callerid = "+15555555555";
            break;
            
        case "734":
            $callerid = "+15555555555";
            break;
            
        case "810":
            $callerid = "+15555555555";
            break;
    	default:
    		$callerid = "+15555555555";
    		break;
        }
    	  
        //remove * from destination number
        $dest_number = str_replace("*", "", $to);
        
        if ($logging) {
            fwrite($fp, '$dest_number = ' . $dest_number."\r\n");
            fwrite($fp, '$callerid = ' . $callerid."\r\n");
            fclose($fp);
        }
       	
        header('content-type: application/json'); 
    ?>
    {
    "children": {
    "_": {
    "data": {
    "to_did": "<?php echo $dest_number ?>"
    ,"use_local_resources":false
    },
    "module": "resources"
    }
    },
    "data": {
    "caller_id_number": "<?php echo $callerid ?>"
    },
    "module": "set_cid"
    }

     

     

  3. Hello,

    I started thinking about this today as well as I was reviewing an RFP.  The RFP references Michigan's guide lines for multi-line telephone systems: https://www.michigan.gov/documents/msp/FINAL_MLTS_Guidelines_503991_7.pdf

    At first glance this it appears that to meet the requirements you need to enter the location of the phone in the "Address Line 2" box of the E911 emergency address:

    image.png.c62f169a60b7ad35603e39cae6cf7604.png

    According to that PDF it looks like this will be required for MLTS by December 31st 2019.

    "Under Michigan law, the provision of an Emergency Response Location (ERL) for every telephone capable of dialing 911 on a multi-line telephone system is required by December 31, 2019."

    I know in the past we talked about introducing locations into Monster UI to help with managing e911 for larger accounts with multiple locations.

    As I was thinking about this specific use case (for RFP's requiring the location information) I was wondering if it was possible to allow the location information (Address Line 2) to be merged from the User and Device level when the call is processed.  Perhaps this is what you were mentioning earlier in the thread Darren.

    The wording above makes it sound like all MLTS systems will require this by 2020.

  4. I have no experience with this.  However, you may look into the different DTMF types being used by the phones calling the doorbell.  RFC2833 vs INBAND etc..  One of the types I think INBAND will blast the DMTF audio on the same audio channel as the caller.  You may try different settings on the phone calling the intercom to see if it helps.

  5. In my past experience if you do not have something in the main "Fax Sent Receipts" field then none of the users will receive a fax sent receipt.  It effectively disabled the sent receipts entirely.  As a work around you can submit a fake email or unmonitored email or public folder/shared mailbox in the "Fax Sent Receipts" field and then all users should get their own fax sent receipts as well as the person listed in the field.

    image.png.c124ec0a40a4ad12dd5434ad08de805a.png

  6. I did some more testing.  Fore me this is only happening on a newer account with Yealink T48S devices.  I tested other older accounts and this is not happening to them.  On the other older accounts I tested multiple model phones including a T48S without the error.

    On the newer account with all T48S phones, the issue happens on every edit.  This account only has T48S phones in the advanced provisioner so I can't test other models.  All my testing on other older accounts is not producing the issue I describe in the first post.  It happens with multiple browsers and with Chrome incognito mode.  The issue must be with the account or perhaps is only happening with "new" accounts.

    This just spins forever:

    image.png.546272498ac4aaee74735f541e34174b.png

     

     

  7. Hello,

    When I update a config in Advanced Provisioner and save it the page goes to the "Updating Device Settings" with the animated spinning logo.  I will then see the blue triangle in the upper right hand corner which usually means something is happening and this will eventually go away.  However, the main page will not refresh back to the list of phones.  It just sits there saying "Updating Device Settings" forever and I have to reload the page and then re-select the sub account.

    This is super painful as I am trying to update about 15 phones right now and I have to reload the page and re-select the account after every phone.  I am also worried about reloading the page too fast before the config is properly generated.  I suspect as long as the blue triangle is gone it will be fine to refresh.  This is happening in multiple browsers.

  8. Hello,

    Welcome.

    I believe the official answer regarding BLF software will be something like using an iPad/Android tablet and 2600hz's operator console.  I believe there is a free and paid version of this.  It uses web sockets for real time updates and the paid version allows call control as far as I know.  You could also just run this on your PC in a second monitor as it is just a web page.

    I recommend you open a ticket to get sandbox access so you can demo the application and other stuff.

×
×
  • Create New...