Jump to content

All Activity

This stream auto-updates

  1. Today
  2. Yesterday
  3. Hi, We setup a single server install of Kazoo 4.3 with couchdb 2.3 to build our web app against the API. It all works, can make and receive calls, use the inbuilt apps to create ring groups etc. However after 2-3 days the database is losing accounts data and we need to create a new account. Any ideas why this would be? Thanks
  4. Last week
  5. Hi Guys, Is there a way to add the favorite key index for the directory on a yealink phone? I know we can do it on Polycom VVX. Is there any way we can do it on Yealink phones? Thanks Dhruv
  6. Thanks! Yes, that seems to work, but only for the traffic to/from the carrier. SIP clients dosen't have any sound, because the internal IP isn't reachable from the outside. I will start a new thread with that issue: https://forums.2600hz.com/forums/topic/12691-dual-media-gw-address-signalling Br Tomas
  7. Hi Mark, Thanks for the reply. Unfortunately we are trying to win a 25 seat opportunity and it involves replacing the existing call center product the customer is using and it currently rings all of the available agents simultaneously. Why is ringing all of the agents highly discouraged? What if there are only 3-5 agents? How do you set up the queue to be able to ring all the users. If we can demo this capability we can win the deal :-) Thanks, Chuck
  8. Earlier
  9. I believe you can use the internal kamailio IP instead
  10. @rhys Hi Rhys, Did you find any solution to your problem? Tommy
  11. Hi again! I have the same issue again, now with another carrier that connects via VPN (AWS Direct Connect) and not through the public internet. They can't reach our external IP, so it's not useful here. What IP should I use in the configs? Br Tomas
  12. Hi I have enabled RTCP in FS, it is working fine however variable_rtp_audio_in_xxxx are not shown in Kazoo call logs. What else need to be enabled in order those variables to be seen by Kazoo? Thank you
  13. One day, I might do a part 2, or even an updated version for more recent versions of couchDB :) If only I had more hours in the day to do all the things I wanted to do :/
  14. I have recently started to investigate to figure out how I can instruct kazoo to route the call to my specified resource from Click2Call API. With suggestions from 2600hz community forum and after some trial & error, finally, I am able to design a solution to achieve this goal. Let’s first understand my goal in detail. For example, I have two remote PBX (asterisk1 & asterisk2) which I have added as resources in kazoo. Both asterisk1 and asterisk2 instances have the same extension 70003. Now if I use clicktocall for dialing 70003, how can I instruct kazoo from clicktocall so that it will dial 70003@asterisk1, not 70003@asterisk2? As I am calling ClicktoCall API from my web app and resource selection logic is also resides in my web app, somehow I need to tell ClicktoCall API which resource to route the call while invoking from the web app. To accomplish this, I have used The rules key on the resource which matches the number dialled. Actually, I have added a unique prefix before the regex pattern in the rules key for each resource. The rules key supports capture groups, in parenthesis. Those will throw away whatever is outside the parenthesis before sending it to the resource. As per my example, For the Asterisk1 resource, I am putting “1(.{5})” for the value of rules, and For the Asterisk2 resource, I am putting “2(.{5})” for the value of rules. So when my web app hits my clicktocall endpoint with the dialled extension of 270003, it will get sent through Asterisk server #2 as 70003. When my clicktocall executes 170003, it will send the call to 70003 on Asterisk server 1, etc. Resource Details Details of my resource setup are as below Asterisk1 { “data”: { “name”: “Asterisk1”, “format_from_uri”: true, “rules”: [ “1(.{5})” ], “flags”: [ “Use_Asterisk1” ], “weight_cost”: 60, “formatters”: { “diversion”: [ { “match_invite_format”: true, “direction”: “outbound” } ], “outbound_caller_id_number”: [ { “value”: “70001” } ], “outbound_caller_id_name”: [ { “value”: “kazoo” } ] }, “gateways”: [ { “caller_id_type”: “external”, “channel_selection”: “ascending”, “codecs”: [ “PCMU”, “PCMA”, “OPUS” ], “custom_sip_headers”: {}, “emergency”: false, “enabled”: true, “endpoint_type”: “sip”, “format_from_uri”: true, “invite_format”: “route”, “password”: “asterisk1_password”, “prefix”: “”, “progress_timeout”: 30, “realm”: “asterisk1_ip”, “server”: “asterisk1_ip”, “skype_rr”: false, “suffix”: “”, “username”: “asterisk1_username”, “force_port”: false, “port”: 5060 } ], “emergency”: false, “enabled”: true, “from_account_realm”: false, “grace_period”: 5, “rules_test”: [], “id”: “c1ad847e401cb9c7a3f264a2840b2fff” }, “revision”: “26-db769ea7891fb82a1d2425a2fe269814”, “timestamp”: “2021–11–01T20:20:14Z”, “version”: “4.3.140”, “node”: “yMeslQexQufV5c-zOCJ0Ow”, “request_id”: “d20e9b4223a47931f4d19b0a5012ddc8”, “status”: “success”, “auth_token”: “auth_token” } Asterisk 2 { “data”: { “name”: “Asterisk”, “format_from_uri”: true, “rules”: [ “2(.{5})” ], “flags”: [ “Use_Asterisk2” ], “weight_cost”: 70, “formatters”: { “diversion”: [ { “match_invite_format”: true, “direction”: “outbound” } ], “outbound_caller_id_number”: [ { “value”: “70001” } ], “outbound_caller_id_name”: [ { “value”: “kazoo” } ] }, “gateways”: [ { “caller_id_type”: “external”, “channel_selection”: “ascending”, “codecs”: [ “PCMU”, “PCMA”, “OPUS” ], “custom_sip_headers”: {}, “emergency”: false, “enabled”: true, “endpoint_type”: “sip”, “format_from_uri”: true, “invite_format”: “route”, “password”: “asterisk2_password”, “prefix”: “”, “progress_timeout”: 30, “realm”: “asterisk2_ip”, “server”: “asterisk2_ip”, “skype_rr”: false, “suffix”: “”, “username”: “asterisk2_username”, “force_port”: false, “port”: 5060 } ], “emergency”: false, “enabled”: true, “from_account_realm”: false, “grace_period”: 5, “rules_test”: [], “id”: “c1ad847e401cb9c7a3f264a2840b2fff” }, “revision”: “26-db769ea7891fb82a1d2425a2fe269814”, “timestamp”: “2021–11–01T20:20:14Z”, “version”: “4.3.140”, “node”: “yMeslQexQufV5c-zOCJ0Ow”, “request_id”: “d20e9b4223a47931f4d19b0a5012ddc8”, “status”: “success”, “auth_token”: “auth_token” } So if my web app decides, it needs to make call to 70003 extension of Asterisk1 instance, then it will append prefix 1 for Asterisk1 (Setup in rules for Asterisk1 described earlier) before the extension 70003 in the value of contact field. https://crossbarserver.tld/v2/accounts/5123456789098765432abcd/clicktocall/my_cool_pivot_c2c/connect?contact=170003 Similarly, if my web app decides, it needs to make call to 70003 extension of Asterisk2 instance,then it will append prefix 2 for Asterisk2 (Setup in rules for Asterisk1 described earlier) before the extension 70003 in the value of contact field. https://crossbarserver.tld/v2/accounts/5123456789098765432abcd/clicktocall/my_cool_pivot_c2c/connect?contact=270003
  15. This is a video edition explaining the install: https://www.youtube.com/watch?v=yA55nkQkxCI
  16. You can also find out more here: https://forums.2600hz.com/forums/home/
  17. Other that reviewing what documentation you can find on 2600hz's site, poking around the UI and trying things is probably your best bet.
  18. Hi @Joe Baran Thank you for fast answer. So, is it there some feature guide or product guide to explore deep dive ? Best regards, Daniel Sobrinho
  19. https://docs.2600hz.com/sysadmin/doc/install/install_via_centos7/ works pretty well for what you're after I think.
  20. Ring all is possible, with limitations (iirc we support a max of 10 agents). However it's use is highly discouraged.
  21. Hi guys, I am newbie. Is there an updated procedure for CentOS 7, with rich in details or a trial version iso ? Best regards Daniel
  22. Happy Holidays! Our offices will be closed January. 17, to honor Martin Luther King. If you experience major operational emergency and support is required, Please first submit a ticket to support@2600hz.com then call our support line at (415) 886-7950 to escalate it. For all other support requests, you may submit a ticket by emailing support@2600hz.com and your ticket will be handled when we return on Tuesday, July 6th.
  23. Happy New Year! Our offices will be closed Dec. 31, to welcome 2022. If you experience major operational emergency and support is required, Please first submit a ticket to support@2600hz.com then call our support line at (415) 886-7950 to escalate it. For all other support requests, you may submit a ticket by emailing support@2600hz.com and your ticket will be handled when we return on Tuesday, July 6th.
  24. Happy Holidays! Our offices will be closed Dec. 24, to honor Hannukkah, Christmas, and Kwanzaa holidays If you experience major operational emergency and support is required, Please first submit a ticket to support@2600hz.com then call our support line at (415) 886-7950 to escalate it. For all other support requests, you may submit a ticket by emailing support@2600hz.com and your ticket will be handled when we return on Tuesday, July 6th.
  25. until
    Thursday and Friday is Thanksgiving weekend in the US. Our offices will be closed. If you experience major operational emergency and support is required, Please first submit a ticket to support@2600hz.com then call our support line at (415) 886-7950 to escalate it. For all other support requests, you may submit a ticket by emailing support@2600hz.com and your ticket will be handled when we return on Tuesday, July 6th.
  26. Hi @Izabell balash, Just a question- Can we ring all of the call center agents simultaneously? In other words ringing on multiple available agent's devices. For example a clinic would want the patients to be able to hear what line in the que they are. Thanks Dhruv
  27. Hi @mc_, thanks for the help. There were a couple of instances where the reorder app seemed to be getting in the way, and wasn't something we specifically needed, so we tried disabling it and everything seems to be working so far.
  28. Hi Roger, Sorry didn't see your response. Matches occur in my understanding in the order in which they are in the JSON for the call flow. If using Monster UI then from left to right as you add them. 1. I am not sure I understand your question, here? 2. You should create one for each date, for instance each Holiday, then create Temporal Rule Sets (https://docs.2600hz.com/supported/applications/crossbar/doc/temporal_rules_sets/) to group them together as one object. This allows you to have a Holiday List you can add to. To possibly answer question 1 here are a couple examples that might help. Christmas Day { "data": { "time_window_start": 0, "time_window_stop": 86400, "days": [ 25 ], "name": "Christmas", "cycle": "yearly", "month": 12, "ordinal": "every", "interval": 1, "start_date": 62586115200, "id": "1e7ced7206b94b575a267db4138ace7a" } } Thanksgiving { "data": { "time_window_start": 0, "time_window_stop": 86400, "wdays": [ "thursday" ], "name": "Thanksgiving", "cycle": "yearly", "month": 11, "ordinal": "fourth", "interval": 1, "start_date": 62586115200, "id": "e1037a00738d9ebe6422c761456991e9" } }
  1. Load more activity
×
×
  • Create New...