shapa

OK, thank you for the clarification. You just lost the client (paying yearly a few thousand $), migrating to 3cx, much cheaper and functional.

Upgraded to 5.3.0 - license is not working anymore. What is the reason?

One small add-on: 600 is not enough sometimes, >600 (like 660s) works Yes, I made a change manually and it works now. iOS clients are able to receive calls for a whole day...

So, "default" is not working at all - iOS client stopping to complain, but all incoming calls are not going to iOS application (neither foreground nor background). Please add 600s ASAP as we've got a lot of users who is complaining about this issue (iOS SIP) It should be just a few seconds for you to "fix" it. Thanks in advance. Screenshot is here: https://www.dropbox.com/s/kicnpegzg886f6i/Screenshot%202015-05-17%2014.15.46.jpg?dl=0 p.s. manual change in pbx.xml seems to work (<nat_tcp2>600</nat_tcp2), but it should be supported officially

iOS applications requiring for backgrounding support at least 600s refresh time. Right now it is not possible to set (maximum available setting is 180s), only "default" settings works, but we'd like to be able to control refresh period (default == client control, right?)

Some workaround I found: 1) create a "inter-domain" trunk with 127.0.0.1:5060 GW address, set SIP Caller-ID Presentation as a P-Asserted. 2) rewrite number in a dialplan with a correct destination domain, i.e. : "90;Inter-Domain;;7xxx;"sip:\1@rdata.com;user=phone";;false" Loopback (even with rewritten destination) doesn't work, but "dummy" trunk works.

Some interesting issue. We've got some important clients who'd like to call different domains (company branches) without any prefixes to add (this is mandatory) and be able to return call. The issue is that it is not possible to specify loopback lookup order or include / exclude domains. One customer used a lot of overlapping numbers and unfortunately PBX is looking up for a number at this domain before others. How to workaround this situation? Ideally, some "local group" functionality should be implemented - i.e. domains added to a group are only included in a loopback. Something like VRF instance on a router. Other option is to be able to specify destination domain in a dialplan, it will also work fine. Configurable lookup order is also a solution (but not the best)

Yes, all assumptions are correct. The issue is also confirmed by other PBX users - no sound with WebRTC calls. Yes, mic use is allowed - Chrome asking about that.

Nothing special, except preload.js:578 Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user's experience. For more help, check http://xhr.spec.whatwg.org/.

Mac Chrome: Version 41.0.2272.53 beta (64-bit) Windows Chrome: Version 40.0.2214.111 m Neither of them works, full silence.

It works now, thank you! Another issue - no audio with browser calls (chrome, firefox) It used to work on 5.2.4

5.2.5a - the same issue.

We've got exactly the same issue - static noise. Extremely bad software release without proper QA. It's not only happens with a "hold" operation, but second line call, etc. All phones (software clients, snom, grandstream, cisco, yealink, etc). The problem is at the PBX side, 100%. Should be fixed ASAP.

Additionally, provisioning parameters are insecure. Should be changed to: port 5061 tls sips It works fine in case of manual adjustment

Ok, provisioning works (tested WAN) fine. LDAP address book doesn't work Settings seems to be OK, but no contacts shown. Snom phones works fine. How to fix? https://www.dropbox.com/s/nn7g4dbi73awc3i/Screenshot%202014-07-04%2017.35.22.png ... OK, realized there is a different app for LDAP contacts - "LDAP Book". It works fine.

Sounds tempting Ordered one phone on Amazon to check tomorrow how everything works

GXV3240 - how to? LAN only or WAN is also supported? Many our customers are asking about this phone to support What about address book? Is it supported as well?

OK. As the only way to open a ticket is to pay for the support, I paid 99$ (we are going to buy more licenses anyway) and sent email to "support@vodia.com" Please let me know in case there is any other address to use (or trouble-ticket system). *** We are using the "try loopback" function in the dial plan

We already discussed that. Your suggestion is ridiculos (sorry). There is a big holding company with many departments (subsidiaries). In all versions <= 5.1.1 short numbers calling works fine (inter-domain). I.e. 3000 <-> 7500 - not a problem. What do you suggest? To change numbering? Simply just because you decided to broke this functionality for some reason? Virtually any PBX software (including 3cx, call manager, etc) could easily do that. Please explain, how our customers can continue to use inter-domain calls from SIP phones using short numbering / internal extentions. All suggestions made earlier by you or your colleagues are not working.

