Scott1234

Thanks, the zoho fix will be apricated by my zoho customers that log in and out of agent groups a lot. Does this teams related fix's fix being able to use teams call park? Label for night more active/inactive was wrong - Does this mean the service flag naming difference between auto attendant and call queue?

FYI I think that post was before the 6.0.4 version it was the new version before the new new version ... ha ha. 6.0.4 is ok at the moment.

FYI, setting the Failover behaviour 5xx and 408 only seems to still trigger with a 603, I have noticed this with other code too that are not 5x 408

try this one. ![0-9]{6}7873!100!

Yep same for me. Seem's as you say, You need to go to the windows notifications centre and turn off Notifications for the Vodia Phone app, for now.

Using the latest app on v68 drops it windows 11, I have to turn off notifications for the Vodia App to stop it.

Just had a random thought, in the PBX it would be nice to have a column called something like "Ref" for reference to click to see everywhere that object is referenced/used. FortiGate's do it so you can quickly find stuff where you have set it up and using it and thought that would be handy on the PBX. Such as finding everywhere a service flag has been set to be used ... Any ways that's it

In the redirection area of both is where I am comparing, only. They work differently to each other.

Is there any way I can experiment with my own JS script fix's? for the above as I really want to resolve the dial issue when defining area code for AU with regards to 13/1300/1800.

Hey, this one has all ways thrown me, I think it's been around for a while and needs addressing. There is a difference between Call Queue service flag logic and Auto Attendant service flag logic. (Manual flag testing) In a Call Queue when you set "When service flag is active" and your flag is clear it will trigger the redirection flow. In a Auto Attendant when you set "When service flag is active" and your flag is clear it does not process the redirection flow. Based on the language the Auto Attendant is doing it correctly and the Call Queue is not. v68.0.32 confirmed.

On the topic of teams, I can never get the SBC to show up with options showing as working on the MS Admin console, ever. On my test pbx (default sip ports) I can get TLS showing as working on MS end but not options. On my production system that uses non-standard sip ports, I can't get TLS or OPTIONS to show as working. Both work with regards to calls in and out, on the non-standard port one I found I had to define the port in the contact header on the trunk setup to get it to work, but yeah never had luck with TLS and OPTIONS. It's why I was trying to install SNGREP and sniff general sip messages to find out what's going on the options requests. Any input would be appreciated

Not that I can see, you can compile it with openssl or gnutls and run it with a, -k flag to define rsa private keyfile, but using the keyfile setting on the pbx did not help. I just found this in their, FAQ page. says, I can't see TLS flows even using the private key sngrep only support a couple insecure cipthers (TLS_RSA_WITH_AES_128_CBC_SHA, TLS_RSA_WITH_AES_256_CBC_SHA and TLS_RSA_WITH_AES_256_GCM_SHA384), and needs to capture the initial TLS negotiation in order to decrypt the conversation. If you're using TLS v1.2 or greater with a DH or ECDH cipher, decrypting is impossible as these ciphers implement Perfect Forward Secrecy. So maybe no go.

Has anyone got SNGREP to work with TLS key support? on the pbx. GitHub - irontec/sngrep: Ncurses SIP Messages flow viewer Screenshots · irontec/sngrep Wiki · GitHub It's my fav goto sip message explorer but since I have been on a mission to go full TLS and SRTP I am now in the dark but want to enjoy this tool again when needed for support. EDIT > I know I can do pcaps from the pbx and get the decode, but sometimes this tool is better to use when listening globally, not just specific to the one call.

no worries. Just thought I would check.

Looks interesting, nice work!

Just looking for a bit more info / guidance on this option under Settings -> Network -> Ports The Read content for global and domain files, the option, attempt to read files from tenant-specific directory. Not documented. How do we make use of this and allow for a customer directory? I ask as when using a wildcard DNS setup for customer domain ID's when you want to establish a team's SBC you need to verify the domain on MS and in doing so you need to create a static txt record that then breaks the wild card option for that domain, if I can place the txt file verification on the PBX side instead in a customer folder that is read when the customer URL, i.e. https://customer.pbx.com/ms12345.txt is requested I can avoid having to statically set DNS to auth the SBC on MS. I know way back when in the old days I recall a folder on the PBX with copies of all the config files extensions generated etc with the customer id as the folder, is that was this is? Would this scenario work with this option enabled?

