FIRST LINE 企業級客服系統
🫱 官方網站🔥 最新消息
  • ❤️關於 FIRST LINE
    • 🥰客服中心
    • 📔更新日誌
      • 🐍2025
      • ☎️電話管理系統
      • 🍱Archive
        • 🐲2024
        • 🐰2023
        • 🐯2022
        • 🐮2021
        • 🐭2020
  • 指南與解答
    • 🚀指南
      • 🤖打造專屬聊天機器人
      • 🧠FIRST LINE AI
      • 🏗️管理者系統建置
      • 👋客服人員:訊息服務
      • 📥服務台:解決與紀錄客戶問題
      • 🔃交談分派的運作模式
      • 💬3 種 WhatsApp 帳號種類大解析!
    • 📔名詞解釋
    • ❓系統疑難
      • ⚠️提示或告警訊息
      • 📶網路離線提醒
      • 🌎支援的瀏覽器
      • 🪠清除瀏覽器快取
  • 功能教學
    • 💬管道
      • 💬即時聊天
        • 疑難雜症
        • 客戶身份驗證
        • 安裝範例
          • 嵌入至 LINE 內服務客戶
          • 安裝於 SHOPLINE 內
          • 安裝於 Shopify 內
      • 💬LINE 官方帳號
        • 如何啟用 Messaging API
        • LINE 訊息費用怎麼算
        • LINE Developer 相關
      • 💬Facebook Messenger
        • 疑難雜症
        • 錯誤代碼 #2022
      • 💬Instagram
      • 💬微信公眾號
      • 💬WhatsApp (Cloud API)
        • 疑難雜症
      • 💬WhatsApp (Twilio)
      • 💬Telegram
      • 💬Viber
      • 📮電子信箱
        • 電子郵件分隔文本
        • 電子郵件附件
        • Gmail 串接測試
      • 📱簡訊
        • Twilio
        • 三竹簡訊
      • ☎️電話
        • ❓疑難雜症
        • 👨‍💻調整或分配分機給專員
        • 📕通話時服務紀錄沒有建立
        • ⤴️轉接與三方通話
        • 😃座席狀態
        • ☎️電話 SIP 代碼
        • 📊通話資訊
      • 🏪線上下通路
    • 📈儀錶板
      • 📊服務水平
      • ☎️電話
      • ☎️專員電話即時狀態
      • 😃社群媒體好友數
      • 📈訊息統計
      • 💬交談佇列
    • 😀客戶關係管理
      • 😀客戶
        • 🔃客戶合併
      • 🏢公司
      • ⬇️匯入客戶
      • 匯入自訂表格
      • 🤝服務紀錄
        • 💬交談紀錄
      • 🔖服務結果
      • ✏️服務原因
      • 自訂欄位
      • 資料匯出
      • 電話紀錄
    • 🤖聊天機器人
      • 📒交談腳本
        • ❓疑難雜症
        • 🚀功能詳解
          • 🧠FIRST LINE AI
          • 📃模組腳本
          • 🔜分派權重
          • 📒事件紀錄
          • 📔草稿與發佈
          • 🗂️輪播訊息
          • 🔘按鈕行為
        • 🎬情境範例
          • 串接 ChatGPT
          • 搜尋與回覆知識庫文章
          • 緊急信件轉派
          • 封鎖名單
          • Webhook 整合指南
          • 如何透過 API 溝通
        • 📊統計數字
        • 從即時聊天 URL 添加數據
      • 😀滿意度調查
      • 🧠AI 訓練資源
      • 🕐營業時間
      • 🤖自動回應
        • 關鍵字回應
    • 💡知識庫
      • 幫助中心
        • 擴充自訂義 HTML
      • 聊天機器人
    • 🎟️工單
      • 工單範本
      • 關注工單
      • 透過電子信箱發送
      • 狀態細項
    • 🛍️行銷
      • 🛍️產品目錄
      • 📢分眾訊息
        • 自動化活動
      • 🎡LINE 圖文選單
      • 📃貼文自動回覆
      • 😁對話角色
      • 🎟️優惠卷
      • 🔗追蹤連結
    • 🔌整合
      • 🚗自動化
        • 範例:發送 LINE 訊息
        • 範例:會員同步
        • 範例:發送 Teams 通知
      • ⛓️Webhook 腳本
    • 📃報表
      • ☎️電話
        • 專員通話效率
        • 通話紀錄報表
        • ACD 號碼分析
      • 服務紀錄明細與樞紐
      • 專員服務效率
      • 訊息管道樞紐
    • ⚒️輔助工具
      • 管道整合
      • 信件範本
      • 對話腳本
      • 訊息範本
    • ⚙️系統設定
      • 🏢企業
        • 🏢系統設定
        • 🧑‍🤝‍🧑部門
        • 💰帳務總覽
        • 🔥IP 允許清單
        • 組別
        • 業主
        • 🗺️地址
          • 縣市
          • 行政區域
          • 國家
        • 🔐權限
      • 😀客戶
        • 客戶分派
      • 🤝服務紀錄
        • 服務原因
      • 🎙️員工
        • 服務狀態
        • 更改或忘記密碼
      • 🗄️檔案管理
      • 💪技能
      • 👜職位
      • 💬開場白與話術
    • 🚀其他資料
      • 🔵Fancy 點數
      • 👨‍💻模板語法
      • 💬交談狀態
      • 🔍全域搜尋
      • 👨‍💻交談腳本變數
      • 📄資料欄位類型
      • 🌐IP 與網域清單
      • 💬各管道訊息類型支援度
    • ✊合作夥伴
      • 📞電話疑難雜症
      • 🎛️其他相關設定
  • 開發文件
    • API 說明
      • 請求方式說明
      • 回應物件資料
      • 😀客戶
      • 🔖客戶標籤
      • 🏢公司
      • ⬇️客戶匯入排程
      • ⬇️客戶自訂表格匯入排程
      • 📄自訂欄位主分類
      • 📄自訂欄位
      • 📄自訂表格
      • ☎️電話號碼
      • 🌎國家、縣市及區域
      • 🏠地址
      • 📧電子信箱
      • 🎫工單
      • 💬服務紀錄
      • 😃滿意度調查
      • 🛍️產品
      • 📄訂單
      • 📦訂單品項
    • Advanced
      • 透過 Hash 值取得 Text-Call ID
      • 透過 Text-Call ID 發送訊息
      • 搜尋聯絡人資料(Partner Limit)
      • Push (Partner Limit)
    • 即時聊天 Javascript API
