Logicwrath
-
Posts
578 -
Joined
-
Days Won
21
Content Type
Profiles
Forums
Resource Library: Monster UI Apps for KAZOO
Events
Downloads
Posts posted by Logicwrath
-
-
Hello,
In the provisioner, we have a reboot option per device. It would be nice if we had the following options above and beyond that.
1. Reboot single device at X time. This way we can make a change and have the phone automatically reboot late at night when it is not in use.
2. Reboot single device at X time on schedule. I have seen people complain about BLF issue and phone reboots. In some cases rebooting a single phone on a schedule might help eliminate complaints.
3. Reboot all phones in an account.
4. Reboot all phones in an account at X time.
5. Reboot all phones in an account at X time on a schedule.
---
At this time it would certainly be helpful if we could schedule reboots at night for when we make changes but don't want to reboot the phone because we don't know if it is in use. -
Is the Odoo integration something public/open or is there a link to more information somewhere?
-
Hello,
We would like to integrate the hosted Kazoo environment with a hosted CRM product. We may consider doing some custom development in this area. Are there any solutions already available? Has anyone already reviewed the major CRMs with an API for this purpose? -
I assume if you switch the SIP signaling to TCP it would also include the BLF. Although, TCP requires more overhead and is certainly not as good as UDP for real time audio. I advise against using TCP.
Getting a packet capture and trying to identify the problem is the best start. I think the option you found about allowing out of order packets is a great start.
You might also look into firewall, MTU, and datagram fragmentation type stuff. -
I wanted to post that I did open a request to get DTMF line keys put into provisioner for Yealink phones and sidecars. Please consider voting for this and following the ticket progress:
https://2600hz.atlassian.net/browse/KAZOO-5088 -
I would go to help.2600hz.com and open a support ticket to get the PDF. They can also open a porting ticket if required.
-
Please do post an update if you try this again, without the list documents. As I am only a hack programmer I would like to see a working example of using this, even if it means you have to attach the list as a child of the call flow and not store it in the database.
-
The answer was that the ability to post lists in the SaaS environment is turned off. However, it sounds like they are considering something.
It was also suggested that the feature I was talking about might have been a community submitted module. However, when I look at the link I posted originally:
https://github.com/2600hz/kazoo/blob/master/applications/callflow/doc/cf_dynamic_cid.md
I thought it looked like standard functionality of the Dynamic CID module and not a community submission. In any case, I wanted to try getting the list examples in the bottom of the above article to work. Without being able to posts lists to Couch I suspect we will not be able to do this. -
Some uses cases include:
1. Client has multiple businesses running out of a single or multiple locations and needs to be able to change the caller ID depending on the call they are making. (Joes Catering, Joes Cleaning, etc.)
2. Client is an answering service for many DIDs in multiple locations throughout US/CAN and needs to be able to switch the caller ID depending on which state they are returning the call in. In my use case this is scheduling but I could see this for sales type organizations as well. -
It appears that a ticket was opened related to this on the reseller call:
https://2600hz.atlassian.net/browse/KAZOO-5100 -
Here is a 3CX article that talks about the BLF handshake process:
http://www.3cx.com/blog/voip-howto/busy-lamp-field/
Additionally, the Yealink handsets can create a pcap that you can open in wireshark, so if you have a recurring issue on a specific phone you can turn that on and then open the pcap in wireshark.
Wireshark has some built in tools for checking the flow of SIP traffic. Looks kind of like this: http://prntscr.com/cmnugv
Again, I am not an expert. -
I need to be careful as I am not a subject matter expert on this. However, this type of thing is likely diagnosed using a tool like wireshark. If you have a good understanding of the handshake you identify problems in the SIP responses.
I suspect in some cases your firewall can have an affect on this as well. Some firewalls do better than others with VoIP & NAT. You may also want to look at your NAT timeout values in the firewall. I am not sure if BLF registrations and re-registration times are different than the handsets register timeout.
https://doc.pfsense.org/index.php/VoIP_Configuration
The pfsense article above mentions UDP timeout. If your stateful firewall is timing out the NAT connection and not re-registering, I could imaging how that would cause a problem.
You may consider flushing the connection tracking table or reviewing the timeout and registration settings.
Here is a screenshot of the default Mikrotik "Connection Tracking" settings.
http://prntscr.com/cmnou5
Again, take this lightly as I am by no means an expert, however, this is the kind of stuff I would start looking at. If you were good at Wireshark, you may be able to confirm that the issue in on one side or another (client vs 2600) for example. -
I was able to get the call flow for the EXT -> Dynamic CID -> DISA working. I had to check the box that says "Keep the original Caller-ID". So far that has been reliable.
However, the call logs and history will only show calling this local extension instead of the actual number getting sent into DISA. While this is better than buying 2 or 3 times the devices it still does not feel like a "permanent fix". I hope there is a better way to do this soon.
Additionally, not being able to provision the DTMF key in the Advanced Provisioner adds complexity. -
I assume you are referring to the PREPEND + DISA method. I wanted to add that my testing with this technique was using a handset registered to the system and not from a cell phone outside the system.
-
esoare:
I have tried using dynamic_cid -> DISA, and it does not have any effect on the caller ID? I also ensured that the user, device, and the company did not have a default caller ID set to test. I also tried with and without a "blank" prepend ahead of the dynamic CID object to see if that would essentially "reset" the CID prior to hitting the other call flow modules.
http://prntscr.com/clg2ot
I did have the PREPEND + DISA mostly working, it was just not 100% reliable. It seems that 1-3 out of 15 calls will show incorrect caller ID.
I was hoping somebody could confirm that creating a single device and registering it on many phones will not cause issues. This would allow me to register one device per DID if I needed to as a last resort.
I am not sure why it is so hard to change outbound caller ID. This seems like a basic feature. What is the point of having multiple DID's if you can't easily use them? -
https://2600hz.atlassian.net/browse/KAZOO-5088
I created a JIRA ticket if anyone wants to upvote and follow for DTMF DSSKeys for Yealink phones. -
-
Can we create 1 device for each DID and register it on many phones without issue? The only use would be to change the outgoing caller-id with 1 click. Would this introduce any kind of problems?
-
Are we allowed to post lists in hosted?
http://api.zswitch.net:8000/v2/accounts/{ACCOUNT_ID}/lists
{ "data":{
"name":"Dynamic CID",
"description":"List of new callerid name and number entries ",
"list_type":"dynamic_cid"
}
}
I get:
{ "data": {
"message": "not found"
},
"error": "404",
"message": "not_found",
"status": "error",
"request_id": "sanitized",
"auth_token": "value"
} -
I am trying to get this to work. Here is some info:
https://github.com/2600hz/kazoo/blob/master/applications/callflow/doc/cf_dynamic_cid.md
I have tried posting a call flow like below but I may have mangled it some how.
{ "data":{
"name": "dynamic_cid_outbound",
"numbers": [],
"patterns":["^\\*9([0-9]{2,})$"],
"flow":{
"module": "dynamic_cid"
,"data": {
"_id": "cidlist",
"length" : 2,
"entries": {
"00": {
"number": "15173335555",
"name": "COMPANY NAME"
},
"01": {
"number": "15175553333",
"name": "NAME COMPANY"
}
}
}
}
}
}
In this example I dial *900 + the 10 or 11 digit phone number and the dynamic_cid module is still asking me for the caller id to use. If I enter one it ends up failing.
Is anyone using dynamic_cid in a call flow? Can you sanitize and post a working example I can hack/tweak? -
I wanted to use PREPEND + DISA to change the outbound phone number. It seems like it works 90% of the time. Then about 10% of the time it shows either restricted or 919-692-6062 or 919-692-6063.
Any idea why this happens? Does it have to do with the route the call takes or the 2600 LCR? -
We have this issue too. We have auto dealerships that fax large packets 20-30 pages. In our case the finance company does not really complain about it too much so it has not become a a major issue.
However, I consider this a "known issue" where the fax quality is not as good as it could be. I do not currently think this is related to the page counts. I also do not think this is an issue with the original PDF resolution or scanner settings. If I were to guess, this is an issue with the conversion process that PDFs go through during the email to fax and fax to email process. Perhaps some ghostscript settings could be changed that would have a drastic improvement. -
We have been trying to avoid giving end user's access to the Smart PBX and some of the other applications for this specific reason.
It would be best case if we could turn off the ability for clients to add Devices, Users, and DIDs to their accounts with out us knowing. If this is difficult, it would be helpful if we could at least be notified that a new DID, User, or Device has been created on an account so we could update our agreements. I do not see any kind of branding email template to this affect. I think all account administrators do get an email about a new user and perhaps new devices as it is now. However, I do not think any emails get generated for new phone numbers. -
When we setup a fax box, if we want to get fax sent receipts sent to the "original sender" we have to specify a recipient in the "Fax sent receipts" box in advanced call flows. In most cases we do not want to specify any specific email to receive all of the fax sent receipts. We typically only want the person sending the fax to get a fax sent receipt. The only way the sender gets the success email is if I enter an email into that box.
I am tempted to enter a dummy email to a domain I own, just so it gets bounced, and the original user still gets the sent receipt. However, this seems like a terrible idea.
Can you allow us to leave this global field "Fax sent receipts" blank or null and still send fax sent receipts to the original sender?
Skype integration
in Tips and Feedback
Posted
Example: http://www.yealink.com/product_info.aspx?ProductsCateID=1312
It would be nice if someone could explain the difference in the firmware. My distributor actually sells the Lync versions for $10 cheaper than the normal version of the phone. If everything is the same and it only "adds" Lync/Skype support, then maybe I should start buying those versions instead since we sell a lot of Office 365.