Zipatile Intercom (SIP Server)

Begin of October was a month ago.

What's the actual situation?

1. 1. Zipatile is not unstable! If it is restarts, you have an issue with the internet or Zipatile itself.
2. 2. 2N Hellios door phone doesn't have SIP server built in. You were probably using client to client connection which is only working between door phone and single client.
3. 3. Zipato Intercom is complete building communication system with multiple SIP servers connected back to back
4. 4. You can always use the system as you explained as you don't need Zipato SIP server for that.

where do i find the zip server adress on the box and id and password, if zipabox ask like a sip server?...

how to install it in zipatile.

He asks me to buy a credits that it's normal

Not 100% sure. It might e. Go to youtube and find zipatotv. They have video tutorials how to set up.

Unfortunately need pro licence see picture in tutoriel.

Hi,

SIP Server and thermostat are not related, they are 2 separate features, so they can't influence one another.

We are already working on thermostat issue.

Regards

Battery consumption is nominal for Sip Server and Intercom apps, please check that "Stay awake" function or some other gesture is not preventing ZipaTile screen to go off after some time, because screen is main power consumer on ZipaTile.

Check that v1.1.1 is installed on ZipaTile and SipServer is configured on WebUI (don't forget to sync ). Afterwards everything should be handled automatically.

Solved! Thx. Did the update in the app repo

Hi Roland,

you are right, SIP server application was causing immense CPU usage, and this was causing all other apps to practically stop working, including rule engine, internal app which is managing sensors, and so on... Of course, battery draining was one of consequences as well.

I can confirm taht I have the same issues as Roland. I have updated SIP and shall see how it goes from now on

Doorbird integration is currently under construction, more information will be available soon.

Currently supported and tested doorphone manufactures ("pure" SIP implementation): 2N, Avadesign, Leviton, ...

yes, how to get one call to go to many clients, or one cluster.

SIP server cluster integration is under implementation, more information will be available soon.

SIP Server provides VoIP service with plain UDP packages to connected clients. Unfortunately, lots of ISPs have restricted such communication on mobile gateways (2G/3G/4G) or even on some xDSL/Cable installations. Please try to make a phone call at least twice between remote clients and if doesn't work then for surly there is ISP restriction.

Future SIPServer & Intercom releases will be included with mechanism which will resolve ISP restrictions permanently.

Hi Tomislav, when do you expect the release to solve the ISP restrictions?

Telephony restriction issues are planned for development, but currently can not say exactly when it will be available.

@Tomislav Senegacnik

Have you released the SIP Server that resolve the ISO Restrictions

?

Did you try the doorbird Andoid app on Zipatile? If you have to run the SIP server on the Zipatile you have to pay for the pro license. but what if the app runs correctly on Zipatile? I've made a test using a 2N Helios doorphone (described here: https://www.youtube.com/watch?v=7Gev9u0tNbM) trying to use the 2N Android client app instead of the setup descibed in the video. The 2N app runs correctly but does not ring. All the other functions (sound, video stream, door lock opening...) are ok but while it doesn't ring, it's actually unusable. Maybe the Doorbird app is different.

Intercom app doesn't have licence restriction, PRO package is required only for creation of SIP server. So, if you have, for example, three ZipaTIles only one needs PRO for SIP server creation, other Tiles can just connect to the tile with SIP server.

Thats all too expensive for testing purposes... There should be something like a trial license.

Noone tells me that it will work afterwards as expected, so I need to struggle around with 3rd Party SIP Servers like uSipServer e.g...

You can always try 2N app, Linphone or other similar apps

We tested 2N app and it does not ring. It pops up corectly even when the Zipatile screen is idle but there is no ring sound. The in-app functions are ok. You can talk, you can see the video stream, you can open the door.

With Linphone we were unable to unlock the door.

The single issue regarding the 2N client is that ringing. It should be fixed by Zipato because if you are using just a sigle Zipatile in your house (probably 95% of the installations), it is a little bit expensive to make it work as an Intercom.

The problem is not the app, the problem is the zipatile and IF its SIP Server is working correctly.

So you should give out a 30day trial to get things running. I don´t spend 100$ not knowing if the functionality really works.

@Laszlo

2N app does have some issues with communication with zipatile because it interferes with SIP server and Intercom app, but Cloud configuration should bypass that issues. You can try with that.

New IP device will ensure bringing to front Doorbird app after push notification so user will be able communicate with caller, open the door, etc. Doorbird app is proprietary IP based solution and it doesn't need SIP server. Disadvantage of this setup is that is dependent on Internet connectivity and it can not work without it. SIP however, works in offline and online state (with or without Internet connectivity), and its currently issue is that some ISPs are blocking SIP traffic so on some ISPs or countries Remote call is not available. This issue will be fixed soon, so free communication will be available localy and remotely.

@Ubuntuu

PRO licence is intended for advanced usage of ZipaTile and its available services. When you buy PRO you get all currently available services + 1 year of free upgrades. Those services stays permanent on your zipatile and can not expire (more details on https://www.zipato.com/how-it-works/features).

Company policy is that SIP server is bundled only with PRO package. If you need to test some other solutions you're free to experiment with APK installation.

@Tomislav

2N Cloud costs $2/device/month. That means $2 for the 2N doorphone and $2 for the Zipatile + Internet connection for both. Youl'll probably spend about $100 on the first year for this setup. PRO license is more cost-efficient in this case.

@Ubuntu

I know nothing about Doorbird but we tested the Zipatile SIP server and 2N Helios doorphone combo in the recommended setup and it works. But we spent $100 for a test. 2N is more expensive than Doorbird, I know. Another issue is the more complex maintenance of a large installation (more than 100 Zipatiles in a building in our case). The 2N doorphone + 2N Android client on the Zipatiles is by far more easy to manage. As you can imagine, the Cloud solution sugested by Tomislav is definitely not a solution for a large istallation. Nobody will pay a monthly fee for the intercom.

But what about the issue where the 2N app doesn't ring on the zipatile, as Laszlo mentioned.

It shows on the screen and you can answer and talk, but the ringing doesn't happen.

That needs a solution.

@laszlo

Hi LAszlo;

Did you find a solution fot the issue related to the 2N app app installed on zipatile that works (video stream, sound, door lock!!!;;;) but without ringing??

I think this solution is only working if you have only one client and one door station.

But what if you have multi 2N video door station with 100 appartments. If you simply install the app on each Client's Zipatile? How do you redirect the call from the 2N door phone to the needed zipatile!!(The zipatile n20 on appartment 20 when the guest press the button 20 on the 2 N external door phone station!!

Does that mean if we have at the building 's entery more than 1 appartment we have to buy zipatile SIP Server so that each one xwill have a name and a password ??

That needs confirmation

Doorbird app doesn't ring because it doesn't have service which waits in background, it depends for push notification which opens the app.

The guys which do not get a ring from their app need to add the google play services to their zipatile as far as I know.

Correct, but this has been taken care of on Zipatile with latest versions, which will be available for update this week.

Well, I really don't want to modify dozens of Zipatiles in an unsupported manner to get an app working. Yes, installing Google Services solves the problem but will open the Zipatile to a whole range of problemes that will crash it seconds. Our last attempt ran into a factory reset and a support ticket to rejoin the Zipatile to its Zipato account. It messed up even the account settings on the cloud. I cannot sugest this solution to my clients, I don't want to be called all day long for crashed Zipatiles. I am wainting for a stable solution from Zipato.

@Tomislav: I'll bomb you with request next week if the update won't be available. Just kidding :)

So the third party apps will work in future?

Yes, there will be support for 3rd party Intercom apps (without SIP) and more robust solutions with SIP.

Allright, then I will wait some more months/years until I can use the zipatile as working door-intercom.

Thanks for the update.

Currently Google services are not intended for ZipaTile.

Hi Tomislav,

In the zipato intercom system, the apartments can clear their neighbors. This is a big problem.

For example I do not like neighbors and I deleted it from zipatile intercom application. As a result, the neighbor can no longer use intercom. Do you have a solution for this?

Best Regards,

Do you mean that ANYBODY can add or delete a user on the Zipatile SIP server, not only the user of that "master" Zipatile? If there is a Zipatile in all apartments, all off them can delete any of the users created on the "master" Zipatile? We just started cabling for 100+ Zipatiles in an apartment building. Tomislav this must be a joke.

Don't worry, apartment contacts can not delete building contacts, they're separated by controller SIP domains.

However, on single SIP server, at this moment, owner and member contacts are treated the same so member can delete owners contact. This will be resolved soon with restriction that only owner of created contact can delete it with exception that owner of zipatile (SIP server) can modify any contacts.

In short, zipatile owner will have full control, and members will have access only of their contacts.

Hi Tomislav,

I do not clearly undestand. We have a sigle SIP server on that building. 100+ Zipatiles, one in each apartment, +1 Zipatile as a SIP server. We have two 2N Helios doorphones at the gates. All are connected in the same network. Will the user be able to delete another user in this this setup or not?

If you have Building SIP server and SIP server for every apartment, then certainly no.

If you have only one SIP server and all clients connected to it, then yes.

You can see the schematic in attachment

As we have only one Zipatile per apartment, I see no reason to install SIP server on them. There are no local doorphones which need to managed by that local SIP server. Another reason is that this will increase our project cost vith more than $10.000 for the pro licenses. I consider this a completely unacceptable security breach. Please suggest a solution for such a large scale project.

In my opinion, security breach is in setup when all tiles from different apartments are set to single Building SIP server, but as you wish. Fix for deleting contacts other then owner will be implemented in SIP server v1.3.2.

Hi LAszlo;

@Laszlo Szoke

I have a simular project with 50 appartments with one zipatile on each appartment.

How have you proceed ? HAve you bought the 10.000$ for the pro licenses for each zipatile?

What if i have a local door phone???

How have you done Laszlo?

My experience says that this dual network setup does not work. The USB-to-Ethernet adapters does not work while the Wi-Fi is active.

All issues with dual network communication are resolved in SIP server v1.3.1 which will be available in new OTA upgrade. Currently it is under testing and will be available for usage soon.

Tomislav, is there a desciption how to use a third party SIP server with Zipatile? In the actual situation I prefer to use a deicated server running Asterisk or 3CX just to avoid users to delete each other.

Currently, there is no public documentation for Zipato sip server. Please be patient and issue with deleting contacts will be resolved soon

@Laszlo

Please try to understand what Tomislav is saying here. Users can't delete each other in appartment building! Building SIP server is only accessible by building manager. What Tomislav is trying to explain to you is related to the appartment SIP server which you don't want to use anyway.

If you want to use any third party SIP server, you can do it. However, please understand that we don't provide any support for these SIP server (which should be quite logical at the first place).

Thank you for your understanding.

@Sebastian Popovici

Thank you very much for your intervention. Tomislav statet above:

"However, on single SIP server, at this moment, owner and member contacts are treated the same so member can delete owners contact. This will be resolved soon with restriction that only owner of created contact can delete it with exception that owner of zipatile (SIP server) can modify any contacts."

This is why I insisted on this issue. We have just one SIP server in the whole network whic is the buildings SIP server. If anyone from an apartment Zipatile will able to delete a registered user, this gonna be a disaster. Obviously we also want to restrict addition or editing of users on the SIP server. The apartment Zipatile should be a simple Intercom client with no rights. If you say that we do not need to spend a lot of money for Pro licenses and the users won't be able to mess up the system, I'm really happy. To be sure we talk about the same thing, here is our building:

@ laszlov

what if we have local door phone in front of each appartment will this schematic works as well?