-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feature request: include an RTSP stream #17
Comments
Hi @pergolafabio , I'm going to work on this feature since we also need RTSP camera support. I think of adding new device type "Audio SIP + RTSP camera" with camera's IP address. Will it do? |
That would be indeed awesome, for now I used my own compiled version with an rtsp player... But would be great if it's going to be official... Also , a nice feature is to have it as early media BUT also in call session itself, usefully for sip door intercoms without a camera... When are you going to start on this one, happy to test |
I will also use a RTSP player, as I do not know how to route RTSP stream into SIP early media. Can you share your code, it it available on github? |
Hi, no didnt share, it was a quick and dirty setup, i just changed the surface view with a player... didnt touch the device settings lie you want todo... is for personal use i used this player : https://github.com/alexeyvasilyev/rtsp-client-android , allthough its not the best one, but was verry easy to implement... just changed the view... have a look at this one, they used linphone as a source https://play.google.com/store/apps/details?id=com.basip.app&hl=nl&gl=US |
OK, I see, thanks for the links. I'm going to use libVLC for RTSP playback, ie https://lindevs.com/display-rtsp-stream-from-ip-camera-using-libvlc-on-android Since we already use libphone native libs, adding libvlc shouldn't do much harm ) |
cool, nice to hear |
Hey @mixaz , is there already some progress?? |
Unfortunately not, current status is - I built linhome app from source code OK, but it has problems:
Since the app from GP works OK, I checked its linphone core version - it's 4.5.0 against 5.2.1-pre.4 in https://gitlab.linphone.org/BC/public/linhome-android. I tried to downgrade source code to last commit with 4.5.0 https://gitlab.linphone.org/BC/public/linhome-android/-/commit/1d5c3fcb2aabb3ae0d64a4350cae646bf72bda84 but got Kotlin code being not compiled. I haven't sorted it out, and I think the matter is different. Googling for "linphone drops call after 30 seconds" brought few topics like BelledonneCommunications/linphone-android#1395, saying that the issue relates to "push notifications" settings in the app. This setting is not available in linhome app, so I can't test. I'm testing my own build of linhome app, signed with a debug key, on sip.linphone.org server. I think that it can cause firebase push notifications not being sent from flexisip to andriod app. My signing key is not registered with firebase app https://gitlab.linphone.org/BC/public/linhome-android/-/blob/master/app/google-services.json. So I either need to deploy my own firebase+flexysip instances for my key, changing the package name, or sign with original linhome key. I see https://gitlab.linphone.org/BC/public/linhome-android/-/blob/master/linhome.keystore which probably has that key, but it needs a password. And source code mentions other keystore file https://gitlab.linphone.org/BC/public/linhome-android/-/blob/master/keystore.properties#L4 My current plan is to check the issue with linphone app, as it has better support and guides. I'm going to build linphone from sources. What is your setup, you said you use a custom linhome app - did you setup firebase+flexisip instances for it? |
Hi, i always tested with Asterisk, and most of the times call drops after 30 sec, means no audio/video for me in two way, was just a misconfiguration in Asterisk or ports setup... I created my own json file , and compiled linhome with it.... From Asterisk, before i do the call, i do a curl command to wake up linhome with my own firebase, works great Dont you have an Asterisk? |
Hello, |
I've built linphone from source, and it works OK, without those issues. Linphone SDK 5.2.1-pre.5. @cdeschambc, can you suggest what to do further to resolve the issue - shall I compare logs between working linhome app from GP and not working one built from sources? Or should I provide it to you? I'm not familiar with SIP protocol. From that linphone app doesn't have the issues, and you say linhome one sends linhome account to sip.linphone.org as "dependent" sip proxy config - may the issue be caused by not working sip.linhome.org, as I reported in #28 ? I tested it with linhome app in GP, it fails to connect to the SIP server either. And I can't explain why linhome GP app works OK with "use your SIP account". Could you please check that you don't have the "drop call after 30 seconds" issue with debug version of linhome built from source code in gitlab? I mean the case when the app is signed by other key, not yours. |
Keeping my eye out on this one, Would love to know if there is any development progress |
Hey @mixaz , have you an update for us? |
Sorry, I didn't work on it much. The issue with call dropping after 30 seconds is more critical IMO, and should be addressed first. Now I'm working on other project, and most likely I won't work on this one. |
Oh, that's really to bad, how can we help with those 30 sec? Really love to see rtsp preview in Linhome, it's specially for door intercoms, imo rtsp is a musthave for doorbells without camera |
Hey @mixaz , still working on this? @cdeschambc , I see you are very busy on 1.2 release? When can we expect the final release? :-) |
@pergolafabio I'm sorry, I'm busy on other projects ( |
Oh that's too bad :-( Was hoping to see RTSP supports, would be a great advantage for intercom purposes Thnx for feedback |
Hi, great Guru! Do u have any news of RTSP supports? |
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
The text was updated successfully, but these errors were encountered: