Gateway 503 Service Unavailable

一、问题排查

  • 昨天升级了一下老项目的 SpringBoot 、SpringCloud版本。
    spring-boot-starter-parent 和 spring-boot 从 2.1.14.RELEASE 升级到2021年版本的最高版 2.6.8 版本。

    spring-cloud-starter-gateway 2.1.5.RELEASE 升级到了最新版的 spring-cloud-starter-gateway 3.1.3

  • 升级完后,发现网关 Gaterway 转发 503,如下图:
    网关503

  • 没升级之前是正常的,排除其他改动导致的问题。

  • 查看网关的配置,大概如下。点击每个配置项都能正常跳转,说明不是配置结构变动问题。

server:
  port: 88
spring:
  application:
    name: xxx-gateway
  cloud:
    gateway:
      routes:
        #        - id: qq_router
        #          uri: https://www.qq.com
        #          predicates:
        #            - Query=url,qq
        #
        #        - id: baidu_router
        #          uri: https://www.baidu.com
        #          predicates:
        #            - Query=url,baidu
        - id: product_router
          uri: lb:http://xxx-product
          predicates:
            # 路径断言:符合 /api/product/** 才放行
            - Path=/api/product/**
          filters:
            # 路径重写,将所有“/api”的请求替换为“/”,相当于去掉“api”
            - RewritePath=/api(?<segment>/?.*), /$\{segment}

        # 配置 Host 域名路由到 xxx-product 服务
        - id: xxx_product_route
          uri: lb:http://xxx-product
          predicates:
          	- Host=xxx.com

  • 发现配置项的 uri: lb:http:xxx.com 都用了 lb(负载均衡),难道是负载均衡不起作用?去掉lb:后发现能正常跳转了。果然…
  • 但是,我还是想加 lb负载均衡呀,然后查SpringBootC官方文档(),发现lb用法还在,猜测:lb用法在但是不起作用,那很有可能是负载均衡的实现内核发生了变动,比如:没有引入负载均衡依赖导致的。

lb 用法

二、解决:

  • 显式的引入spring-cloud-starter-loadbalancer 负载均衡依赖(Ribbon在高版本中已经被干掉)。
  • 不用指定版本,gateway 内部已经帮我们设置了版本。
    重新引入了 spring-cloud-starter-loadbalancer负载均衡依赖后,恢复lb 写法,测试,跳转正常。
        <dependency>
            <groupId>org.springframework.cloud</groupId>
            <artifactId>spring-cloud-starter-gateway</artifactId>
        </dependency>
<!--引入 loadbalancer 负载均衡依赖,替代 Ribbon-->
        <dependency>
            <groupId>org.springframework.cloud</groupId>
            <artifactId>spring-cloud-starter-loadbalancer</artifactId>
        </dependency>

三、版本对比

低版本 依赖图
spring-cloud-gateway 3.1.3 依赖图

参考文档:

  • 5
    点赞
  • 3
    收藏
    觉得还不错? 一键收藏
  • 1
    评论
Fikker 是一款面向广大站长的专业级网站加速服务器软件,跨平台,全界面化管理,利用页面缓存技术(webcache),网站管理员或开发人员通过 Fikker 管理平台将指定的页面缓存起来,其他用户在访问相同页面时候,就不需要网站读取数据库后再生成页面了,Fikker 直接返回用户需要的页面,响应速度成倍提升;另外 Fikker 通过 gzip 将页面(html,asp,php,css,js)压缩起来,减少了传输尺寸,提高传输效率和减少带宽占用。 Fikker缓存加速服务器设计与实现,包含了详细的网络设计,缓存技术设计,容错处理,gzip 设计,防盗链设计,主机管理设计,转向设计等。采用 C 语言实现。 目录: 1. 系统说明 2. 全非阻塞(non-block)网络设计 2.1. 全非阻塞设计说明 2.2. 网络负载均衡设计说明 2.3. 图例说明 3. 缓存设计 3.1. 缓存说明 3.2. 智能缓存设计 3.3. 强制缓存设计 3.3.1. 公共缓存 3.3.2. 会员缓存 3.3.3. 游客缓存 3.3.4. 会员缓存设计背景 3.3.5. 图例说明 3.4. 拒绝缓存设计 3.5. 清理缓存设计 3.6. 缓存优先级设计 3.7. 页面匹配规则设计 3.8. 缓存页面淘汰算法设计 3.8.1. 缓存页面淘汰说明 3.8.2. 缓存页面淘汰优先级 3.8.3. 同一优先级时淘汰规则 3.9. 页面压缩gzip设计 3.9.1. 说明 3.9.2. HTTP头中有关gzip压缩的字段 3.9.3. 页面压缩的实现 4. URL转向设计 4.1. URL转向简介 4.2. 转向逻辑 4.3. 简单举例 5. 防盗链设计 5.1. 防盗链说明 6. 黑名单设计 6.1. 黑名单说明 7. 代理设计 7.1. 代理介绍 7.2. 负载均衡策略 7.3. 负载均衡图例 8. 流量统计设计 8.1. 流量统计说明 8.2. 总量统计 8.3. 分量统计 Fikker 设计与实现V3 home:http://www.fikker.com 3 9. 实时监控设计 9.1. 实时监控说明 10. Windows 和Linux 兼容性设计 10.1.绿色安装包 10.2.Fikker 的运行权限 10.3.配置文件兼容性 11. 关于Fikker限制的说明 11.1.内存限制 11.2.连接数限制 11.3.HTTP 头尺寸限制 11.4.缓存页面尺寸限制 11.5.操作系统限制 12. Fikker 与HTTP 头 13. 关于Fikker返回错误页面的说明 13.1. 400 Bad Request 13.2. 403 Forbidden 13.3. 409 Conflict 13.4. 502 Bad Gateway 13.5. 503 Service Temporarily Unavailable
RELEASE NOTES FOR MICROSOFT(R) TCP/IP-32 FOR WINDOWS(TM) FOR WORKGROUPS 3.11 PLEASE READ THIS ENTIRE DOCUMENT General ------- This product is compatible with, and supported exclusively on, the Microsoft Windows For Workgroups 3.11 platform. If you are running a different TCP/IP product on your system, you must remove it before installing Microsoft TCP/IP-32. If you experience difficulties with another vendor's product, remove the existing TCP/IP stack, exit Network Setup completely, reboot your system, and then proceed to add the Microsoft TCP/IP-32 drivers by following the instructions given in the documentation. Known Problems -------------- There have been a number of reports on IBM TokenRing, EtherLink III cards, and ODI drivers that are related to bugs in drivers other than TCP/IP-32. These Windows For Workgroups 3.11 patches are described in the following Application Notes: WG0990 (contains updated ELNK3.386) WG0988 (contains updated IBMTOK.386) WG1004 (contains updated MSODISUP.386) You can obtain these Application Notes from the following sources: - The Internet (ftp.microsoft.com) - CompuServe(R), GEnie(TM), and Microsoft OnLine - Microsoft Download Service (MSDL) - Microsoft Product Support Services On CompuServe, GEnie, and Microsoft OnLine, Application Notes are located in the Microsoft Software Library. You can find an Application Note in the Software Library by searching on a keyword, for example "WG0990". Application Notes are available by modem from the Microsoft Download Service (MSDL), which you can reach by calling (206) 936-6735. This service is available 24 hours a day, 7 days a week. The highest download speed available is 14,400 bits per second (bps). For more information about using the MSDL, call (800) 936-4200 and follow the prompts. Previous Beta Users ------------------- If you had installed a previous beta of the Microsoft TCP/IP-32 for Windows for Workgroups product, you may encounter one of the following errors: "Setup Error 108: Could not create or open the protocol.ini file." "Setup Error 110: Could not find or open win.ini." If this happens do the following: 1) Remove any previous versions of Microsoft TCP/IP-32. 2) Exit Network Setup and restart your system. 3) Rename any OEMx.INF (where x is any number) files that are in your WINDOWS\SYSTEM directory. 4) Go back into Network Setup and install Microsoft TCP/IP-32 following the installation instructions in the manual. Mosaic ------ NCSA's Win32s version of their popular Mosaic application requires that you pick up version 115a or greater of the Win32s distribution to function correctly. DHCP Automatic Configuration ---------------------------- DHCP is a new TCP/IP protocol that provides the ability to acquire TCP/IP addressing and configuration dynamically with no user intervention. DHCP depends on your network administrator to set up a DHCP server on your network. A DHCP server is scheduled to ship as part of Windows NT(TM) Server version 3.5. If you enable automatic DHCP configuration without a DHCP server available on your network, the following message will appear after approximately a 10 second black-screen delay during the Windows for Workgroups booting process: "The DHCP client was unable to obtain an IP network address from a DHCP server. Do you want to see future DHCP messages?" This message means that TCP/IP has initialized but without any addressing information. If you are running TCP/IP as your only protocol, you will not have access to the network. This situation requires that you go back to the TCP/IP configuration settings, disable DHCP, and manually specify your TCP/IP network parameters. If you are running multiple protocols, you should have access to your network with these. If you do have a DHCP server on your network and this message appears, this indicates that the server was unavailable and that your lease has expired. DHCP will (in the background) continue to try to acquire a valid lease while Windows for Workgroups continues to run (although you will not have TCP/IP functionality). If you are running with DHCP automatic configuration, use the IPCONFIG utility to learn your IP configuration. DHCP Options ------------ The following changes are not reflected in the TCP/IP-32 documentation. Currently Microsoft DHCP clients support only the following options: - DHCP protocol options - DHCP message type (53) - Lease Time (51), Renewal Time (58), Rebind Time (59) - Information options: - Subnet Mask (1) - Default Router (3) - DNS Server (6) - WINS Server (NetBIOS Name Server) (44) - NetBIOS Node Type (46) - NetBIOS Scope Id (47) Any other options received by the client are ignored and discarded. No Option Overlays - Option Limit Is 336 Bytes ---------------------------------------------- The DHCP client does not recognize option overlays. If a non-Microsoft server is sending the options, make sure that either all the options fit within the standard option field, or at least that those used by the Microsoft clients (listed above) are conta ined in the standard Option field. Since the Microsoft client only supports a subset of the defined DHCP option types, 336 bytes should be sufficient for any configuration. Ipconfig - Moving Client to New Address --------------------------------------- When a DHCP client is moved to a new reserved address or is moved from an address to make way for an exclusion or another client's reservation, the client should first release its current address using ipconfig /release. This may be followed by ipconfig /renew to get a new address. ARP Conflicts - Report to DHCP Server Administrator --------------------------------------------------- Before the TCP/IP stack comes up with the address acquired via DHCP, the stack ARPs for the address. If a machine is already running with this address, the client will display a popup informing the user of the address conflict. Users should contact the CP server administrator when this occurs. Once the server has excluded the conflicting address, the client should get a new address using ipconfig /renew. If this is unsuccessful, the client may need to reboot. NetBIOS over TCP/IP ------------------- Multihomed Computer NetBIOS Node Type A computer can be one of four NetBIOS node types: broadcast node, mixed node, point-to-point node, or hybrid node. The node type cannot be specified per network adapter card. In some circumstances, it may be desirable to have one or more network adapter c ards function as broadcast nodes and other network adapter cards to function as hybrids. You accomplish this by setting the node type to broadcast node, and configuring WINS name server addresses for the network adapter cards that will function as hybrids. The presence of the WINS addresses will effectively override the broadcast node setting for the adapters on which they are set. To make an adapter a broadcast node, configure DHCP to set the node type to Bnode, or in the absence of DHCP, the computer will assume Bnode behavior by default. Including Remote LMHOSTS Files You must modify the Registry of a remote computer if network clients will #INCLUDE the LMHOSTS file on the remote Windows NT computer. The share containing the LMHOSTS file must be in the Null Sessions list on the Server by adding the share name to the following Windows NT Registry key: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services \LanManServer\Parameters\NullSessionShares Microsoft TCP/IP Workstations with UB NetBIOS Name Servers ---------------------------------------------------------- The Microsoft clients can be configured to use a UB name server by adding the SYSTEM.INI parameter RefreshOpCode under the [NBT] section. Set its value to 9 to interoperate with UB name servers. NetDDE Applications Communicating over Subnets via LMHOSTS ---------------------------------------------------------- If you are connecting to a remote machine via a NetDDE application, using a #PRE LMHOSTS entry, you must have a separate entry specifying a special character in the 16th byte: 138.121.43.100 REMOTEDDE #PRE 138.121.43.100 "REMOTEDDE \0x1F" A special entry is not required if #PRE is not used. Browsing Resources on Remote IP Subnetworks ------------------------------------------- Browsing remote IP subnetworks requires a Windows NT computer on the local subnet. Using File Manager to Access Servers Specified in LMHOSTS --------------------------------------------------------- Reading and parsing LMHOSTS to resolve a name is done by the NBT driver at run time. This operation is not permissible under certain conditions. One such condition commonly encountered is when a network connection is attempted from the File Manager. The result is that the name is reported as 'not resolved' even if the name exists in LMHOSTS file (since the driver wasn't even allowed to open LMHOSTS file). The workaround for such conditions is to put a #PRE against the name in the LMHOSTS file. This causes the name to be stored in the name cache when the machine is first initialized, so the name gets resolved without the driver having to open LMHOSTS at run time. IP Routing ---------- Multiple Default Gateways in Microsoft TCP/IP Act as Backup Gateways When more than one default gateway is specified for a given IP network or for multiple IP networks on different network cards, the first default gateway for the first network card is always used to route IP network traffic. All the subsequent gateways are used as backup when the first default gateway is discovered to be unavailable. The Dead Gateway Detection mechanism is used only with TCP (connection-oriented traffic). Therefore, utilities like PING will only use the first default gateway. Notice that t his only applies to IP datagrams that have to be routed to a remote network (that is, to a network to which the workstation is not directly connected). FTP --- FTP is implemented in a Windows console in this release. It is not presently hooked to the Microsoft TCP/IP-32 Help file, although the Help file does have FTP command summaries in it. Many of the documented command line options are supported, although they require you to modify your FTP Program Item manually. The FTP application which ships with this product does not support the "!" command, which typically invokes a user shell. ODI Driver Support ------------------ Due to system restrictions, TCP/IP-32 cannot support more than one network adapter using ODI drivers. Multihomed configurations are supported using NDIS drivers only. If after installing TCP/IP-32 you have problems accessing the network over your ODI drivers, please make sure that the syntax and frame types listed in your NET.CFG file are correct for your network. DNS Resolution Hierarchy ------------------------ The Microsoft TCP/IP-32 stack uses various means to resolve a host name to get the IP address of a certain host. The various mechanisms used are Local Cached Information, Hosts File, DNS Servers, and NetBIOS name resolution mechanisms. The default resolution order for resolving a host name is Local Cached Information -> Hosts File -> DNS Servers -> NetBt (NetBIOS over TCP/IP). NetBIOS over TCP/IP name resolution can consist of local subnet broadcasts, and/or querying the Windows Internet Names Server (WINS) running on Windows NT Servers. Your Guide to Service and Support for Microsoft TCP/IP-32 --------------------------------------------------------- Microsoft Support: Network Advanced Systems Products Support Options The following support services are available from Microsoft for Microsoft Advanced Systems products, including Microsoft Mail Server and its gateways, SQL Server, LAN Manager, Windows NT Workstation, Windows NT Server, and SNA Server. Electronic Services ------------------- Microsoft Forums ---------------- These forums are provided through the CompuServe Information Service, (800) 848-8199, representative 230 (sales information only). Access is available 24 hours a day, 7 days a week, including holidays. These forums enable an interactive technical dialog between users as well as remote access to the Microsoft KnowledgeBase of product information, which is updated daily. These forums are monitored by Microsoft support engineers for technical accuracy. If you are already a subscriber, type "GO <forum name>" at any ! prompt. MSCLIENT Microsoft Network Client support WINNT Microsoft Windows NT support MSSQL Microsoft SQL Server support MSWRKGRP Microsoft Windows for Workgroups support MSNETWORKS Microsoft LAN Manager support MSAPP Microsoft applications support MSWIN32 Information on Win32 MSDR Development-related discussion forum WINEXT Support for extensions and drivers for Windows WINSDK Support for Microsoft Windows Software Development Kit Microsoft Download Service -------------------------- Use the Microsoft Download Service (MSDL) to access the latest technical notes on common advanced system products support issues via modem. MSDL is at (206) 936-6735, available 24 hours a day, 7 days a week, including holidays (1200, 2400, or 9600 baud; no parity, 8 data bits, 1 stop bit). Internet -------- Use the Internet to access the Microsoft Driver Library and Microsoft KnowledgeBase. The Microsoft Internet FTP archive host FTP.MICROSOFT.COM (ip address 198.105.232.1) supports anonymous login. When logging in as anonymous, please offer your complete e-mail name as your password. Telephone Support ----------------- Microsoft FastTips ------------------ An interactive, automated system providing support at no charge through toll lines and accessed by touch-tone phone. FastTips provides fast access to answers to common questions and a library of technical notes delivered by phone recording or fax. FastTips is available 24 hours a day, 7 days a week, including holidays. Microsoft Advanced Systems products (800) 936-4400 Priority Telephone Support -------------------------- Get technical support from a Microsoft engineer. Microsoft offers pay-as-you-go telephone support from a Microsoft engineer, available 24 hours a day, 7 days a week, except holidays. Choose from the following options: Per Incident: Dial (900) 555-2100. $150.00 per incident. (Charges appear on your telephone bill.) Per Incident: Dial (800) 936-5900. $150.00 per incident. (Charges billed to your Visa, Master Card, or American Express.) 10-pack: Ten incidents for $995 prepaid. Additional Information ---------------------- For additional information about Microsoft support options or for a list of Microsoft Solution Providers, call Microsoft Support Network Sales and Information Group at (800) 936-3500, Monday through Friday, 6:00 A.M. to 6:00 P.M., Pacific time, excluding holidays. This list includes only domestic support programs. Microsoft's customer support services are subject to Microsoft's then-current price, terms, and conditions.
sip RFC3261 中文版 1、SIP协议介绍 10 2、SIP协议功能概况 10 3、术语 12 4、实施概览 12 5、协议的结构 22 6、协议的定义 24 7、SIP消息: 32 7.1 请求 33 7.2应答 34 7.3 头域 35 7.3.1 头域格式。 35 7.3.2 头域分类。 39 7.3.3 缩写格式 39 7.4包体 39 7.4.1 消息正文类型(MessageBodyType) 39 7.4.2 消息体长度 40 7.5 分帧的SIP消息(Framing SIP Messages) 40 8 一般用户代理行为 40 8.1 UAC特性 41 8.1.1 产生一个请求 41 8.1.1.1 Request-URI 42 8.1.1.2 TO 42 8.1.1.3 From 43 8.1.1.4 Call-ID 44 8.1.1.5 Cseq 45 8.1.1.6 Max-Forwards 45 8.1.1.7 Via 45 8.1.1.8 Contact 46 8.1.1.9 Supported 和 Require 47 8.1.1.10 附加信息部分 47 8.1.2 发送一个请求 47 8.1.3 处理应答 48 8.1.3.1: transaction 层的错误 49 8.1.3.2 未知的应答 49 8.1.3.3 Vias 49 8.1.3.4 处理3xx应答 49 8.1.3.5 处理4xx应答 51 8.2 UAS特性 52 8.2.1 方法判定 53 8.2.2 包头判断 53 8.2.2.1 TO 和Request-URI 53 8.2.2.2 合并的请求 54 8.2.2.3 Require 54 8.2.3 内容处理 55 8.2.4 应用扩展 55 8.2.5 处理请求 56 8.2.6 产生应答 56 8.2.6.1 发送一个临时应答 56 8.2.6.2 包头和Tags 57 8.2.7 无状态UAS行为 57 8.3 重定向服务器 58 9 取消一个请求(Cancel) 60 9.1 客户行为(Client Behavior) 60 9.2 服务端行为(Server Behavior) 62 10 注册(Registrations) 63 10.1 概览 63 10.2 构造一个REGISTER请求 64 10.2.1 增加绑定 66 10.2.1.1 设置Contact地址的过期参数 67 10.2.2 删除绑定 68 10.2.3 访问绑定 68 10.2.4 刷新绑定 69 10.2.5 设置内部时钟 69 10.2.6 寻找注册服务器 69 10.2.7 传送一个请求 70 10.2.8 错误响应 70 10.3 处理REGISTER请求 70 11 查询能力 73 11.1 构造OPTIONS请求 74 11.2 处理OPTIONS请求 75 12 对话(Dialog) 77 12.1 创建一个对话 78 12.1.1 UAS行为 78 12.1.2 UAC行为 79 12.2 对话中的请求 80 12.2.1 UAC行为 81 12.1.1.1 产生请求 81 12.2.1.2 处理应答 83 12.2.2 UAS行为 84 12.3 终止对话 85 13 初始化一个会话 85 13.1 概览 85 13.2 UAC处理 86 13.2.1 创建一个初始化的INVITE 86 13.2.2 处理INVITE应答 89 13.2.2.1 1xx应答 89 13.2.2.2 3xx应答 89 13.2.2.3 4xx,5xx,6xx应答 90 13.2.2.4 2xx 应答 90 13.3 UAS处理 91 13.3.1 处理INVITE 91 13.3.1.1 提示进度 92 13.3.1.2 INVITE请求转发 93 13.3.1.3 INVITE请求的拒绝 93 13.3.1.4 接受INVITE请求 93 14 更改已经存在的会话 94 14.1 UAC行为 95 14.2 UAS行为 96 15 结束一个会话 98 15.1 使用BYE请求终止一个会话 99 15.1.1 UAC行为 99 15.1.2 UAS行为 100 16 proxy行为 100 16.1 概述 100 16.2 有状态的proxy 101 16.3 验证请求 103 16.4 路由信息预处理 105 16.5 确定请求的目的 106 16.6 请求转发 108 16.7 应答的处理 117 16.8 处理定时器C 125 16.9 处理通讯层的错误 126 16.10 CANCEL处理 126 16.11 无状态的proxy 127 16.12 Proxy Route处理的总结 129 16.12.1例子 130 16.12.1.1 基本SIP四边形 130 16.12.1.2 穿越一个严格路由proxy 132 17事务 134 17.1 客户端事务 136 17.1.1 INVITE客户事务 137 17.1.1.1 INVITE事务概述 137 17.1.1.2 正式的描述 138 17.1.1.3 构造ACK请求 142 17.1.2 非INVITE客户端事务 143 17.1.2.2 正式的描述 143 17.1.3 客户端事务匹配应答 145 17.1.4 处理通讯错误 145 17.2 服务端事务 147 17.2.1 INVITE服务端事务 147 17.2.2 非INVITE服务端事务 150 17.2.3 为服务端事务匹配请求。 151 17.2.4 处理通讯错误 154 18 通讯(transport) 154 18.1 客户Clients 155 18.1.1 发送请求 155 18.1.2 接收应答 157 18.2 服务端 158 18.2.1 接收请求 158 18.2.2 发送应答 159 18.3 分块 160 18.4 错误处理 161 19 常见消息部件(Common Message Components) 161 19.1 SIP和SIPS统一资源标记 161 19.1.1 SIP和SIPS部件 162 19.1.2 Character Escaping Requirements(字符转码要求) 166 19.1.3 SIP和SIPS URI例子 168 19.1.4 URI比较 168 19.1.5 从URI中产生请求 171 19.1.6 关联SIP URI和tel URL 173 19.2 Option Tags 175 19.3 Tags 175 20 头域 176 20.1 Accept 178 20.2 Accept-Encoding 181 20.3 Accept-Language 182 20.4 Alert-Info 182 20.5 Allow 183 20.6 Authentication-Info 183 20.7 Authorization 183 20.8 Call-ID 184 20.9 Call-Info 184 20.10 Contact 185 20.11 Content-Disposition 186 20.12 Content-Encoding 187 20.13 Content-Language 188 20.14 Content-Length 188 20.15 Content-Type 189 20.16 Cseq 189 20.17 Date 190 20.18 Error-Info 190 20.19 Expires 191 20.20 From 191 20.21 In-Reply-To 192 20.22 Max-Forwards 193 20.23 Min-Expires 193 20.24 MIME-Version 193 20.25 Organization 194 20.26 Priority 194 20.27 Proxy-Authenticate 195 20.28 Proxy-Authorization 195 20.29 Proxy-Require 196 20.30 Record-Route 196 20.31 Reply-To 196 20.32 Require 197 20.33 Retry-After 197 20.34 Route 198 20.35 Server 198 20.36 Subject 198 20.37 Supported 199 20.38 Timestamp 199 20.39 To 199 20.40 Unsupported 200 20.41 User-Agent 200 20.42 Via 200 20.43 警告 202 20.44 WWW-Authenticate 204 21 应答代码 205 21.1 临时应答1xx 205 21.1.1 100 Trying 205 21.1.2 180 Ringing 205 21.1.3 818 Call is Being Forwarded(呼叫被转发) 205 21.1.4 182 Queued 206 21.1.5 183 会话进度 206 21.2 成功信息2xx 206 21.2.1 200 OK 206 21.3 转发请求3XX 206 21.3.1 300 Multiple Choices 206 21.3.2 301 Moved Permanently 207 21.3.3 302 Moved Temporarily 207 21.3.4 305 Use Proxy 208 21.3.5 380 Alternative Service 208 21.4 请求失败4xx 208 21.4.1 400 Bad Request 208 21.4.2 401 Unauthorized 208 21.4.3 402 Payment Required 209 21.4.4 403 Forbidden 209 21.4.5 404 Not Found 209 21.4.6 405 Method Not Allowed 209 21.4.7 406 Not Acceptable 209 21.4.8 407 Proxy Authentication Required 209 21.4.9 408 Request Timeout 210 21.4.10 410 Gone 210 21.4.11 413请求实体过大。 210 21.4.12 414 Request-URI Too Long 210 21.4.13 415 Unsupported Media Type 211 21.4.14 416 Unsupported URI Scheme 211 21.4.15 Bad Extension 211 21.4.16 421Extension Required 211 21.4.17 423 Interval Too Brief 211 21.4.18 480 Temporarily Unavailable 212 21.4.19 481 Call/Transaction Does Not Exist 212 21.4.20 482 Loop Detected 212 21.4.21 483 Too Many Hops 212 21.4.22 484 Address InComplete 213 21.4.23 485 Ambiguous 213 21.4.24 486 Busy Here 213 21.4.25 487 Request Terminated 214 21.4.26 488 Not Acceptable Here 214 21.4.27 491 Request Pending 214 21.4.28 493 Undecipherable 214 21.5 Server Failure 5xx 214 21.5.1 500 Server Internal Error 215 21.5.2 501 Not Implemented 215 21.5.3 502 Bad Gateway 215 21.5.4 503 Service Unavailable 215 21.5.5 504 Server Time-out 216 21.5.6 505 Version Not Supported 216 21.5.7 Message To Large 216 21.6 Global Failures 6xx 216 21.6.1 600 Busy Everywhere 216 21.6.2 603 Decline 217 21.6.3 604 Does Not Exists Anywhere 217 21.6.4 606 Not Acceptable 217 22 使用HTTP认证 218 22.1 框架 218 22.2 用户到用户的认证。 221 22.3 Proxy到用户的认证 222 22.4 Digest 认证方案 225 23 S/MIME 227 23.1 S/MIME 认证 227 23.2 S/MIME 密钥交换 228 23.3 加密MIME 包体 231 23.4 SIP头隐私和用S/MIME的完整性:SIP地道 233 23.4.1 SIP头的完整性和机密属性 234 23.4.1.1 完整性 234 23.4.1.2 机密性 234 23.4.2 隧道的完整性和身份认证 236 23.4.3 隧道加密 239 24 例子 242 24.1 注册 242 24.2 建立会话 244 25 SIP协议的BNF范式 251 25.1 基本规则 252 26 安全考虑:威胁模式和安全应用建议。 273 26.1 攻击和威胁模式 274 26.1.1 注册服务 Hijacking。 274 26.1.2 模仿一个服务器 275 26.1.3 修改消息包体 276 26.1.4 破坏会话 277 26.2 安全机制 278 26.2.1 通讯和网络层的安全 279 26.2.2 SIPS URI方案 281 26.2.3 HTTP Authentication 282 26.2.4 S/MIME 282 26.3 安全机制的实现 283 26.3.1 对SIP实现者的要求 283 26.3.2 安全解决方案 284 26.3.2.1 注册 284 26.3.2.2 在域之间的请求 286 26.3.2.3 点对点请求 288 26.3.2.4 DoS 防护 289 26.4 限制 290 26.4.1 HTTP Digest 290 26.4.2 S/MIME 291 26.4.3 TLS 292 26.4.4 SIPS URI 293 26.5 Privacy(隐私) 295 27 IANA 认证 295 27.1 Option Tags 296 27.2 Warn-Codes 296 27.3 头域名 297 27.4 方法和应答码 297 27.6 新Content-Disposition 参数注册 299 28 同RFC 2543的改变 299 28.1 主要的功能改变 300 28.2 小功能性的变更 304 29 标准索引 304 30 信息索引: 307 定时器值的表格: 308 感谢书 310 版权声明 313
Introduction xiii CHAPTER 1 Standard Procedures for SMS in GSM Networks 1 1.1 GSM Network Architecture and Principle of the SMS Procedure 1 1.2 Implementation of SMS Services 3 1.2.1 SMS-MO Implementation 3 1.2.2 The SMS-MT Implementation 6 1.2.3 Sending Commands to the SMSC 14 1.2.4 Addressing the Foreign Network HLRs for SMS-MT 15 1.2.5 Summary of the Network Equipment Model for SMS 16 1.3 MAP Dialogue Models at the Application Level 16 1.3.1 Request and CNF (Simple) Dialogue 17 1.3.2 Concatenated SMS Dialogue: More Message to Send 17 1.3.3 Update Location Dialogue 17 1.3.4 Send Routing Information for SM Dialogue 18 1.4 SCCP Addresses: The Tool for Flexible International Roaming 18 1.5 Mobility Procedures 19 1.5.1 Update Location Procedure 20 1.5.2 Making a Telephone Call to a Mobile 22 1.6 GPRS Procedures: The Gc Interface 23 1.7 SMS Billing Records and Methods 23 1.7.1 SMS-MO CDRs 25 1.7.2 SMS-MT CDRs 26 1.8 Load Test of an SMSC 26 1.8.1 SMS-MT Test Configuration 26 1.8.2 Results and Performance Model 26 Exercises 28 References 28 CHAPTER 2 SS7 Network and Protocol Layers 29 2.1 History 29 2.2 Efficient and Secure Worldwide Telecommunications 29 2.3 MTP Protocol (OSI Layers 1–3) 30 2.3.1 MTP Layer 1: Signaling Data Link Level 31 v 2.3.2 MTP Layer 2: Signaling Link Functions 31 2.3.3 MTP Layer 3: Signaling Network Functions 34 2.4 Signaling Connection Control Part 37 2.4.1 SCCP Message Format 38 2.4.2 SCCP Layer Architecture 38 2.4.3 SCCP Routing 39 2.5 Transaction Capability Application Part (TCAP) 42 2.5.1 Main Features of TCAP 43 2.5.2 TCAP Architecture 43 2.5.3 TCAP Operation Invocation Example 44 2.6 User-Level Application Parts: MAP, INAP, CAMEL 45 2.6.1 User Part Mapping onto TCAP: MAP Example 45 2.6.2 Routing Design 48 2.6.3 Service-Oriented Design: Application to an SS7-Based Fault-Tolerant System 50 2.7 SS7 and VoIP Interworking Overview SIGTRAN 51 2.7.1 SCTP 51 2.7.2 Interworking with SS7 52 2.7.3 M3UA Layer 52 2.7.4 M2UA Layer 52 2.7.5 SUA Layer 52 2
Contents Foreword to the First Edition xvii Preface to the Second Edition xix Preface to the First Edition xxi 1 SIP and the Internet 1 1.1 Signaling Protocols 1 1.2 The Internet Engineering Task Force 2 1.3 A Brief History of SIP 3 1.4 Internet Multimedia Protocol Stack 4 1.4.1 Physical Layer 4 1.4.2 Internet Layer 4 1.4.3 Transport Layer 5 1.4.4 Application Layer 8 1.5 Utility Applications 9 1.6 DNS and IP Addresses 10 1.7 URLs and URIs 12 1.8 Multicast 12 1.9 ABNF Representation 13 References 14 2 Introduction to SIP 17 2.1 A Simple Session Establishment Example 17 2.2 SIP Call with Proxy Server 25 2.3 SIP Registration Example 31 2.4 SIP Presence and Instant Message Example 33 2.5 Message Transport 38 2.5.1 UDP Transport 38 2.5.2 TCP Transport 40 2.5.3 TLS Transport 40 2.5.4 SCTP Transport 41 References 42 3 SIP Clients and Servers 43 3.1 SIP User Agents 43 3.2 Presence Agents 44 3.3 Back-to-Back User Agents 45 3.4 SIP Gateways 45 3.5 SIP Servers 47 3.5.1 Proxy Servers 47 3.5.2 Redirect Servers 52 3.5.3 Registration Servers 55 3.6 Acknowledgment of Messages 55 3.7 Reliability 56 3.8 Authentication 57 3.9 S/MIME Encryption 59 3.10 Multicast Support 60 3.11 Firewalls and NAT Interaction 61 3.12 Protocols and Extensions for NAT Traversal 62 3.12.1 STUN Protocol 63 3.12.2 TURN Protocol 65 3.12.3 Other SIP/SDP NAT-Related Extensions 66 References 68 viii SIP: Understanding the Session Initiation Protocol 4 SIP Request Messages 71 4.1 Methods 71 4.1.1 INVITE 72 4.1.2 REGISTER 74 4.1.3 BYE 76 4.1.4 ACK 77 4.1.5 CANCEL 79 4.1.6 OPTIONS 81 4.1.7 REFER 82 4.1.8 SUBSCRIBE 86 4.1.9 NOTIFY 89 4.1.10 MESSAGE 90 4.1.11 INFO 93 4.1.12 PRACK 94 4.1.13 UPDATE 96 4.2 URI and URL Schemes Used by SIP 98 4.2.1 SIP and SIPS URIs 98 4.2.2 Telephone URLs 100 4.2.3 Presence and Instant Messaging URLs 101 4.3 Tags 102 4.4 Message Bodies 102 References 104 5 SIP Response Messages 107 5.1 Informational 108 5.1.1 100 Trying 109 5.1.2 180 Ringing 109 5.1.3 181 Call Is Being Forwarded 109 5.1.4

“相关推荐”对你有帮助么?

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论 1
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值