Giter Site home page Giter Site logo

linhome-android's People

Contributors

cdeschambc avatar cdeschamps avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

linhome-android's Issues

File format XML

I ask you to suggest the XML file format for remote configuration of the Linhome application, especially the addition of devices (intercoms).

feature request: include an RTSP stream

Hi, as in topic, is it possible to insert a manual rtsp stream? usefull for intercoms that are not able to send video in SIP
or we can inject an camera feed from another camera

thnx in advance

Firebase configuration

Hello,
I'm trying to use linhome application with our Flexisip server.
What I want is for a user to log in with a SIP account (Flexisip) that was configured to send push notifications using Firebase to wake up the application.
I succeeded to clone the project, replace the google service file, run in it into debug mode video calls etc. work but I do not receive push notifications when the app is closed.
Do you have any suggestions?

Thank you.

Is sip.linhome.org down?

Some 3 or 4 days ago, some working configurations I had with Linhome stopped working. It seems that sip.linhome.org is not responding, is that possible?

Symptoms: door system trying to connect to sip.linhome.org gets stuck "connecting...". I didn't change any configurations, and this was working before...

I thought it was just for me but I heard from a friend that also uses linhome that it's broken for him too.

Any debugging I can do? Anyone else with this issue?

Unable to connect with transport TCP under "use your SIP account"

I'm unable to connect to my flexisip server with "use your sip account" option in assistant :

Connection to server is always established with UDP transport regardless of transport selection UDP/TCP/TLS in assistant.
Also unable to specify a non-standard port inside proxy field.

I didn't find another place to report this issue as code is hosted on your own gitlab

Allow taking door video calls during audio call.

Suppose I am talking on the phone with someone (a normal GSM call, or WhatsApp or Signal audio calls).

During that call, someone arrives at my door and rings, I see the early video coming in while Linhome is "ringing". I recognize the person(this is what happens 99% of all the calls taken on most door systems), and I want to open the door for him. So I tap Linhome to take the call.

But it doesn't answer, and I see a message saying something like "Linhome can't answer the phone while your microphone is busy on the other call". Meanwhile, everything is awkward because I am still talking on the phone, but my phone is buzzing and ringing, and I can't get on my life.

What I would prefer: just take the call without sound, so I can send the Open the door command, while I continue my voice call. Just flash me a message as you start the call "Linhome can't connect to your speaker and microphone because they are busy! Your call won't have any audio".

Linhome Version: Beta 1.2

feature request: password protection for door entry definition

Dear linhome-team,

I relally appreciate the great linhome app and all the possible features, the app is working very well within my smarthome configuration. There is one topic, which is not so nice:
Is it possible to protect the settings of the door opening control? For now the DTMF-code in the app is visible by everyone, if the app is running if foreground on the main page. It would be very helpful to hide the DTMF-code in the main view and also show/change the DTMF-code for the door opening function with a password protection function.

Thank you very much for your feedback!

Refresh registration

Linhome proxy uses long time registrations. But many of intercom users call 1 time for week. Long registration expires too.

What shall I send to user to refresh registration then it expires?

I dont want missed calls or blank sms in history.

Action buttons don't show during video call

Hi! I just discovered Linhome after making some feature requests for Linphone and getting sent here :-)

I am trying Linhome and I could easily get it to make video calls to my door video, a 2N Helios. I am using the sip.linhome.org account, and my door device is not registering to that account. This means I can only make calls from the door to the phone, not the other way around (which is fine with me, I just mention it in case it is relevant).

I set up also an "Action", to send the DTMF code 7* which triggers the door lock to open.

But I can't see any way to tell Linhome to run the action. No button, nothing. I tried full-screen, normal view, I tapped everywhere on screen and nothing happened...

My action is set up like this:

image

Technical info

Device: OnePlus Nord CE 5G
OS: Android 11
Version of the App: 5.0.5
Version of the SDK: 5.2.15
Where you did got it from: Play Store
Oxygen OS 11.0.5

Am I doing something wrong?
Thanks!

403 Domain forbidden from sip.linhome.org

Then linhome android call intercom via asterisk - it call directly asterisk.

After answer asterisk sends invite to sip:[email protected] contact

sip.linhome.org answers 403 Domain forbidden so INVITE (SDP) not reached intercom.

So I have one way audio.

LInhome get token device