Powered by GitBook
On this page
  1. 功能教學
  2. 管道
  3. 電話

電話 SIP 代碼

SIP responses are the codes used by Session Initiation Protocol for communication. We have put together a list of all the SIP responses known.

代碼狀態

代碼

名稱

描述

100

Trying

Extended search is being performed so a forking proxy must send a 100 Trying response.

180

Ringing

The Destination User Agent has received the INVITE message and is alerting the user of call.

181

Call Is Being Forwarded

Optional, send by Server to indicate a call is being forwarded.

182

Queued

Destination was temporarily unavailable, the server has queued the call until the destination is available.

183

Session Progress

This response may be used to send extra information for a call which is still being set up.

199

Early Dialog Terminated

Send by the User Agent Server to indicate that an early dialogue has been terminated.

200

OK

Shows that the request was successful

202

accepted

Indicates that the request has been accepted for processing, mainly used for referrals.

204

No Notification

Indicates that the request was successful but no response will be received.

300

Multiple Choices

The address resolved to one of several options for the user or client to choose between.

301

Moved Permanently

The original Request URI is no longer valid, the new address is given in the Contact header.

302

Moved Temporarily

The client should try at the address in the Contact field.

305

Use Proxy

The Contact field details a proxy that must be used to access the requested destination.

380

Alternative Service

The call failed, but alternatives are detailed in the message body.

400

Bad Request

The request could not be understood due to malformed syntax.

401

Unauthorized

The request requires user authentication. This response is issued by UASs and registrars.

402

Payment Required

(Reserved for future use).

403

Forbidden

The server understood the request, but is refusing to fulfil it.

404

Not Found

The server has definitive information that the user does not exist at the (User not found).

405

Method Not Allowed

The method specified in the Request-Line is understood, but not allowed.

406

Not Acceptable

The resource is only capable of generating responses with unacceptable content.

407

Proxy Authentication Required

The request requires user authentication.

408

Request Timeout

Couldn’t find the user in time.

409

Conflict

User already registered (deprecated)

410

Gone

The user existed once but is not available here any more.

411

Length Required

The server will not accept the request without a valid content length (deprecated).

412

