extremerotary

Can't even imagine my friend. It affected everyone I know in one way or another. Keep up the good work. Your community appreciates it!

I figured it wasn't just them. You're doing a huge service for your customers and making it much more cost-effective for clients to go after hotels, schools, and some retirement homes with this type of feature. Awesome to hear!

Just adding my 2-cents in here; It's not up to 2600hz to build this. Every carrier charges VoIP providers on a per-location basis. So even if 2600hz built something to make it look like it was all one, they would be getting charged on the backend so that wouldn't make sense from a business perspective. However, i know for a fact that since Ray Baum's Act, Bandwidth,com (3 day outage, i know i know) has been actively working on a dynamic E911 addressing service. In this way, 2600 could pass additional, more specific data to the PSAP using SIP headers (Like "room 121") instead of requiring an e911 registration per room. Last I heard they were close. Might be ready at this point. Bandwidth wasn't the only carrier looking into this, so since 2600hz aggregates multiple outbound carriers, i'm sure they are working with one to develop this dynamic e911 farther and bring that to their customers!

The error was that there were no valid candidates in the SDP because they were all local IPs. By applying the candidate ACLs, FreeSWITCH handles the SDP differently and is able to determine the public address to send the SDP.

Using the DND button could work here 😉 . Otherwise, yes, you'll need to create a TOD per user and a callflow for each to toggle the TOD rules. I know of no other solution

@FASTDEVICE James merged this PR for me a couple months back that was created specifically for your (and my) use-case. https://github.com/2600hz/kazoo/pull/5899 This allows you to branch to the cf_set_variable callflow module, set group_id, then go to the group. Then, in the CDRs, the custom_channel_vars will contain the variable with the value you've defined.

In my experience, the callflow ID in the CDR is the first callflow that the call followed, so if you ever branched the callflow for the telephone number to another callflow ID, the CDR won't illustrate that.

+1 for building an app. Some environment set-up instructions and basic uses of the monster APIs for gathering data from Kazoo.

@avig2 Polycoms - <attendant attendant.resourceList.{x}.address="{PRESENCE_ID}" (102) attendant.resourceList.{x}.callAddress="{*0+EXTENSION_NUMBER}" (*0102) attendant.resourceList.{x}.label="{TEXT_DISPLAY_ON_PHONE}" (John Smith) attendant.resourceList.{x}.type="automata" />

@mc_ That did it, thanks 🙂 For reference for the community - add this to your sipinterface_1.xml <param name="apply-candidate-acl" value="localnet.auto"/> <param name="apply-candidate-acl" value="rfc1918.auto"/>

@mc_ Do you have an example of this I can test with?

Hey guys, I see that you've moved from using the sipjs stack to using the jssip stack for the libwebphone. I cloned the repo, set up the basic wss and tried to make a call. The call is failing and FS is generating a 488 Not Acceptable Here. After some troubleshooting, i've determined the issue is with the audio candidate list having a private IP address a=candidate:329485039 1 udp 2122260223 192.168.76.132 61644 typ host generation 0 network-id 7 network-cost 50 Reading through the documentation for 3.3.X, i don't see anywhere to define a STUN server to correct this issue. I then went ahead and cloned an older version of the libwebphone that used sipjs 0.7.5. I was able to define and configure a STUN server, and I was able to make and receive calls, but I had one-way audio. My computer never played audio, but my cell phone always had audio from my computer. Using wireshark, I confirmed that FS is sending the audio back to my computer, but it's like the web phone isn't getting the remote audio track or something. Have you guys run into this before? Any suggestions on resolving either issue? I am testing with the rc3 version of kamailio and kazoo-freeswitch 4.3.-4. Kamailio is enabled for websocket role and TLS role, and i have configured certs on it and everything.

@AlexKazoo Hey Alex, Update the system schema file. I put a PR in for this a few months ago - i'll have to check on its status... system_schemas/media

Hey Jack, I don't believe that Yealink has this capability, and it's not really a function of Kazoo. Like, when a group is rang, all devices get the INVITE. When someone answers, they all get a CANCEL with a Reason that the call was answered elsewhere (i don't recall the specific cause code or text offhand). In this situation, Yealink says, "cool, that was answered elsewhere and not missed." When no one answers the group call, the CANCEL to all the devices contains a Reason NO_ANSWER. To the Yealink, this means that it actually missed a call and therefore presents it in the missed call list. This is a shortcoming of the device, and i'm not familiar of any device that operates the way you're requesting.

@esoare Yes, my testing would indicate that forwarding does not respect the ring timeout. I was hoping there was something else i could set...