Sipdroid 授权用户名与来电显示
我是 VOIP 领域的新手，正在为我的一位客户开发 SIPDroid。在SIPDroid的SIP帐户首选项详细信息窗口中，我可以看到有两个用户名字段。一个是“授权用户名”，另一个是“用户名或来电显示”。我的客户端有一个基于 REST 的 Web 服务来与 Asterisk 背后的服务器进行通信。
我的问题是，“授权用户名”和“用户名或来电显示”之间的区别是什么 两个字段以及它们的目的是什么。我知道，我需要一个唯一的标识符来拨打和接听电话，但是哪个字段适用于这个唯一值？
谢谢
I am very new in VOIP world and working on SIPDroid for one of my client. At the details of SIP Account Preference window of SIPDroid, I can see there are two username field. One is 'Authorization Username' and the other is 'Username or Caller ID'. My client has a REST based web service to communicate with the server behind Asterisk.
My question is, what are the difference between 'Authorization Username' and 'Username or Caller ID' two fields and what is their purpose. I know, I need a unique identifier to dial and receive call, but which field is applicable for this unique value?
Thanks
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
CallerID 用户名将用作 SIP From 标头中 SIP URI 的用户部分，例如：
绝大多数 SIP 服务器（包括 Asterisk）在收到带有 joe 的请求时将使用 joe 作为用户名来自标题。大多数 SIP 服务器也会对 URI 的服务器部分（在本例中为 from.somwhere.com）进行某种匹配，以确定请求是来自想要进行身份验证的用户还是来自想要呼叫的外部方一个用户。
授权用户名的使用频率较低，并且与 SIP 客户端在受到服务器质询时必须响应的摘要式身份验证标头中放置的值相关。身份验证标头的示例是：
在本例中，授权用户名也是 joe。当服务器在 Authorization 标头中要求的值与 From 标头中的值或您所称的 CallerID 用户名不同时，需要为 Authorization Username 指定单独的值。
The CallerID Username is what will be used as the user portion of the SIP URI in your SIP From Header, for example:
The vast majority of SIP servers out there, including Asterisk, will use joe as the username when they receive a request with that From header. Most SIP servers will do some kind of matching on the server portion of the URI as well, in this example from.somwhere.com, in order to determine if the request is from a user wanting to authenticate or from an external party wanting to call a user.
The Authorization Username is used a lot more infrequently and relates to the value to place in the Digest authentication header that a SIP client must respond to when challenged by the server. An example of an authentication header is:
In this case the Authorization Username is also joe. The need for a separate value to be specified for the Authorization Username is where the value the server requires in the Authorization header differs from the value in the From header or as you have termed it the CallerID Username.