Conditional Request Failed

The given precondition has not been met.

413

Request Entity Too Large

Request body too large.

414

Request URI Too Long

Server refuses to service the request, the Req-URI is longer than the server can interpret.

415

Unsupported Media Type

Request body is in a non-supported format.

416

Unsupported URI Scheme

Request-URI is unknown to the server.

417

Uknown Resource-Priority

There was a resource-priority option tag, but no Resource-Priority header.

420

Bad Extension

Bad SIP Protocol Extension used, not understood by the server.

421

Extension Required

The server needs a specific extension not listed in the Supported header.

422

Session Interval Too Small

The request contains a Session-Expires header field with a duration below the minimum.

423

Interval Too Brief

Expiration time of the resource is too short.

424

Bad Location Information

The request’s location content was malformed or otherwise unsatisfactory.

428

Use Identity Header

The server policy requires an Identity header, and one has not been provided.

429

Provide Referrer Identity

The server did not receive a valid Referred-By token on the request.

430

Flow Failed

A specific flow to a user agent has failed, although other flows may succeed.

433

Anonymity Disallowed

The request has been rejected because it was anonymous.

436

Bad Identity Info

The request has an Identity-Info header and the URI scheme contained cannot be de-referenced.

437

Unsupported Certificate

The server was unable to validate a certificate for the domain that signed the request.

438

Invalid Identity Header

Server obtained a valid certificate used to sign a request, was unable to verify the signature.

439

First Hop Lacks Outbound Support

The first outbound proxy doesn’t support the “outbound” feature.

440

Max-Breadth Exceeded

If a SIP proxy determined a response context had insufficient Incoming Max-Breadth to carry out a desired parallel fork, and the proxy is unwilling/unable to compensate by forking serially or sending a redirect, that proxy MUST return a 440 response. A client receiving a 440 response can infer that its request did not reach all possible destinations.

469

Bad Info Package

If a SIP UA receives an INFO request associated with an Info Package that the UA has not indicated willingness to receive, the UA MUST send a 469 response, which contains a Recv-Info header field with Info Packages for which UA is willing to receive INFO requests.

470

Consent Needed

The source of the request did not have the permission of the recipient to make such a request.

480

Temporarily Unavailable

Callee currently unavailable.

481

Call/Transaction Does Not Exist

Server received a request that does not match any dialogue or transaction.

482

Loop Detected

Server has detected a loop.

483

Too Many Hops

Max-Forwards header has reached the value ‘0’.

484

Address Incomplete

Request-URI incomplete.

485

Ambiguous

Request-URI is ambiguous.

486

Busy Here

Callee is busy.

487

Request Terminated

Request has terminated by bye or cancel.

488

Not Acceptable Here

Some aspects of the session description of the Request-URI are not acceptable.

489

Bad Event

The server did not understand an event package specified in an Event header field.

491

Request Pending

Server has some pending request from the same dialogue.

493

Undecipherable

UndecipherableRequest contains an encrypted MIME body, which recipient can not decrypt.

494

Security Agreement Required

The server has received a request that requires a negotiated security mechanism.

500

Server Internal Error

The server could not fulfill the request due to some unexpected condition.

501

Not Implemented

The SIP request method is not implemented here.

502

Bad Gateway

The server, received an invalid response from a downstream server while trying to fulfill a request.

503

Service Unavailable

The server is in maintenance or is temporarily overloaded and cannot process the request.

504

Server Time-out

The server tried to access another server while trying to process a request, no timely response.

505

Version Not Supported

The SIP protocol version in the request is not supported by the server.

513

Message Too Large

The request message length is longer than the server can process.

555

Push Notification Service Not Supported

The server does not support the push notification serviced specified in the pn-provider SIP URI parameter.

580

Precondition Failure

The server is unable or unwilling to meet some constraints specified in the offer.

600

Busy Everywhere

All possible destinations are busy.

603

Decline

Destination cannot/doen’t wish to participate in the call, no alternative destinations.

604

Does Not Exist Anywhere

The server has authoritative information that the requested user does not exist anywhere.

606

Not Acceptable

The user’s agent was contacted successfully but some aspects of the session description were not acceptable.

607

Unwanted

The called party did not want his call from the calling party. Future attempts from the calling party are likely to be similarly rejected.

Previous座席狀態Next通話資訊

Last updated 8 months ago

💬
☎️
☎️