Good day!
Problem getting token in LINHOME app. I am using SIP connection through my Asterisk server. But after registering in the contact header, I do not receive the application token. I looked at your other application: LINPHONE it has the "Allow push notification" setting when it is turned on, the token appears, but I do not see it in the LINHOME application for the intercom. What can be done with these.

No incoming sound

Hello,
I just installed linhome for android and configured it. I think it is a great app, but unfortunately incoming audio is not working.
Specifically, this is what is happening:

  • If I receive a call, I cannot hear the caller
  • If I start a call to the doorbell, I cannot hear the person at the doorbell
  • The app also doesn't ring when receiving a call
  • Everything else, including video, outgoing audio and early-media works as expected

I think it is an app issue as audio works fine when using linphone app.
Please tell me if you need other info.
Thanks

User experience issues for "Delete all History"

Hi

I often go into History to clear a bunch of videos from my phone.

This is the current sequence:

  1. Go to history tab (bottom of screen)
  2. Tap Delete button (top of screen)
  3. Tap select all (bottom of screen)
  4. Tap Delete again (top of screen)
  5. Tap confirm delete (middle of screen)
  6. Wait
  7. Faced with a useless blank screen, tap Devices (bottom of screen)

What I would like to have:

  1. A button on the main devices UI to "Clear all history"
  2. Pressing it would just delete all history, in the background, without confirmation. This would make the every-day experience a single tap.
  3. An undo option could appear for a few seconds next to that button. If pressed, the deletes would be undone (under the hood, this would be implemented by only apparently, but not really, deleting them until the seconds elapsed).

Also a good idea:

  • an option in preferences to automatically clear history after X days.

I believe this would greatly improve every-day experience of many users.
Thanks!

Support for Android 13

Hi

I tried to install the app yesterday in a friend's phone, and the Google Play Store said "app is not compatible with this version of Android". It's Android 13, which was released about a year ago.

What is the status of Android 13 support in Linhome? Is it planned? Any expected date? Thanks

Device does not re-register after registration expires

Hi,
I noticed that my device does not refresh it's registration state after the configured timeout expires (in my setup it is 7200 seconds).
I suspect this is because, if I am not mistaken, there is no WorkManager support so if the device is not used for a prolonged time (longer then expiration time) it simply does nothing.
I am not sure if this is a bug or if there some setting I can configure in my server side local setup (asterisk + PJSIP).
Is this a bug? Is there anything I can try to fix this behaviour?

SIP proxy at sip.linhome.org is not available

Account registration at sip.linhome.org works OK, but connection to SIP proxy fails. I see in menu "My Account":

Account: sip:[email protected]
SIP connection: Connection failed

Connecting to sip.linphone.org account works OK, using it instead.

I use Android 10 x86 emulator from Android Studio.

Relevant logcat output:

