good morning!

I'm trying to configure push notification and need to clarify something

sup pusher_maintenance add_firebase_app AppId Secret

What should be format of Appid?

is it app name, project number or what?

I see APP ID in ffirebase app section started with 1:8080366xxxxxx:android:d0575bx

should I use this APP ID?

"mobilesdk_app_id": "1:8080366xxxxxx:android:d0575bxxxxxx" is also in my google-services.json file

mc_: any idea?

Serge: i don't know offhand, i would guess its whatever app id you use to register on google?

mc_ you mean firebase

mobilesdk_app_id might be right

sure

lol

i see one customer using it have a Java-like namespace for their app id

like "com.foobar.calling.sdk.example" or something

but i haven't really dug into the pusher client configs much

<sip:testuser1⊙124X:5212;pn…silent=1;pn-timeout=0;transport=udp>;+sip.instance="<urn:uuid:5fe34d9f-477e-007b-b4ea-4286eefa3527>";+org.linphone.specs="lime" : 3600

but I'm afraid it did not pushing any notifications =(

is there any way to get status of push notification (registrations) from kazoo?

kazoo doesn't send anything to firebase until a push notification event (like incoming call) is triggered

I'm trying to make call, but can't see any push out notification

I believe kamailio send them?

What the best place to look?

Serge: there is a good thread on the forum that details setup for push notifications. IIRC it's titled "My pusher problems are solved" or something like that.

lvlinux: yes, I saw it, however it doesn't look like pusher is trying to wake up my app at all

and analytics dashboard said that there are no requests or active users

that's why I'm trying to see what piece didn't work

ah gotcha

Serge: do you have Kazoo logs on debug? I just did a quick look at the pusher code and saw there is logging going on in the app, so you should be able to see some information there.

lvlinux yes, I have it enabled, but can't really see that kazoo pushing anything to firebase server

the only registration log

He mc_ is kazoo_modb:save_doc the normal function to call to put a new doc in an MODB? Like for CDRs, Voicemail, fax, SMS, etc.? Or is there another different way that is used sometimes?

Serge: if it's not giving an error or trying something, then likely it hasn't received the right push info on the registration. You might monitor the AMQP bus and see if a message gets sent to the pusher process when the client registers. If not, then back up to Kamailio configs and see what it's supposed to be sending. Shouldn't be too hard to isolate that way.

Also watch your Kamailio logs as they might give a clue.

Hmm I don't see any code at all that stores SMS messages, but it evidently used to. Wonder why that was removed?

RHEL trying to kill open source downstream distros :( . rockylinux.org/news/2023-06-22-press-release

:-(

Thanks for the info btw lvlinux

Now I gotta figure out freeswitch, as there's no mod_av release for rocky 8. Might need to use debian for fs if I don't wanna build all that from source too

But maybe it's more sane now to just debian everything :P

hehe Debian is my goto distro

(for servers anyway)

I've been a CentOS boy my entire life. Change is hard

Have you managed 4.3 on debian? I'm trying to dodge eol CentOS 7 while I migrate to new servers, new data centres, etc

I haven't yet---my DBs run on debian, and everything else I've just stayed with the "safe" CentOS 7. But we have only right at a year to switch before EOL right? (June 2024?)

I just run the RPMs though. When I build it I will probably do it on Debian.

Hopefully v5 OS comes out soon and I won't have to build or hack up v4.3. Some things I want fixed but don't want to put in time for that when it may be moot or have to be re-done after v5 comes out.

I'm starting to think along the same lines. CentOS 7 for another year except for kazoo apps, rabbitmq and couchdb since they're all built from source successfully.

If 5 isn't out be the end of the year, then I have 6 months to get rocky 8 running instead of rushing like I am now lol

:)