我想在我的java应用程序中构造一个电话呼叫者。为此,我使用了JAIN-SIP库。在第一次邀请之后,系统需要代理身份验证。第二个邀请是在"AuthenticationHelperImpl.class":https://gitorious.org/0xdroid/external_nist-sip/source/1e0f37693341071f316852c8e05a08deef2b7fc4:java/gov/nist/javax/sip/clientauthutils/AuthenticationHelperImpl.java#L311 的帮助下构建的,包括代理身份验证标头和lloks,例如:
INVITE sip:+11111111111@fpbx.de;maddr=fpbx.de SIP/2.0
Call-ID: 1c609509a43b721ab11c396c1e6ea9e7@192.168.17.107
CSeq: 2 INVITE
From: "77735hk6iu" <sip:77735hk6iu@fpbx.de>
To: "+111111111111111" <sip:+11111111111@fpbx.de>
Via: SIP/2.0/UDP 192.168.17.107:34567;rport;branch=z9hG4bK-383337-5bc4fd6b7a616843fce9eaa243bcb10e
Max-Forwards: 70
Contact: <sip:77735hk6iu@192.168.17.107:5060>
Content-Type: application/sdp
Proxy-Authorization: Digest username="77735hk6iu",realm="fpbx.de",nonce="VLaIxVS2h5muPS30F2zLdXHjup6ELyen",uri="sip:+111111111111@fpbx.de:5060;maddr=fpbx.de",response="47ea578c6b01c99fd3ed2b41c60983df"
Content-Length: 61
v=0
o=- 130565705777141827 1 IN IP4 192.168.17.107
s=call
之后,我在开头收到代码 100 消息("您的电话对我们非常重要"),然后是 408 代码消息("请求超时")。
我做了什么来改善这种情况:
尝试了不同的电话号码格式:004930208488480,04930208488480, 049, 0049, sdfhajfkhsk.对于所有这些数字,我在消息上成为相同的组合。
尝试在请求 URI 中使用端口
尝试从请求 URI 中删除 MADDR。
尝试使用Codek设置填充邮件正文。
从 via 标头中设置和删除 rport
如果你现在知道我做错了什么,请帮助我。提前谢谢你。
我想,也许你的代理授权标头是错误的。也许你失算了。我想分享我的决心。
authUser 是您的电话号码。(例如:77735HK6IU)authPass 是您用户的密码。味精是您的邀请请求。(标题!
AccountManagerImpl accountManagerImp = new AccountManagerImpl(authUser, AuthPass);
AuthenticationHelperImpl authenticationHelperImpl = new AuthenticationHelperImpl(accountManagerImp);
try {
this.authentication = authenticationHelperImpl.handleChallenge(msg, (SIPClientTransaction)trans);
AuthenticationHelperImple.java 类 :
public AuthorizationHeader handleChallenge(Response challenge, ClientTransaction challengedTransaction) throws SipException {
SIPRequest challengedRequest = ((SIPRequest) challengedTransaction.getRequest());
ListIterator authHeaders = null;
if (challenge.getStatusCode() == Response.UNAUTHORIZED) {
authHeaders = challenge.getHeaders(WWWAuthenticateHeader.NAME);
}
else {
if (challenge.getStatusCode() == Response.PROXY_AUTHENTICATION_REQUIRED) {
authHeaders = challenge.getHeaders(ProxyAuthenticateHeader.NAME);
}
else {
throw new IllegalArgumentException("Unexpected status code ");
}
}
if (authHeaders == null) {
throw new IllegalArgumentException("Could not find WWWAuthenticate or ProxyAuthenticate headers");
}
WWWAuthenticateHeader authHeader = null;
while (authHeaders.hasNext()) {
authHeader = (WWWAuthenticateHeader) authHeaders.next();
String realm = authHeader.getRealm();
this.uri = challengedRequest.getRequestURI();
this.requestMethod = challengedRequest.getMethod();
this.requestBody = (challengedRequest.getContent() == null) ? "" : new String(challengedRequest.getRawContent());
if (this.accountManager instanceof SecureAccountManager) {
UserCredentialHash credHash = ((SecureAccountManager) this.accountManager).getCredentialHash(challengedTransaction,
realm);
if (credHash == null) {
logger.logDebug("Could not find creds");
throw new SipException("Cannot find user creds for the given user name and realm");
}
this.authorizationHeader = this.getAuthorization(requestMethod, uri.toString(), requestBody, authHeader, credHash);
}
else {
UserCredentials userCreds = ((AccountManager) this.accountManager).getCredentials(challengedTransaction, realm);
if (userCreds == null) {
throw new SipException("Cannot find user creds for the given user name and realm");
}
// sipDomain = userCreds.getSipDomain();
// we haven't yet authenticated this realm since we were
// started.
this.authorizationHeader = this.getAuthorization(requestMethod, uri.toString(), requestBody, authHeader, userCreds);
}
}
return this.authorizationHeader;
}
获取授权函数:
public AuthorizationHeader getAuthorization(String method,
String uri,
String requestBody,
WWWAuthenticateHeader authHeader,
UserCredentials userCredentials) throws SecurityException {
String response = null;
String qopList = authHeader.getQop();
String qop = (qopList != null) ? "auth" : null;
String nc_value = "00000001";
String cnonce = "xyz";
try {
response = MessageDigestAlgorithm.calculateResponse(authHeader.getAlgorithm(),
userCredentials.getUserName(), authHeader.getRealm(),userCredentials.getPassword(), authHeader.getNonce(), nc_value, // JvB added
cnonce, // JvB added
method, uri, requestBody, qop,logger);
}
catch (NullPointerException exc) {
throw new SecurityException("The received authenticate header was malformatted: " + exc.getMessage());
}
AuthorizationHeader authorization = null;
try {
if (authHeader instanceof ProxyAuthenticateHeader) {
if (this.headerFactory != null) {
authorization = headerFactory.createProxyAuthorizationHeader(authHeader.getScheme());
}
else {
authorization = new ProxyAuthorization();
authorization.setScheme(authHeader.getScheme());
}
}
else {
if (this.headerFactory != null) {
authorization = headerFactory.createAuthorizationHeader(authHeader.getScheme());
}
else {
authorization = new Authorization();
authorization.setScheme(authHeader.getScheme());
}
}
authorization.setUsername(userCredentials.getUserName());
authorization.setRealm(authHeader.getRealm());
authorization.setNonce(authHeader.getNonce());
authorization.setParameter("uri", uri);
authorization.setResponse(response);
if (authHeader.getAlgorithm() != null) {
authorization.setAlgorithm(authHeader.getAlgorithm());
}
if (authHeader.getOpaque() != null) {
authorization.setOpaque(authHeader.getOpaque());
}
// jvb added
if (qop != null) {
authorization.setQop(qop);
authorization.setCNonce(cnonce);
authorization.setNonceCount(Integer.parseInt(nc_value));
}
authorization.setResponse(response);
} catch (ParseException ex) {
throw new RuntimeException("Failed to create an authorization header!");
}
return authorization;
}
最后,您的 this.authentication 变量是 ProxyAuthorizationHeader。您必须将此。身份验证放在您的邀请消息中。然后,您将SipMessage从事务或对话框发送到JAIN-SIP堆栈。
祝你好运!
当从请求 URI 和代理身份验证中删除"maddr=fpbx.de"时,该问题已部分解决。
fpr 这是一个使用带有布尔参数的句柄Cahllenge方法:
inviteTid = authenticationHelper.handleChallenge(response, tid, sipProvider, 15, **true**);
但是我仍然不知道我怎么能找到一个漂亮的电话号码。
100 消息是逐跳的,也就是说,它只是意味着下一跳收到了您的请求。 其他消息通常是端到端的(因此,如果您收到 180 振铃,这通常意味着被调用的终结点发送了 180)。 当其中一个跃点发送邀请但从未收到响应时,通常会显示 408(并且您的 SIP 堆栈可能会在合理的时间范围内未获得临时响应时在内部生成该响应 - 通常使用默认 SIP 计时器大约 32 秒)。
我不知道您的网络设置,但该消息中有几个私有 IP(192.168.x.x 品种)。 如果我不得不猜测,您的第一个跃点是将 100 发送回它接收它的 IP/端口,但下一个响应遵循 Via 标头(它应该),并且您之后的跃点不尊重 rport 参数,因此响应丢失了。 或者,您的 NAT 配置不佳,并且过快地关闭了它为 INVITE 创建的漏洞。
如果您在网络边缘有一个代理,此消息正在发出,它要么在消息上放置错误的 Via 标头(可能使用内部 IP 而不是外部 IP),要么将 INVITE 发送到错误的位置(导致它永远不会得到响应),并且 408 来自它。