2022-11-30 12:51:33.740  5169-5169  Linhome                 org.linhome                          I  channel [0xbc9f8fc0]: keep alive sent to [UDP://sip.linphone.org:5060]
2022-11-30 12:51:33.740  5169-5169  Linhome                 org.linhome                          I  channel [0xbcbb7080]: keep alive sent to [TLS://sip.linhome.org:5061]
2022-11-30 12:52:03.745  5169-5169  Linhome                 org.linhome                          I  channel [0xbc9f8fc0]: keep alive sent to [UDP://sip.linphone.org:5060]
2022-11-30 12:52:03.746  5169-5169  Linhome                 org.linhome                          I  channel [0xbcbb7080]: keep alive sent to [TLS://sip.linhome.org:5061]
2022-11-30 12:52:23.754  5169-5169  Linhome                 org.linhome                          I  bellesip_wake_lock_acquire(): Android wake lock [belle-sip transaction(0xc1e9e260)] acquired [ref=0x31ea]
2022-11-30 12:52:23.754  5169-5169  Linhome                 org.linhome                          I  bellesip_wake_lock_acquire(): cast long of wakelock 12778
2022-11-30 12:52:23.754  5169-5169  Linhome                 org.linhome                          I  transaction [0xc1e9e260]: starting transaction background task with id=[31ea].
2022-11-30 12:52:23.755  5169-5169  Linhome                 org.linhome                          I  Transaction [0xf0d85660] deleted
2022-11-30 12:52:23.755  5169-5169  Linhome                 org.linhome                          I  Changing [client] [REGISTER] transaction [0xc1e9e260], from state [INIT] to [TRYING]
2022-11-30 12:52:23.756  5169-5169  Linhome                 org.linhome                          I  channel [0xbcbb7080]: message sent to [TLS://sip.linhome.org:5061], size: [887] bytes
2022-11-30 12:52:23.756  5169-5169  Linhome                 org.linhome                          I  REGISTER sip:sip.linhome.org SIP/2.0
2022-11-30 12:52:23.756  5169-5169  Linhome                 org.linhome                          I  Via: SIP/2.0/TLS 10.0.2.16:35290;alias;branch=z9hG4bK.zB9OHH9U~;rport
2022-11-30 12:52:23.756  5169-5169  Linhome                 org.linhome                          I  From: <sip:[email protected]>;tag=1nhQzqbC9
2022-11-30 12:52:23.756  5169-5169  Linhome                 org.linhome                          I  To: sip:[email protected]
2022-11-30 12:52:23.756  5169-5169  Linhome                 org.linhome                          I  CSeq: 22 REGISTER
2022-11-30 12:52:23.756  5169-5169  Linhome                 org.linhome                          I  Call-ID: BhYahYWv9c
2022-11-30 12:52:23.756  5169-5169  Linhome                 org.linhome                          I  Max-Forwards: 70
2022-11-30 12:52:23.756  5169-5169  Linhome                 org.linhome                          I  Supported: replaces, outbound, gruu, path
2022-11-30 12:52:23.756  5169-5169  Linhome                 org.linhome                          I  Accept: application/sdp
2022-11-30 12:52:23.756  5169-5169  Linhome                 org.linhome                          I  Accept: text/plain
2022-11-30 12:52:23.756  5169-5169  Linhome                 org.linhome                          I  Accept: application/vnd.gsma.rcs-ft-http+xml
2022-11-30 12:52:23.756  5169-5169  Linhome                 org.linhome                          I  Contact: <sip:[email protected]:48572;pn-prid=fxV-H_5hSayT9rbRMpK9EN:APA91bHuWNfPboC0MDqh_xulnYQx7CgyB5d5lzCyqfYSi1jiGjj5Bs5M3cXUmieOfN3wH8gOOJRtFJn_ISXq2uVXvjejLS-kwQjA6yZslDsGTm4sLvpuB9y3CqCAZYBOrAVAq2Ox-XpC;pn-provider=fcm;pn-param=1041242817246;pn-silent=1;pn-timeout=0;transport=tls>;+sip.instance="<urn:uuid:3703990a-a30e-00ab-acfd-d726eb98dfcf>"
2022-11-30 12:52:23.756  5169-5169  Linhome                 org.linhome                          I  Expires: 31536000
2022-11-30 12:52:23.756  5169-5169  Linhome                 org.linhome                          I  User-Agent: Linhome/5.0.0 (Android SDK built for x86) LinphoneSDK/5.2.0-beta.93+730cd63 (pipelines/55099)
2022-11-30 12:52:23.756  5169-5169  Linhome                 org.linhome                          I  Content-Length: 0
2022-11-30 12:52:23.756  5169-5169  Linhome                 org.linhome                          I  
2022-11-30 12:52:23.756  5169-5169  Linhome                 org.linhome                          I  
2022-11-30 12:52:23.832  5169-5169  Linhome                 org.linhome                          I  bellesip_wake_lock_acquire(): Android wake lock [belle-sip recv channel] acquired [ref=0x312a]
2022-11-30 12:52:23.833  5169-5169  Linhome                 org.linhome                          I  bellesip_wake_lock_acquire(): cast long of wakelock 12586
2022-11-30 12:52:23.833  5169-5169  Linhome                 org.linhome                          I  channel [0xbcbb7080]: starting recv background task with id=[312a].
2022-11-30 12:52:23.833  5169-5169  Linhome                 org.linhome                          I  channel [0xbcbb7080]: received [625] new bytes from [TLS://sip.linhome.org:5061]:
2022-11-30 12:52:23.833  5169-5169  Linhome                 org.linhome                          I  SIP/2.0 401 Unauthorized
2022-11-30 12:52:23.833  5169-5169  Linhome                 org.linhome                          I  Via: SIP/2.0/TLS 10.0.2.16:35290;alias;branch=z9hG4bK.zB9OHH9U~;rport=48572;received=79.126.58.253
2022-11-30 12:52:23.833  5169-5169  Linhome                 org.linhome                          I  From: <sip:[email protected]>;tag=1nhQzqbC9
2022-11-30 12:52:23.833  5169-5169  Linhome                 org.linhome                          I  To: <sip:[email protected]>;tag=58B771p6rF5US
2022-11-30 12:52:23.833  5169-5169  Linhome                 org.linhome                          I  Call-ID: BhYahYWv9c
2022-11-30 12:52:23.833  5169-5169  Linhome                 org.linhome                          I  CSeq: 22 REGISTER
2022-11-30 12:52:23.833  5169-5169  Linhome                 org.linhome                          I  Server: Flexisip/2.2.0-3-g73237746 (sofia-sip-nta/2.0)
2022-11-30 12:52:23.833  5169-5169  Linhome                 org.linhome                          I  WWW-Authenticate: Digest realm="sip.linhome.org", nonce="WKYx5wAAAACj4y7wAABM0mDfvb0AAAAA", opaque="+GNywA==", algorithm=SHA-256, qop="auth"
2022-11-30 12:52:23.833  5169-5169  Linhome                 org.linhome                          I  WWW-Authenticate: Digest realm="sip.linhome.org", nonce="WKYx5wAAAACj4y7wAABM0mDfvb0AAAAA", opaque="+GNywA==", algorithm=MD5, qop="auth"
2022-11-30 12:52:23.833  5169-5169  Linhome                 org.linhome                          I  Content-Length: 0
2022-11-30 12:52:23.833  5169-5169  Linhome                 org.linhome                          I  
2022-11-30 12:52:23.833  5169-5169  Linhome                 org.linhome                          I  
2022-11-30 12:52:23.840  5169-5169  Linhome                 org.linhome                          I  channel [0xbcbb7080] [625] bytes parsed
2022-11-30 12:52:23.840  5169-5169  Linhome                 org.linhome                          I  Found transaction matching response.
2022-11-30 12:52:23.840  5169-5169  Linhome                 org.linhome                          I  Changing [client] [REGISTER] transaction [0xc1e9e260], from state [TRYING] to [COMPLETED]
2022-11-30 12:52:23.841  5169-5169  Linhome                 org.linhome                          I  AuthRequested pushed
2022-11-30 12:52:23.841  5169-5169  Linhome                 org.linhome                          I  No auth info found for call id [BhYahYWv9c]
2022-11-30 12:52:23.841  5169-5169  Linhome                 org.linhome                          I  linphone_core_find_auth_info(): returning auth info username=gmixaz, realm=sip.linhome.org
2022-11-30 12:52:23.841  5169-5169  Linhome                 org.linhome                          I  AuthStack::authFound() for Username[gmixaz];Userid[];Realm[sip.linhome.org];Domain[sip.linhome.org];Algorithm[];AvailableAlgorithms[];
2022-11-30 12:52:23.841  5169-5169  Linhome                 org.linhome                          I  Auth info found for [gmixaz] realm [sip.linhome.org]
2022-11-30 12:52:23.843  5169-5169  Linhome                 org.linhome                          I  bellesip_wake_lock_acquire(): Android wake lock [belle-sip transaction(0xbc858760)] acquired [ref=0x3106]
2022-11-30 12:52:23.843  5169-5169  Linhome                 org.linhome                          I  bellesip_wake_lock_acquire(): cast long of wakelock 12550
2022-11-30 12:52:23.843  5169-5169  Linhome                 org.linhome                          I  transaction [0xbc858760]: starting transaction background task with id=[3106].
2022-11-30 12:52:23.843  5169-5169  Linhome                 org.linhome                          I  Changing [client] [REGISTER] transaction [0xbc858760], from state [INIT] to [TRYING]
2022-11-30 12:52:23.844  5169-5169  Linhome                 org.linhome                          I  channel [0xbcbb7080]: message sent to [TLS://sip.linhome.org:5061], size: [1153] bytes
2022-11-30 12:52:23.845  5169-5169  Linhome                 org.linhome                          I  REGISTER sip:sip.linhome.org SIP/2.0
2022-11-30 12:52:23.845  5169-5169  Linhome                 org.linhome                          I  Via: SIP/2.0/TLS 10.0.2.16:35290;alias;branch=z9hG4bK.HF5jxVg7J;rport
2022-11-30 12:52:23.845  5169-5169  Linhome                 org.linhome                          I  From: <sip:[email protected]>;tag=1nhQzqbC9
2022-11-30 12:52:23.845  5169-5169  Linhome                 org.linhome                          I  To: sip:[email protected]
2022-11-30 12:52:23.845  5169-5169  Linhome                 org.linhome                          I  CSeq: 23 REGISTER
2022-11-30 12:52:23.845  5169-5169  Linhome                 org.linhome                          I  Call-ID: BhYahYWv9c
2022-11-30 12:52:23.845  5169-5169  Linhome                 org.linhome                          I  Max-Forwards: 70
2022-11-30 12:52:23.845  5169-5169  Linhome                 org.linhome                          I  Supported: replaces, outbound, gruu, path
2022-11-30 12:52:23.845  5169-5169  Linhome                 org.linhome                          I  Accept: application/sdp
2022-11-30 12:52:23.845  5169-5169  Linhome                 org.linhome                          I  Accept: text/plain
2022-11-30 12:52:23.845  5169-5169  Linhome                 org.linhome                          I  Accept: application/vnd.gsma.rcs-ft-http+xml
2022-11-30 12:52:23.845  5169-5169  Linhome                 org.linhome                          I  Contact: <sip:[email protected]:48572;pn-prid=fxV-H_5hSayT9rbRMpK9EN:APA91bHuWNfPboC0MDqh_xulnYQx7CgyB5d5lzCyqfYSi1jiGjj5Bs5M3cXUmieOfN3wH8gOOJRtFJn_ISXq2uVXvjejLS-kwQjA6yZslDsGTm4sLvpuB9y3CqCAZYBOrAVAq2Ox-XpC;pn-provider=fcm;pn-param=1041242817246;pn-silent=1;pn-timeout=0;transport=tls>;+sip.instance="<urn:uuid:3703990a-a30e-00ab-acfd-d726eb98dfcf>"
2022-11-30 12:52:23.845  5169-5169  Linhome                 org.linhome                          I  Expires: 31536000
2022-11-30 12:52:23.845  5169-5169  Linhome                 org.linhome                          I  User-Agent: Linhome/5.0.0 (Android SDK built for x86) LinphoneSDK/5.2.0-beta.93+730cd63 (pipelines/55099)
2022-11-30 12:52:23.845  5169-5169  Linhome                 org.linhome                          I  Content-Length: 0
2022-11-30 12:52:23.845  5169-5169  Linhome                 org.linhome                          I  Authorization:  Digest realm="sip.linhome.org", nonce="WKYx5wAAAACj4y7wAABM0mDfvb0AAAAA", algorithm=MD5, opaque="+GNywA==", username="gmixaz",  uri="sip:sip.linhome.org", response="59e29ac04a1ae10e67e0e1f3efb0bc70", cnonce="Hg3WtsOPunYiLrzb", nc=00000001, qop=auth
2022-11-30 12:52:23.845  5169-5169  Linhome                 org.linhome                          I  
2022-11-30 12:52:23.845  5169-5169  Linhome                 org.linhome                          I  
2022-11-30 12:52:23.845  5169-5169  Linhome                 org.linhome                          I  Changing [client] [REGISTER] transaction [0xc1e9e260], from state [COMPLETED] to [TERMINATED]
2022-11-30 12:52:23.845  5169-5169  Linhome                 org.linhome                          I  Client internal REGISTER transaction [0xc1e9e260] terminated
2022-11-30 12:52:23.845  5169-5169  Linhome                 org.linhome                          I  transaction [0xc1e9e260]: ending transaction background task with id=[31ea].
2022-11-30 12:52:23.848  5169-5169  Linhome                 org.linhome                          I  bellesip_wake_lock_release(): Android wake lock released [ref=0x31ea]
2022-11-30 12:52:23.848  5169-5169  Linhome                 org.linhome                          I  Transaction [0xc1e9e260] deleted
2022-11-30 12:52:23.848  5169-5169  Linhome                 org.linhome                          I  channel [0xbcbb7080]: ending recv background task with id=[312a].
2022-11-30 12:52:23.849  5169-5169  Linhome                 org.linhome                          I  bellesip_wake_lock_release(): Android wake lock released [ref=0x312a]
2022-11-30 12:52:23.852  5169-5169  Linhome                 org.linhome                          I  Authentication request not needed.
2022-11-30 12:52:23.912  5169-5169  Linhome                 org.linhome                          I  bellesip_wake_lock_acquire(): Android wake lock [belle-sip recv channel] acquired [ref=0x3122]
2022-11-30 12:52:23.912  5169-5169  Linhome                 org.linhome                          I  bellesip_wake_lock_acquire(): cast long of wakelock 12578
2022-11-30 12:52:23.912  5169-5169  Linhome                 org.linhome                          I  channel [0xbcbb7080]: starting recv background task with id=[3122].
2022-11-30 12:52:23.912  5169-5169  Linhome                 org.linhome                          I  channel [0xbcbb7080]: received [342] new bytes from [TLS://sip.linhome.org:5061]:
                                                                                                    SIP/2.0 403 Forbidden
                                                                                                    Via: SIP/2.0/TLS 10.0.2.16:35290;alias;branch=z9hG4bK.HF5jxVg7J;rport=48572;received=79.126.58.253
                                                                                                    From: <sip:[email protected]>;tag=1nhQzqbC9
                                                                                                    To: <sip:[email protected]>;tag=7tyrBrrDK1H1g
                                                                                                    Call-ID: BhYahYWv9c
                                                                                                    CSeq: 23 REGISTER
                                                                                                    Server: Flexisip/2.2.0-3-g73237746 (sofia-sip-nta/2.0)
                                                                                                    Content-Length: 0
2022-11-30 12:52:23.914  5169-5169  Linhome                 org.linhome                          I  channel [0xbcbb7080] [342] bytes parsed
2022-11-30 12:52:23.914  5169-5169  Linhome                 org.linhome                          I  Found transaction matching response.
2022-11-30 12:52:23.914  5169-5169  Linhome                 org.linhome                          I  Changing [client] [REGISTER] transaction [0xbc858760], from state [TRYING] to [COMPLETED]
2022-11-30 12:52:23.914  5169-5169  Linhome                 org.linhome                          I  Refresher[0xc1eb0c90]: scheduling next timer in 60000 ms for purpose [retry]
2022-11-30 12:52:23.914  5169-5169  Linhome                 org.linhome                          I  Register refresher [403] reason [Forbidden] for proxy [<sip:sip.linhome.org;transport=tls>]
2022-11-30 12:52:23.914  5169-5169  Linhome                 org.linhome                          I  linphone_core_find_auth_info(): returning auth info username=gmixaz, realm=sip.linhome.org
2022-11-30 12:52:23.914  5169-5169  Linhome                 org.linhome                          I  sip.linhome.org/gmixaz/sip.linhome.org/HttpDigest authentication fails.
2022-11-30 12:52:23.914  5169-5169  Linhome                 org.linhome                          I  AuthRequested pushed
2022-11-30 12:52:23.914  5169-5169  Linhome                 org.linhome                          I  Changing [client] [REGISTER] transaction [0xbc858760], from state [COMPLETED] to [TERMINATED]
2022-11-30 12:52:23.914  5169-5169  Linhome                 org.linhome                          I  Client internal REGISTER transaction [0xbc858760] terminated

Where "pn-tok"?

Good day!
I do not know where to write, please help.
Working on push notifications. But for push notifications you need to get pn-tok, but in asterisk I don't get it in Reg. Contact, that is, completely different information comes in.

In which file do you transfer data to the header for Asterisk?

feature request: SIP port definition

Dear linhome-team,

thanks for the great work on linhome app. Is it possible to get an additional feature into the linhome app for a manual SIP port definition on the configuration screen? For some routers it is not possible to use the std. 5060 SIP port, because the port is pre-used by the router itself for SIP communication.

Linhome android, running the application in the background

Good day! Thank you for your work! After the update on April 19, the application rings normally with an incoming call. However, the application stopped working after restarting the device (autorun is enabled), and after clearing the gadget's memory (all background permissions in android are also set).

No access to submodule [email protected]:BelledonneCommunications/linhome-shared-themes

Submodule 'linhome-shared-themes' ([email protected]:BelledonneCommunications/linhome-shared-themes) registered for path 'linhome-shared-themes'
Cloning into '/home/gmixaz/linhome-android/linhome-shared-themes'...
ERROR: Repository not found.
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.
fatal: clone of '[email protected]:BelledonneCommunications/linhome-shared-themes' into submodule path '/home/gmixaz/linhome-android/linhome-shared-themes' failed

Use a Linhome account doesn't work

Hi! When adding an account, this doesn't work:

  1. Go to account assistant
  2. Select Use a Linhome account
  3. Enter user name (e.g. myuser) and password (e.g. mypass).
  4. See an error: Unknown username or incorrect password

But those credentials work just fine to log in at https://subscribe.linhome.org/login !

And I can also login in Linhome app by doing this instead:

  1. Go to account assistant
  2. Select Use your SIP account
  3. Enter user name (e.g. myuser), SIP domain (sip.linhome.org, I wish this value was there by default so I wouldn't have to type it every time) and password (e.g. mypass).
  4. It works

Am I missing something, or is this a bug? Thanks

Tested on version 1.2 beta

Feature request: enable / disable app easily

Hi

Often we need to turn the app off in order not to get annoyed by devices ringing. For example, for me it's when I leave the office, I am not supposed to answer the video door, other people who are there can take care of that. So I might need to switch on and off several times a day.

In Linphone I do this with Account settings, disable, but I wish it required less taps. It is a very frequent operation.

In Linhome there is no way to manage this except unlinking the account, and then having to reconfigure everything afterwards?

Eventually this request could extend to per-device enable/disable controls. I guess a small checkbox on the device list could let me "subscribe" to individual devices.

Thanks

Direction of development, to obtain an application token?

The product is very good for organizing intercom. What I personally liked was the initial video stream, and the beautiful interface. But there is one thing, push notifications need to be improved, since they do not work at the moment. I use my personal Asterisk server, and I can't get the device token to send a notification. It would be great if you could organize a token receiving switch for Asterisk in the settings. To send through our server. And so the product is damp, that is, without this option I see no potential. I wanted to know if there are any plans to develop in this direction? Since it is precisely because of this moment that it is not possible to implement the intercom application itself.

No pn-prid in register like linphone does...

Hi, when push is enabled on linphone, it sends a pn-prid token in the registrar header
But push is already enabled in Linhome, but i dont see any pn-prid coming in

I'm using my own json file, and was ablle to retrieve the token this way below ...

But why doesnt linhome send it to asterisk like Linphone does? do we need to enable it somewhere?

thnx

FirebaseMessaging.getInstance().token.addOnCompleteListener(OnCompleteListener { task ->
    if (!task.isSuccessful) {
        Log.w(TAG, "Fetching FCM registration token failed", task.exception)
        return@OnCompleteListener
    }

    // Get new FCM registration token
    val token = task.result

ERROR initiateIncomingStream Unable to find a suitable configuration for stream of type audio

Hey @cdeschambc

Just a small question here, can you help me out? Just installed an android studio, cloned version 1.2 from gitlab
cloned the shared themes, building was OK, launched it on my test device
Created an account on linhome.org for registering

On incoming call, 1 see the call coming in for 1 second, and then terminates, app doesnt crash, but got a 503 sip error
When i install the linhome from playstore, same account setup, it rings fine

What am i missing? i didnt change anything in the code

When i start a video call, then it keeps ringing, i can also answer, but there is no audio
something wrong indeed with audi, but what?

This is debug from an andio call:

2022-06-06 13:53:31:068 [org.linhome/liblinphone] ERROR initiateIncomingStream Unable to find a suitable configuration for stream of type audio
2022-06-06 13:53:31:185 [org.linhome/liblinphone] ERROR Bad state LinphoneCallIncomingEarlyMedia for MediaSession::acceptEarlyMedia()

This is debug from a video call


2022-06-06 13:53:39:694 [org.linhome/liblinphone] ERROR initiateIncomingStream Unable to find a suitable configuration for stream of type audio
2022-06-06 13:53:39:836 [org.linhome/mediastreamer] ERROR no such method on filter MSMediaCodecH264Decoder, fid=16389 method index=7
2022-06-06 13:53:39:836 [org.linhome/mediastreamer] ERROR no such method on filter MSAndroidTextureDisplay, fid=16387 method index=1
2022-06-06 13:53:39:836 [org.linhome/mediastreamer] ERROR no such method on filter MSAndroidTextureDisplay, fid=16387 method index=0
2022-06-06 13:53:40:000 [org.linhome/liblinphone] ERROR Bad state LinphoneCallIncomingEarlyMedia for MediaSession::acceptEarlyMedia()
2022-06-06 13:53:42:919 [org.linhome/mediastreamer] ERROR MediaCodecEncoder: I-frame requested to MediaCodec
2022-06-06 13:53:43:930 [org.linhome/mediastreamer] ERROR MediaCodecEncoder: I-frame requested to MediaCodec
2022-06-06 13:53:44:161 [org.linhome/mediastreamer] ERROR Mismatch between decoder new format and output image detected: 576x480 vs 572x468


thnx in advance!!

Linphone not working on Tablet Android 13

Hi, I am using a Dahua VTO door station as a sip server. It works perfectly fine with Linphone on the Android 13 Tablets.
However, I prefer the Linhome, because it got an action option with a code that is being sent to open a door or gate.
Linhome can be installed and devices added, but calls are not working work (it looks like it is calling, but it does not connect to the door station. And when calling another devices, it does not ring the device).
I installed linphone on a Samsung Phone (android 13 as well) in the same way and that works perfectly fine.

Any Sugggestion?

"Call was answered on another device" message

I noticed that in recent versions (maybe in the Beta 1.2 which I am using now) when I get a call from a device, but don't take the call, Linhome leaves a notification saying Call was answered on another device.

This causes me to have to swipe away dozens of annoying notifications which I couldn't care less about. Yes, somebody else is answering the door, that's good, I don't need to know.

That message needs to be made optional, or even completely removed, IMHO.

Thanks!

Push with own PBX / group calling

Hi @cdeschambc , quick question

with tha playstore edition, is it possible to use the PUSH method when running our own PBX like asterisk?
or only possible when using the free linhome ? https://subscribe.linhome.org/

if only possible with linhome services, is there a way to make group calling possible? so the door intercom can call a group of users?

thnx in advance

"Use your SIP account" problems

There are few issues in input screens when registering external SIP account (sip.linphone.org). It is possible to add that account but the way is not clear.

  1. After entering username, sip domain (sip.linhome.org) and password and pressing "Login" button, nothing happens

  2. In "Advanced settings" proxy field is empty and marked "Mandatory". Entering just sip.linphone.org doesn't work, only full form with username, ie sip:[email protected], that is not quite clear.

User experience in Call Screen

When I answer a call from my video door-phone (a recognized device I configured), I get a screen like this:

Note the absence of the status bar on top and the navigation bar (or whatever it is called) at the bottom. Here is a screenshot of the normal app screen so you can see how my phone looks, regarding the top and bottom toolbars:

If I touch anything, the Linhome buttons also disappear (Open the door, Mute, Hang up, Turn on ), and now it looks like this:

I think the logic behind all this hiding screen elements is that video screens are, for some reason, meant to be "immersive", so that I can dive into some episode of a series I am watching, etc.

None of that is a good idea for a door entry device app. Just leave everything visible on screen, please.

I want the Open the door button to stick right there, not that it disappears just because I made some accidental tap.

I want to be able to check my top status bar, for wi-fi connectivity ("why is my image so laggy?..."), the time of day ("John is arriving early..."), etc.

I want to be able to use my bottom navigation toolbar! I might want to switch apps to check some information while I am talking to the parcel delivery guy, or to send quickly a WhatsApp to somebody who is at home, but not answering the door, while I am remotely answering it.

I also have that fourth button on the right of my bottom toolbar which is important to me: it's the Accessibility feature called "Magnification shortcut". It helps people with poor eye-sight zoom in on parts of the screen. It's quite helpful while answering the door so I can quickly zoom in on the face until I recognize the person.

Getting Application Token in Contact Header for Your Asterisk Server

Good day!
Problem getting app token. I use a SIP connection through my Asterisk server. But after registering in the contact header, I do not receive the application token. I looked at another application of yours: linphone it has a setting "Allow push notification" when it is turned on, a token appears, but in this application for an intercom, I do not see it.

Confusing: google-services.json is part of this project??

Hi,

questions about push, its confuses me... in readme they mention that the google_services.json is not part of the project? that it has been added to igonore list, but if i clone this project, the file is just part of it? so is readme wrong?

Also, the included file, only works when we use SIP extentions subscribed at https://subscribe.linhome.org/ , am i right? if we use our own PBX, then we need to setup flexisip too ?

Also, when making a debug package, do we need to change it also in the google_services file "package_name": "org.linhome" => org.linhome.debug?

thnx for feedback

However to make Firebase push notifications work, the project needs to have a file named app/google-services.json that contains some confidential informations, so you won't find it (it has been added to the .gitignore file). This means that if you compile this project, you won't have push notification feature working in the app!

To enable them, just add your own google-services.json in the app folder.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.