14:25:00 <Serge> mc_: Do you know by any chance if v5 will have updated push notifications?
15:28:36 <mc_> Serge: websocket or mobile push?
15:28:45 <Serge> mobile push\
15:30:50 <mc_> yes, we've added a couple more...new vm, missed call, and an API to send arbitrary notifications to the phone
15:30:57 <mc_> not sure what's in 4.3 still
15:34:47 <Serge> in 4.3 you have only old legacy pusher
15:46:47 <mc_> i don't know what's going on with the google integration, that's a good question
15:56:13 <Serge> pn-tok is not used anymore in current firebase pusher, they start use pn-prid
15:57:07 <Serge> it is in RFC8599
16:07:20 <Serge> freeswitch port 11000, where should it be open? Does end users use it when make a call?
16:11:30 <Serge> is it just interserver communications?
16:11:51 <mc_> Serge: 11000 can be open but generally we recommend just between kam/fs and force all public SIP through kam
16:12:03 <mc_> certainly for registrations
16:12:19 <mc_> some send direct FS to carrier though, but carriers should send to kam for inbound
16:12:37 <Serge> so, iff my clients use port 7000 only, can I block port 11000 with iptables?
16:12:55 <Serge> in all in one node?
16:13:11 <mc_> i would, no public inbound connections to 11000, only from kam IPs
16:17:52 <ruel> Serge it's a good idea to allow your carrier[s] IP[s] to access port 11000 on Freeswitch, as well as all other Freeswitch servers. The reason for carriers is that on an outbound call IF your firewall times out the SIP connection during a call, and the carrier sends a reinvite (often after 10-30 minutes on the call), if the carrier can't reach Freeswitch it will kill the call. The reason to open 11000 to your 
16:17:58 <ruel> other Freeswitch servers is that if there is a conference call, and a new call comes in destined for the conference, but first ends up on a different Freeswitch server, the system will direct that FS server to transfer the call to the FS server where the conference is.
16:18:45 <ruel> mc_ does the above sound correct? Or have things changed and this is no longer needed?
16:19:54 <Serge> ruel, as I know carrier will send reinvite to port which is specified on your carrier settings, i.e. port 7000
16:20:47 <ruel> For inbound yes, but outbound calls go directly out from Freeswitch remember.
16:20:59 <ruel> Of course it doesn't apply on an AIO server, just clustered.
16:23:46 <ruel> (I should have specified that, sorry.)
16:25:15 <ruel> But yes, on a single server, with IP auth, then the carrier should send the reinvite to the Kamailio port.
16:27:23 <mc_> ruel: at most, i would allow FS to send INVITE to carrier, but even that isn't recommended as much
16:27:34 <mc_> in our newer clusters, everything proxies through kamailio
16:28:23 <mc_> as far as i know, we haven't observed calls terminating due to firewall timeouts
16:28:40 <mc_> between kazoo/carrier, that is
17:52:42 <ruel> really? So you're doing something like fs_path for outbound now?
17:53:30 <ruel> Or is it a change in V5 that automatically does it? That does eliminate some complexity with having calls originating from different places than they come into the system.
18:06:32 <mc_> tbh i forget the mechanism, but yes, effectively an implied fs_path=kam.ip
18:06:44 <mc_> i think its an opt-in system config thing 
18:06:52 <mc_> but its default on for our installs now
18:33:51 <ruel> ah ok nice