Scott1234
-
Posts
210 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by Scott1234
-
-
Hey, was doing some work recently on moving all mailing to AWS SES and whilst checking how the PBX shapes up I am all ways losing 2.5 points on spam assassin due to HDRS_MISSP "Misspaced headers" I only get this on the pbx.
Can you guys look at the header structure and make it complaint ? just so we don't all lose 2.5 points out of the gate, also some of the base e-mail templates are missing alt text's.
<img src="https://portal.vodia.com/img/googleplay.png" width="135px" height="40px" /> <img src="https://portal.vodia.com/img/appstore.png" width="135px" height="40px" /> <img src="https://portal.vodia.com/img/msstore.png" width="135px" height="40px" /> <img style="border-top-style: none; border-right-style: none; border-left-style: none; border-bottom-style: none; max-width: 200px" src="data:image/png;base64,
-
Just came across this with a customer with power outage who had recently added the app usage as an option.
I normally use the "No agent has phone registered" logic to control what to do in a office power outage, where in the past this would divert off to a human answering service for this customer.
I assumed as they all had apps registered it would not follow that logic, but as the app is not treated as an active registration when backgrounding it treats them as not registered, even though technically its capable of pushing though to the app.
Is there any options I am missing to allow for this? for now I have just said to use "all primary agents are logged out"
-
Maybe we can use these new AI chatGPT type tools to build a UI
Galileo AI · Copilot for interface design (usegalileo.ai)
-
7 hours ago, WaveVoIP said:
Attached I have a screenshot of the user front end for v69. Blank canvas is an understatement. There is literally nothing on it anymore.. I had to make a ticket with support to make sure there wasn't an issue with the PBX. But they told me that it is in fact how it's supposed to look now. Which is a shame. I would assume most people who deploy and manage the system are not web designers and have little to no css / html experience, and don't have the ability to get someone to do it for them without hiring an external dev. So unless Vodia ends up changing the front end in a new update, or someone in the forum is kind enough to provide templates to change the front end to something that is nice and professional enough for us to actually use and put our names on to give out to clients. Then I would say most people will stay with v68 if the user front end is important to them. I know I will be until something about it changes.
Agree, I think the future of the PBX is in the web front end parts of it and mobile apps, and a good well documented API and heavy focus on integration's. I think desk phone's are dead in the long run which is why the UI and functionality with in those areas and apps is super important.
I said blank canvas as I hope its just because of the early release, or the focus is on the operators to make it make it look great. I started looking around to see what I can modify. But some good doc on it would be nice.
My 10 cents
-
9 hours ago, proskater1223 said:
Is there any screenshots of the new frontend? I don't feel like spinning up another machine to check.
wont win any thing in the looks department its a bit of a blank canvas would need to spend a long time to make it look good, deffo need some good doco on tweaking the assets for it.
-
For any one playing around early, if you were running modified appearance CSS on the login/welcome page you will need to make welcome.css in the pbxwebai folder as its now using this.
-
On 10/29/2022 at 1:58 AM, Vodia PBX said:
Might just be the form validation that stops you from entering alphanumeric. The Vodia API will take it.
Anyhow that being said, we plan to move on to passkey in 69 instead of 2nd factor. The whole 2nd factor was just a workaround for a flawed system where users have to come up with more-or-less random passwords.
Looks like the form validation accepts, it seems it was just Twilio that took longer in their backend before my number was truly enabled for Alpha ID. As I got missed call text messages come through with the name a few hours after posting this.
-
On the back of this is there any way to support Alphanumeric Sender IDs I tried to simply just input my Alphanumerica Sender ID as the ANI thinking that might just do it, but no go.
Great for 2-FA logins to present "VODIA PBX" etc...
Change the "From" number or Sender ID for Sending SMS Messages – Twilio Support
SMS seems to be fine in current config even when using 'Message Service'
-
On 10/17/2022 at 12:07 AM, Vodia PBX said:
On the top right of the text screen there should be a blue plus icon. For example, try texting into a page account it should be blasted out over the speakers.
No Plus icon, latest iOS tested in both dark mode and normal. Also adjusted screen font size to see if that made it disappear, no change either way. Pics attached.
Plus icon only appears after first message is sent or received, but no way to start your first message from the iphone.
-
FYI, if your extension uses the press 1 to connect feature for the cell phone that also gets used for teams on a direct extension call but not a call queue call, I think you would want to standardize that operation if its effecting it on one level but not the other bringing it more in line with how it works for the cell phone. Which also will stop the teams users voice mail from taking the call with in the call queue. Ideally direct extension calls are OK to go to teams VM without press 1, but not a call queue / ring group.
However, when it calls the team's client, it won't accept key input for pressing 1 to connect.
Key input works when the teams client makes the outbound call, so not sure what's going on there.
-
External Call -> Answered on Teams -> Click 'Consult then transfer' -> Key in another extension number click 'Consult' -> When answered 'Transfer' button appears Click 'Transfer' -> It keeps the Consult leg active and then begins the transfer in the background so that a second call comes in, cant it just complete the operation in one go like if doing it between two desk phones.
Like when I use two Yealink phones and do a consult then press the transfer button the call ends and is connected to the other person 'in flight' so to speak.
-
-
I have extensively tested with Teams on what does and does not work and the quirks to determine if it's usable for customers.
It seems the basics are all good. However, I sometimes get an OPTIONS warning on the MS admin panel, which is odd. It just randomly appears and will stay with a warning for ages, occasionally returning to normal.
My main question is about Consulted Transfers. It seems it will open up a new call leg when you click the transfer after the consult, keeping you on the line with the destination making one of you need to hang up or accept the next call.
Call to PBX -> Answered on Teams -> Consulted Transfer to -> PBX Internal Ext
Some reading here, is REFER active on this trunk?
Issues with call transfers - Microsoft Teams | Microsoft Learn
Not sure if its related to the change documented here, about replace headers being rejected from April 2022
https://learn.microsoft.com/en-us/microsoftteams/direct-routing-whats-new#replace-headers
&
Microsoft Teams Direct Routing & Audiocodes SBCs – Replaces Header – Michael Paul | @micoolpaul
-
Awesome, thanks !
-
Long time no post
PBX 68.0.16
I would prefer to setup teams end points correctly as per MS doco where you should be running a command like so,
Set-CsPhoneNumberAssignment -Identity xxx@xx.com.xx -PhoneNumber "61XXXXXXXXX;ext=801" -PhoneNumberType DirectRoutingThis will define the users "Assigned phone number" plus also their "Phone number extension" which displays neatly in teams so the end user can see their DID with in teams.
As the PBX will send the invite as 801@xx.com.xx to teams it won't ring the teams end point when setup as above unless the PBX extension is setup as the DID with the extension number as an 'alias' however this is not ideal config.
Is there a way to tweak the trunk settings with some advanced custom headers to send the invite based on the extensions defined DID failing that followed by the extension number for endpoints that might not have a DID?
Thanks
-Scott
-
Tested didn't work, oh well. Was worth a try
it wont execute. EXEC format error. IO looks cool but don't think any one sells to AU
-
Hey just wondering if you can compile a aarch64 build, I want to test some thing out
I have proper shell access on UniFi dream machine and can install what ever I want its got decent hardware specs and could be a cool way to run a basic pbx for customers.
-
Hey,
Just letting you know I have been using the app for a while iOS and a few clients and its been great cant fault its operation.
What would be cool at some point which you are no doubt onto is when doing transfer being able to see the user list and pick from there instead of having to know the extension number.
Otherwise great, backgrounding works perfect.
-
I see the SMS ANI on the agent group is just for when the agent sends out a SMS it will go out as that ANI.
What would be cool, would be if that also works for inbound messages, meaning. Who ever is logged into the agent group for that day could receive the SMS's and or reply, and obviously some kind of sync so that any other agents can see the message stream?
-
How's this PhoneBridge re-integration tacking ? keen for an update so I can let eager customers know how its tracking.
-
On 10/30/2019 at 5:21 AM, Vodia PBX said:
AFAIK this is currently under review and should be approved shortly.
Awesome ! will it require a PBX update or is it all ZoHo side with being published.
-
3 hours ago, Vodia PBX said:
There was a bug in some older versions in that area - what version are we talking about here? The caller-ID is indeed a nuisance, we also have to look into this generally with the click to dial.
63.0 (CentOS64)
-
10 hours ago, Support said:
Would the Agents not remember from the AG number being dialed, which agent that call back belongs to? Having the name feature does help make it clearer, but AG number should be fine too no?
No we normally have buttons setup with nice easy to remember names for login / log out functions or agents are just permanently logged into groups. So they have no need or want to remember a number code. Using the group name would be far more intuitive option for a user like how hunt groups and agent groups work when they dial up the phone.
Maybe the settings controls for this could be embedded into the 'Outbound Calling' tab of the agent group setup. To allow for customisation of the call back name.
-
Hi,
I feel this to be strange behaviour and put forth for your consideration for tweaking the operation.
When using the call back feature if the agent hangs up the call first and or does not let the menu play out to the 'press #' to check the rest of the list the system will keep calling back even if there is no more calls in the list. Can it not just assume the operation as being closed if no further calls are in the list no matter who hangs up?
Also, at the moment when a call back operation happens the caller ID comes up as *55xx(xx = agent group number) and wont present any group name identification.
Would it be possible to display the agent group name maybe annotated with 'CALL BACK' or some thing similar such as "CALL BACK (XYZ AGENT GROUP name)" so end user has some idea of what type of call back it might be verses seeing the star code only?
Thanks
System SMTP headers Misspaced
in Email Topics
Posted
I think its the placement of headers but I could be wrong,
It should be,
From: To: Subject: Date: Message-ID: MIME-Version: Content-Type:PBX is,
Content-Type: Subject: From: To: Content-Transfer-Encoding:base64 Date: MIME-Version: