-
Notifications
You must be signed in to change notification settings - Fork 445
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
Route incoming call #788
Comments
I am not sure, i am also trying to achieve something similar, but here is how i am trying it. when using sip, we get an invite when someone calls us which we can handle using onInvite delegate of useragent. That is passed with the invitation object which is the main thing. Here is react-native-callkeep, we can use listeners to check if the call is answered or rejected or any other action is taken like this:
Then, we need to have access to the invitation object from sip and inside the onAnswerCAll function, we can call, invitation.accept() to accept the call and so on. |
Hey, Did you checked it? Is it working?
…On Fri, Jun 28, 2024, 9:49 PM Irfan Wani ***@***.***> wrote:
I am not sure, i am also trying to achieve something similar, but here is
how i am trying it. when using sip, we get an invite when someone calls us
which we can handle using onInvite delegate of useragent. That is passed
with the invitation object which is the main thing.
Here is react-native-callkeep, we can use listeners to check if the call
is answered or rejected or any other action is taken like this:
RNCallKeep.addEventListener('answerCall', onAnswerCall);
RNCallKeep.addEventListener('endCall', onEndCall);
Then, we need to have access to the invitation object from sip and inside
the onAnswerCAll function, we can call, invitation.accept() to accept the
call and so on.
—
Reply to this email directly, view it on GitHub
<#788 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AZ5AHJNVCGIQKLFCCN37D5LZJVLXPAVCNFSM6AAAAABJLJM5SKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOJWHAZTGNRTGM>
.
You are receiving this because you authored the thread.Message ID:
***@***.***
com>
|
If you are talking about the listeners, yes it is working now, still working on the sip part. |
Hi Irfan, Do you updated github repo, which could I look into ? Would you
mind sharing it. I'll also give a try :).
…On Sun, Jun 30, 2024, 8:55 PM Irfan Wani ***@***.***> wrote:
yes it is working now
—
Reply to this email directly, view it on GitHub
<#788 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AZ5AHJJ55KKVNL7ZQCGRPADZJ7W4HAVCNFSM6AAAAABJLJM5SKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOJYGUZTMNZQHE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***
com>
|
Sorry, I was just talking about the listeners. But talking about the SIP part, here is the flow, |
I tested the listeners in foreground and it works, but not when the app is killed. Also, when answering the call, call accepted screen is never shown, it just shows a blank screen and then after some time shows the incoming call UI again. |
Hello guys,
I want to forward my incoming call to SIP URI e.g Sip:[email protected]. How to achieve it?
Thanks
The text was updated successfully, but these errors were encountered: