Skip to content

Conversation

@nickvergessen
Copy link
Member

@nickvergessen nickvergessen commented Mar 27, 2025

☑️ Resolves

🛠️ API Checklist

🏁 Checklist

  • ⛑️ Tests (unit and/or integration) are included or not possible
  • 📘 API documentation in docs/ has been updated or is not required
  • 🔖 Capability is added or not needed

@nickvergessen nickvergessen added this to the 🪺 Next Major (32) milestone Mar 27, 2025
@nickvergessen nickvergessen self-assigned this Mar 27, 2025
@nickvergessen nickvergessen force-pushed the feat/14418/sip-dialin-calling branch from 89d895b to 52483d9 Compare April 2, 2025 15:43
@nickvergessen
Copy link
Member Author

/backport to stable31

@nickvergessen nickvergessen force-pushed the feat/14418/sip-dialin-calling branch from 52483d9 to f4bc5d9 Compare April 14, 2025 19:46
@fancycode
Copy link
Member

On a more general note: some customers might use internal phone extensions, i.e. not fully E.164 formatted. This will cause the validation to fail both here and in #14729. In such cases, numbers will be short.

I would suggest supporting these both in #14729 and here, i.e. everything that is all-numeric (with an optional leading +) will be considered to be a phone number. This then matches both short internal extensions and full E.164 numbers.

@fancycode
Copy link
Member

We probably need a dedicated response code for when the regular call workflow should be used, or should that always happen on 404?

@nickvergessen
Copy link
Member Author

or should that always happen on 404?

I'm not really sure I can distinguish a random number from a workflow one. So yeah I'd say 404 means there is no direct-dialin => normal workflow?

@nickvergessen nickvergessen force-pushed the feat/14418/sip-dialin-calling branch 4 times, most recently from 0d7cdf8 to b227252 Compare April 24, 2025 14:11
@nickvergessen
Copy link
Member Author

nickvergessen commented Apr 28, 2025

  • Conversation is not marked as "In call" yet
  • Neither does the called user receive a notification

@fancycode fancycode changed the title feat(sip): All the sipbridge to create a conversation with a user for a phone number feat(sip): Allow the sipbridge to create a conversation with a user for a phone number Apr 28, 2025
@nickvergessen nickvergessen force-pushed the feat/14418/sip-dialin-calling branch 4 times, most recently from 35d8780 to a5eee09 Compare April 28, 2025 15:08
@nickvergessen
Copy link
Member Author

nickvergessen commented Apr 28, 2025

/backport 2dad1f7 to stable30

@nickvergessen
Copy link
Member Author

nickvergessen commented Apr 28, 2025

/backport 2dad1f7 to stable31.0

@fancycode
Copy link
Member

Web-UI tries to call the phone user when clicking the button to join the call.

POST-URL is https://myserver/ocs/v2.php/apps/spreed/api/v4/call/<token>/dialout/%7BattendeeId%7D.

Copy link
Member

@fancycode fancycode left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The triggered dial-out when joining from the web should be fixed imho, the display name is nice to have.

@nickvergessen
Copy link
Member Author

The triggered dial-out when joining from the web should be fixed imho, the display name is nice to have.

It was done from frontend, but fixed it myself

… a phone number

Signed-off-by: Joas Schilling <coding@schilljs.com>
Signed-off-by: Joas Schilling <coding@schilljs.com>
Signed-off-by: Joas Schilling <coding@schilljs.com>
Signed-off-by: Joas Schilling <coding@schilljs.com>
Signed-off-by: Joas Schilling <coding@schilljs.com>
@nickvergessen nickvergessen force-pushed the feat/14418/sip-dialin-calling branch from 9c68e0e to da463a9 Compare April 30, 2025 07:37
#[OpenAPI(scope: 'backend-sipbridge')]
public function directDialIn(string $phoneNumber, string $caller): DataResponse {
if (!$this->talkConfig->isSIPConfigured()) {
return new DataResponse(null, Http::STATUS_NOT_IMPLEMENTED);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should we also throttle the "not implemented" response?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

you are not able to brute force the sip secret, so I don't think it's needed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants