Skip to content

Conversation

@nishadmusthafa
Copy link
Contributor

No description provided.

@changeset-bot
Copy link

changeset-bot bot commented Jul 28, 2025

🦋 Changeset detected

Latest commit: 89c753b

The changes in this PR will be included in the next version bump.

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

💥 An error occurred when fetching the changed packages and changesets in this PR
Some errors occurred when validating the changesets config:
The package or glob expression "github.com/livekit/protocol" specified in the `fixed` option does not match any package in the project. You may have misspelled the package name or provided an invalid glob expression. Note that glob expressions must be defined according to https://www.npmjs.com/package/micromatch.

@nishadmusthafa nishadmusthafa requested a review from a team August 13, 2025 17:52
@nishadmusthafa nishadmusthafa marked this pull request as ready for review August 13, 2025 17:52
import "google/protobuf/empty.proto";

// Public Phone Number Service - External API for phone number management
service PhoneNumberService {
Copy link
Contributor

Choose a reason for hiding this comment

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

If this makes it to OSS, do you think we could adapt it to Twilio API for example?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

yeah, I think that's a good idea. Would take a stab at it in a later iteration. Also as I mentioned in the comment below, we might have variations in how that is implemented in cloud/oss for things like what is supported. Billing probably is not something we might support in OSS as it would be something very custom to implementation.

Copy link
Contributor

@dennwc dennwc left a comment

Choose a reason for hiding this comment

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

Looks good now, thanks a lot! One small item remains only.

@nishadmusthafa nishadmusthafa merged commit b1e3bf2 into main Aug 19, 2025
5 checks passed
@nishadmusthafa nishadmusthafa deleted the lk-phone-numbers branch August 19, 2025 22:54
@github-actions github-actions bot mentioned this pull request Aug 19, 2025
Copy link
Member

@davidzhao davidzhao left a comment

Choose a reason for hiding this comment

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

it'd be great if we can simplify the PurchasedPhoneNumber, GlobalPhoneNumber, and PhoneNumberInventoryItem.

can they be the same object?

}

// TelephonyCost represents the pricing structure for a specific telephony service
message TelephonyCost {
Copy link
Member

Choose a reason for hiding this comment

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

I don't think this should be exposed. our other APIs don't expose cost/pricing information currently.

when we do, it should not be dependent on a particular resource. but rather types of resources.

returns (PurchasePhoneNumberResponse) {}

// List purchased phone numbers for a project
rpc ListPurchasedPhoneNumbers(ListPurchasedPhoneNumbersRequest)
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
rpc ListPurchasedPhoneNumbers(ListPurchasedPhoneNumbersRequest)
rpc ListPhoneNumbers(ListPhoneNumbersRequest)

Copy link
Member

Choose a reason for hiding this comment

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

IMO by default list is listing resources that you own

PhoneNumberStatus status = 2; // Current status of the phone number
google.protobuf.Timestamp assigned_at = 3; // Timestamp when the number was assigned
google.protobuf.Timestamp released_at = 4; // Timestamp when the number was released (if applicable)
SIPDispatchRuleInfo sip_dispatch_rule = 5; // Optional: Associated SIP dispatch rule
Copy link
Member

Choose a reason for hiding this comment

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

should this be set on the dispatch rule itself? we already have the "inbound numbers" field in there

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants