免费注册 查看新帖 |

Chinaunix

  平台 论坛 博客 文库
最近访问板块 发新帖
查看: 2317 | 回复: 0
打印 上一主题 下一主题

SIP response codes [复制链接]

论坛徽章:
0
跳转到指定楼层
1 [收藏(0)] [报告]
发表于 2006-10-16 14:00 |只看该作者 |倒序浏览

SIP response codes
SIP response codes
SIP/2.0 allows six values for the first digit:
From the SIP Rfc:
The response codes are consistent with, and extend, HTTP/1.1 response codes. Not all HTTP/1.1 response
codes are appropriate, and only those that are appropriate are given here. Other HTTP/1.1 response codes
SHOULD NOT be used. Also, SIP defines a new class, 6xx.

1xx: Provisional ¡ª request received, continuing to process the request;
Provisional responses, also known as informational responses, indicate that the server contacted is performing some further action and does not yet have a definitive response. A server sends a 1xx response if it expects to take more than 200 ms to obtain a final response. Note that 1xx responses are not transmitted reliably. They never cause the client to send an ACK. Provisional (1xx) responses MAY contain message bodies, including session descriptions.
2xx: Success ¡ª the action was successfully received, understood, and accepted;
3xx: Redirection ¡ª further action needs to be taken in order to complete the request;
4xx: Client Error ¡ª the request contains bad syntax or cannot be fulfilled at this server;
5xx: Server Error ¡ª the server failed to fulfill an apparently valid request;
6xx: Global Failure ¡ª the request cannot be fulfilled at any server.
SIP response codes, class 1: Provisional messages
These are sent within a SIP dialogue
100 Trying
180 Ringing
181 Call Is Being Forwarded
182 Queued
183 Session Progress
SIP Response codes: 2xx class
The 2xx class of responses indicates a success
200 OK
202 accepted: Used for referrals
SIP response codes, class 3xx
The 3xx class of responses indicates a redirection of the call
300 Multiple Choices
301 Moved Permanently
302 Moved Temporarily
305 Use Proxy
380 Alternative Service
SIP responses, class 4: Request failures
400 Bad Request
401 Unauthorized: Used only by registrars. Proxys should use proxy authorization 407
402 Payment Required (Reserved for future use)
403 Forbidden
404 Not Found: User not found
405 Method Not Allowed
406 Not Acceptable
407 Proxy Authentication Required
408 Request Timeout: Couldn't find the user in time
410 Gone: The user existed once, but is not available here any more.
413 Request Entity Too Large
414 Request-URI Too Long
415 Unsupported Media Type
416 Unsupported URI Scheme
420 Bad Extension: Bad SIP Protocol Extension used, not understood by the server
421 Extension Required
423 Interval Too Brief
480 Temporarily Unavailable
481 Call/Transaction Does Not Exist
482 Loop Detected
483 Too Many Hops
484 Address Incomplete
485 Ambiguous
486 Busy Here
487 Request Terminated
488 Not Acceptable Here
491 Request Pending
493 Undecipherable: Could not decrypt S/MIME body part
SIP responses, class 5: Server failures
500 Server Internal Error
501 Not Implemented: The SIP request method is not implemented here
502 Bad Gateway
503 Service Unavailable
504 Server Time-out
505 Version Not Supported: The server does not support this version of the SIP protocol
513 Message Too Large
SIP response codes, class 6: Global failures
600 Busy Everywhere
603 Decline
604 Does Not Exist Anywhere
606 Not Acceptable


本文来自ChinaUnix博客,如果查看原文请点:http://blog.chinaunix.net/u/18264/showart_185504.html
您需要登录后才可以回帖 登录 | 注册

本版积分规则 发表回复

  

北京盛拓优讯信息技术有限公司. 版权所有 京ICP备16024965号-6 北京市公安局海淀分局网监中心备案编号:11010802020122 niuxiaotong@pcpop.com 17352615567
未成年举报专区
中国互联网协会会员  联系我们:huangweiwei@itpub.net
感谢所有关心和支持过ChinaUnix的朋友们 转载本站内容请注明原作者名及出处

清除 Cookies - ChinaUnix - Archiver - WAP - TOP