Guys, As I could see - you simply ignoring the fact the inter-domain calls is broken. In 5.2.0 it is not working also. Domain / routing part identified correctly, but for some reason - "SIP/2.0 501 Temporarily Unavailable" When it will be fixed??? Very, very disappointing decision to ignore customers. We are thinking to massively extend the amount of licenses (add more companies) but inter-domain calls is a "must" Calling from 3000 to 7013: [9] 12:10:09.147 SIP: Resolve 815: udp 127.0.0.1 5060 [5] 12:10:09.147 PACK: SIP Tx udp:127.0.0.1:5060: ACK sip:7013@127.0.0.1:5060 SIP/2.0 Via: SIP/2.0/UDP 127.0.0.1:5060;branch=z9hG4bK-9b7c161e71e7da39fc5da3f55e38443c;rport From: "Maxim Shaposhnikov" <sip:3000@pbx.highperf.pro>;tag=1985252171 To: <sip:7013@pbx.navica.highperf.pro;user=phone>;tag=cb47e67e08 Call-ID: a35e627e@pbx CSeq: 21764 ACK Max-Forwards: 70 Contact: <sip:3000@127.0.0.1:5060;transport=udp> P-Asserted-Identity: "Maxim Shaposhnikov" <sip:3000@pbx.highperf.pro> Content-Length: 0 [5] 12:10:09.148 SIP: INVITE Response 501 Temporarily Unavailable: Terminate a35e627e@pbx [5] 12:10:09.148 PACK: SIP Rx udp:127.0.0.1:5060: ACK sip:7013@127.0.0.1:5060 SIP/2.0 Via: SIP/2.0/UDP 127.0.0.1:5060;branch=z9hG4bK-9b7c161e71e7da39fc5da3f55e38443c;rport From: "Maxim Shaposhnikov" <sip:3000@pbx.highperf.pro>;tag=1985252171 To: <sip:7013@pbx.navica.highperf.pro;user=phone>;tag=cb47e67e08 Call-ID: a35e627e@pbx CSeq: 21764 ACK Max-Forwards: 70 Contact: <sip:3000@127.0.0.1:5060;transport=udp> P-Asserted-Identity: "Maxim Shaposhnikov" <sip:3000@pbx.highperf.pro> Content-Length: 0 [9] 12:10:09.149 SIP: Resolve 816: aaaa udp 127.0.0.1 5060 [9] 12:10:09.149 SIP: Resolve 816: a udp 127.0.0.1 5060 [9] 12:10:09.149 SIP: Resolve 816: udp 127.0.0.1 5060 [5] 12:10:09.149 PACK: SIP Tx udp:127.0.0.1:5060: SIP/2.0 501 Temporarily Unavailable Via: SIP/2.0/UDP 127.0.0.1:5060;branch=z9hG4bK-21bfb19cb37a5db1cbe919bd3d0cb86a;rport=5060 From: "Maxim Shaposhnikov" <sip:3000@pbx.highperf.pro>;tag=203808712 To: <sip:7013@pbx.navica.highperf.pro;user=phone>;tag=98216bdf51 Call-ID: f3b1842e@pbx CSeq: 28624 INVITE Contact: <sip:7013@127.0.0.1:5060> Supported: 100rel, replaces, norefersub Allow-Events: refer Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE Accept: application/sdp User-Agent: Vodia-PBX/5.2.0 P-Asserted-Identity: <sip:7013@pbx.highperf.pro> Content-Length: 0

Any news regarding inter-domain calls? Currently we are using 5.1.1 with zero problems, but we'd lilke to be able to upgrade...

Ndemou, John. Indeed, there are some serious issues with inter-domain calling in 5.1.2 / 5.1.3 We don't have any issues with 5.1.1 (loopback works fine), but we could not make it work in the latest releases (with exactly the same config) My recommendation is to try with 5.1.1. Vodia guys don't like to accept the idea that they broke something recently.

Second question (again regarding inter domain calls). Let's make it simple. We've got some customers with 4 digit internal numbers. (i.e. 3000). There are some other companies (in the same holding) with numbers 70xx, 71xx, etc. They are not willing to change internal numbers (therefore it is not acceptable to set "more than 6 digits" numbers), they'll better change provider (us). It is not a problem to allow inter-domain calls in 4.x and 5.x ( lower than 5.1.2), but Vodia developers changed something in the code and now it is simply not possible to make it working again. We tried to rewrite numbers (adding "+" before extension), use additional trunk, etc. It is simply not working. The issue is very serious for us. Please provide correct steps, how to achieve old, simple and reliable behavior - call from 3000 to 7000 should be made locally without any additional numbers to dial. That's is. Customers don't like to use more than 4 digits numbers (hard to remember and address book is not useable from some soft phones), don't like to dial any additional digits, etc. Your own sample (http://wiki.snomone.com/index.php?title=Dial_Plan_Inter-domain ) not works on 5.1.3 (however it works fine on 5.1.1)

Still, we can't make it working (inter-domain calls) But this issue is not the most serious one... With 5.1.2 and 5.1.3, our users are not able to register on the PBX after a while (normally one day or less). PBX restart always helps. It never happens with 5.1.1 and lower, but always happens with 5.1.3. Web interface looks normal, no any issues - but all clients (including soft phones and Snom 870 devices) are simply not able to use PBX ("registering..." forever). Networks are not blocked.

Sorry, but still it is not very clear. It used to work without any prefixes for a long time (v3, v4, v5 up to 5.1.1) We don't like to set any additional aliases for each account as it is completely meaningless However, it is not a big deal to set prefixes per domain, but what does it mean under "prefixes"? How to set it? Finally, what is the reason to change normal behavior and to force customers to use workarounds? We've got plenty of internal users (without access to outside) and we don't need any external numbers / aliases attached to them.