Skip to content
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

3pcc SIP NOTIFY #556

Open
kelptan opened this issue Sep 26, 2024 · 2 comments
Open

3pcc SIP NOTIFY #556

kelptan opened this issue Sep 26, 2024 · 2 comments
Labels
enhancement New feature or request

Comments

@kelptan
Copy link

kelptan commented Sep 26, 2024

Hold or resume for incoming SIP NOTIFY messages:
◆ A NOTIFY with the 'talk' event in early dialog triggers the softphone to accept a call
(OK response to NOTIFY followed by an OK response to INVITE).
◆ A NOTIFY with the 'hold' event during a call triggers the softphone to hold the call
(OK response to a received NOTIFY and INVITE request for hold).
◆ A NOTIFY with the 'talk' event during a held call triggers the softphone to send a
re-INVITE to resume the call (OK response to a received NOTIFY and INVITE request
to resume call).

My upstream sip server is configured as 3rd party call control which sends a SIP NOTIFY to sip endpoint to answer the call, hold and resume calls.

Any idea how to go about and implement this?

Thanks,

@InnovateAsterisk
Copy link
Owner

Brower Phone supports NOTIFY messages within the context of a subscription, like a voicemail subscription or a presence subscription.

Take a look here:

function ReceiveNotify(notification, selfSubscribe) {

This is the subscription NOTIFY handler: web_hook_on_notify(ContentType, buddyObj, notification.request.body) event built in, but as I mentioned, you have to be subscribed first.

Browser Phone also supports Out-of-Dialog messages:

function ReceiveOutOfDialogMessage(message) {

This is the handler for this message: web_hook_on_message(message); But in looking at the code now, I see it rejects the message if it doesn't recognize it.

Either you would have to make your own branch, and maintain it. In this branch you would add additional handling of the notify event for you own needs, or try the events above.

If you have more documents or an RFC for the notify messages we can try support it.

@kelptan
Copy link
Author

kelptan commented Oct 2, 2024

Dear Conrad,

Basically the flow is based off rfc3725 (flow 1) with the addition of SIP Notify.
https://datatracker.ietf.org/doc/html/rfc3725#section-4.1

I'd attached the sample test calls (SIP Flow) as html file
flow.zip

you may refer to F8 and F9.
image

@InnovateAsterisk InnovateAsterisk added the enhancement New feature or request label Oct 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants