VodiaUser

I found out somethng new regading the Echo: It will also occur if I use the linphone client if I make an outgoing call. If a call comes in there is no echo. The same applies to the Vodia App. The trunk uses PCMA only. I made a pcap capture. The vodia and the linphone will also use PCMA for the outgoing cal. So, the codec seems not the problem. I then tried opuc codec for an outgoing Call from my mobile: one way audio: The remote party can hear me, I have no audio. The same for G722.

A few more observations: I tried to set the ILBC codec as the only active codec for mobile apps. However when using the Vodia app for an outging internal call the used codec is anyway PCMA (internal call). When using linphone and enabling only ILBC there is no audio. I then enabled opus. This works with my Deskphone (yealink VP59, it is able to do opus). Does the PBX include the capability of audio transcoding? Or do I need an extra transcoding software? Regarding roaming between WiFi and mobile network. The Vodia App seem not to include this capability. Correct? 3CX is able to do roaming during a call, not perfect, but it does. Missed calls: with 3CX i have about 90% success then using the app. With Vodia about 60% of all calls will be received. I like the feature of the Vodia app to use the Andoid phone system. With 3CX initiating a call by tapping a number will instead trigger the native android phone instead of the 3CX app. What does not work however is clicking a number from a missed call email on the PC. I get a dialogue asking me an authenticaton challenge, but when I enter my credentials it will only ask again. I have to copy an paste the number to make the call. Using an iphone (2022 SE): No Echo!