I find it to do with, explicitly list addresses for inbound traffic. The addresses included by default in the trunk are outdated. The list should be, for most. 52.112.0.0/14 52.120.0.0/14 https://learn.microsoft.com/en-us/microsoftteams/direct-routing-plan#microsoft-365-office-365-and-office-365-gcc-environments-1 Secondary to that it's typically something to do with the Rewrite global numbers section of the trunk and country code and Trunk may terminate calls for remote systems I still think their implementation of how-to setup the user is wrong, but the pbx is the problem and needs the team's part reworked. We should be able to setup the user elements as, Set-CsPhoneNumberAssignment -Identity user4@contoso.com -PhoneNumber "+14255551000;ext=1234" -PhoneNumberType DirectRouting So that the users DID can show up in their teams client. https://learn.microsoft.com/en-us/powershell/module/teams/set-csphonenumberassignment?view=teams-ps#example-6 https://learn.microsoft.com/en-us/powershell/module/teams/set-csphonenumberassignment?view=teams-ps#-phonenumber I still have issues but with parking and retrieving with in teams side not working and the caller gets dropped. Transferring / consult transfers are finnicky when it comes to external to the system transfers. FYI Trunk may terminate calls for remote systems must be enabled to allow external transfer function to work. I think its best only used to make and take calls, if you need to start parking and transferring it becomes a bit finnicky, receptionists stay away. If anyone can share me a full config guide of it all working, I will be happy.

It could be to do with sleeping tabs that a lot of browsers use now a days, you can explicitly define what not to ever sleep. Or use the stand-alone web app from the app store, I have found this works better sometimes, when it comes to users and different org security policy's and making sure the user knows to allow access to microphone / speaker etc, the standalone app makes it somewhat full proof.

Ok, I might wait for the non-beta, so I can see release notes of changes. Unless you can provide. Cheers.

68.0.32 , can we get the fix added to the next build of that? As I am not ready to have customers move to 69 with regards to user interface.

Thanks, I will check into SNI support on the external SBC. As I prefer to use "Ignore Packets" setting. This was working fine on the old version, is this part of a fix to support secure TLS renegotiation properly as for why its stopped working on this version? Back to call Q and not ringing, I have to set the "Extension feature set" as "Call Queue" Agent vs "Regular Extension" for it to ring, is this the expected setup now? what happens if that user also wants teams? what is the new "all function levels" setting?

When I upgrade from 68.0.32 to 69.1.1 I can no longer receive inbound calls from the external SBC. (This is not specific to 69.1.1, it's just the first time I have tested an in-place upgrade or 69 at all) What is it looking for that is different to 68.0.32 with regards to client hello ? I use TLS everywhere, end to end normally. Switching to UDP will make it work. [9] 15:48:47.759 SIP xxx.xxx.xxx.xxx:43985: Receive Client Hello(0303D0F6..00000000)ⓘ [9] 15:48:47.759 SIP xxx.xxx.xxx.xxx:43985: Client Hello TLS version(0303)ⓘ [6] 15:48:47.759 SIP xxx.xxx.xxx.xxx:43985: Session DFFC6302..7562B1F0 not foundⓘ [9] 15:48:47.759 SIP xxx.xxx.xxx.xxx:43985: Matched cipher suite TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256ⓘ [9] 15:48:47.759 SIP xxx.xxx.xxx.xxx:43985: Enabled secure renegotiationⓘ [8] 15:48:47.759 SIP xxx.xxx.xxx.xxx:43985: Client hello did not match any known address, ignoring itⓘ Edit - When I make a call q for testing and log myself in my phone wont ring, I just gets the hold music and waits in the queue, I don't get it? all the settings look fine. Direct calls to phone work or hunt groups etc. Has there been some fundamental setting changes changed that I am missing? I could not spot anything.

Thanks, I checked not the case here. Plus also its random some times ok some times not but very random when it happens. Have not seen it for a while again, but will be on the look out.

I decided to finally start testing 69 on 69.1 Am I meant to be able to drag / drop calls into park ? in the web interface.

As for road maps, the best one I have seen in a while is by a local digital bank, I thought the layout was great. The Tree of Up — Up Product Tree