speaker is in normal mode. The echo also gets wors if I use the speaker mode. Android device is a Sony XZ1 Compact. Stock Firmware - latest available Andrdoid 9. The Vodia app uses the Systems native dialer, which also jumps in the foreground. However I initiate the call from the Vodia App (originating the call from the native Dialer will not work because there then the Vodia App crashes (I already submittet a the crash report), but that does not make a difference in my opinion. then I used Linphone for a test. When using this sip client there is no echo at all (regardless of the linphone settings "use software echo cancellation").

Understood. It currently works with the "15" but the 15 is the extension number. I would rather like to send the call to the ring group. And this does not work.

I currently try to use Vodia instead of a 3CX System. While many things do work much better then with 3CX, I have problems with the Android app. One of these problems is that the other party will tell me they are unable to speak to me because of an Echo. I do not have any options I could choose from to supress this Echo. It does not happen when I use the buiilt in mobile phone. Also when using a real phone there is no Echo. Is there anything which could be done to fix this?

The Call fllow is like this: incoming call goes to a ring group (ext. 30), if not answered it is transfered to this IVR. If there is no respone or if the caller presses "1" The call should be transfered again to the ring group ext. 30. However, If i do this instead of "15" the call will not be sent to the ring group. Instead it will go to the IVR.

Ich habe ein Exchange one Premises (wie ganz am Anfang schon geschrieben. Daher ist das hier nicht zutreffend. mit Exchange on Prem muss es auch gehen und zwar mit Active sync, aber mit Bug gehts eben nicht.

I tried to send callers after a timeout of 60sec back to a ring group, but it does not work. Callers will be sent instead back to where they came from (an IVR Node). If I replace the Destination with the number of an extension it will work. Is this expected behaviour?

noch ein zusatz dazu: ein anderer User, der funktioniert, aber der hat nur 8GB potfach und nur 33 Ordner, das ist zumindest ein Unterschied. Der erste User (ich) der hat 159 Ordner und ca. 48GB - was aber IMO nichts ungewöhnliches ist. Weiterhin: da ist ein Bug.

Ich denke ich habe es herausgefunden und einen Bug gefunden. der client (die PBX) kann sich fehlerfrei anmelden. Und dann fragt die PBX die ordnerliste ab. Der in frage kommende Ordner sind die Kontakte. Im EAS protokoll sieht das so aus: <Add> <ServerId>27</ServerId> <ParentId>0</ParentId> <DisplayName>Contacts</DisplayName> <Type>9</Type> </Add> Jetzt, so wie ich es jedenfalls begriffen habe sollte der client den Ordner holen. Dabe muss man die ServerID als CollectionID angeben. aber die PBX schlckt: <?xml version="1.0" encoding="utf-8" ?> <Sync xmlns="AirSync:"> <Collections> <Collection> <SyncKey>0</SyncKey> <CollectionId>K</CollectionId> </Collection> </Collections> </Sync> "K" ist nicht 27, und ausserdem gibts die ID nicht. EAS sagt dann der PBX, Fehler, und auf wiedersehen. SyncCommand_OnExecute_Exception : Microsoft.Exchange.AirSync.AirSyncPermanentException at Microsoft.Exchange.AirSync.SyncCollection.OpenSyncState(Boolean autoLoadFilterAndSyncKey, SyncStateStorage syncStateStorage) at Microsoft.Exchange.AirSync.SyncCommand.SyncTheCollection(SyncCollection collection, Boolean createSubscription, Boolean tryNullSync) at Microsoft.Exchange.AirSync.SyncCommand.OnExecute() BadCollectionIdInSync2 LogicalRequest : <?xml version="1.0" encoding="utf-8" ?> <Sync xmlns="AirSync:"> <Collections> <Collection> <SyncKey>0</SyncKey> <CollectionId>K</CollectionId> </Collection> </Collections> </Sync> Command_WorkerThread_Exception : --- Exception start --- Exception type: Microsoft.Exchange.AirSync.AirSyncPermanentException Exception message: Exception level: 0 HttpStatusCode: OK AirSyncStatusCode: Sync_ObjectNotFound ProtocolLoggerString: Sync.ObjectNotFound3 XmlResponse: <?xml version="1.0" encoding="utf-8" ?> <Sync xmlns="AirSync:"> <Status>8</Status> </Sync> Sieht nach einem Bug aus. Warum es überhaupt bei jemand anderen funktioneren kann - ich weis es nicht, denn wie man von 27 auf "K" kommt ist schwer vorstellbar. Aber "K" ist eben falsch.

Ich habe noch nicht so viel Erfahrung mit dieser PBX. Also, es kann sein ich habe etwas einfaches übersehen? Jedenfalls, wenn ich versuche das Feature ActiveSync zu verwenden, dann endet das immer mit eine Fehlermeldung: "Activesync Status Error: Failure 2. Status =" Vodia PBX Version 69.2.1 (mit V.68 hat es auch nicht funktioniert, älter habe ich nicht getestet). Der Server ist ein eigener (im gleichen subnetz mit der PBX) Exchange 2013, alle installierbaren Patches sind installiert. ExchangeAS funrktinoiert mit diversen Mobilgeräten. Autodiscover geht, auch mit einem Test via Microsoft remote connectivity Analyzer Die mailbox wird wohl auch geöffnet. Aber dann fehler s. O. Ich habe mal das aus dem log der Tel. Anlage extrahierte Protokoll angehängt - hoffentlich befreit von allen persönlichen informationen. Vielleicht hat ja jemand eine Idee? Danke. ex-as-log.zip

Turned out it was my fault: A second view on the problem after a healthy sleep revealed I just made a typo in the router/firewall UI. Where I blindy typed the rtp port range from 49152 to 65535 the input was used to redirect a single port to another port. So, the STUN messags of the client never reached the PBX. I now made the correct setting in routers UI where I can forward a port range, and immediately it worked as expected. As a side note: the RTP port range in the link above seems to be outdated. instead of 64512 it should be 65535 (I found that in another howto).

I am a new Vodia User. I did setup a test environment on a Win Server 2016. As long as I use the PBX from the internal Network everything is fine (I am able to autoprovision phones, I can make and receive calls from the trunk I did setup, also can make and receive calls to an Android phone in the Lan). However when I try to use the Vodia app to call an extension from android connected to the mobile network, the call arrives and I can accept it, but there is no audio. I tried a different Android phone, also an iphone, also a different moblle provder. The Vodia PBX is version 68.0. The OS I installed is a fresh installed Server 2016 with all updates running in a VM. Connection to the internet is made a dedicated static IP. I forwarded ports 80, 443, 123, 5060, 5061, 49152–64512 as documented here: Configuring your firewall for remote users | Vodia Blog, The Server has only one tenant. I have installed a valid certificate, login using barcode includd in the welcome message works fine. Also I tried instead of using the "private/public" variables in the IP Routing list I tried the actual IP adresses. No change. I captured a session. I can see rtp packets originating from the phone inside the network going to the PBX. When I playback the packets they sound good. But nothing from the remote end. I enabled the call recording feature for both extensions. Again the recording of the phone inside the LAN is good, but the recording of the remote extension is empty. No Audio, in either direction. Looks like something trivial I did oversaw or I do not know. I have another PBX (3CX) running on a different VM and on a different external IP. Works good since several years. I have not setup any frewallrule for outgoing traffic. I did however restrict admin access to the management console to the local network. Is there a switch I have to flip? Thank you for an Idea.