SipJS和Freeswtch：无法接听电话

正在尝试使用基于sipJS的SipPhone呼叫 我在一端使用linphone，在另一端使用sipjs，lin phone可以呼叫sipjs phone作为铃声，但我无法接听电话 这是我的日志，未经授权的UA似乎是个问题

日志：

SIP/2.0 401 Unauthorized
Via: SIP/2.0/WS hntgukqjg2hc.invalid;branch=z9hG4bK8046067;received=100.74.156.116;rport=49654
From: "1000" <sip:1000@100.74.156.116>;tag=ab7a6dqv0k
To: "1000" <sip:1000@100.74.156.116>;tag=rS92SD9Zt6yDg
Call-ID: 52aucsstdsah4mf5499e6m
CSeq: 81 REGISTER
**User-Agent: FreeSWITCH-mod_sofia/1.5.15b~64bit**
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER, REFER, NOTIFY, PUBLISH, SUBSCRIBE
Supported: timer, path, replaces
WWW-Authenticate: Digest realm="100.74.156.116", nonce="f92c8e20-1906-4a61-b341-f6fd43e1be87", algorithm=MD5, qop="auth"
Content-Length: 0



sip.transport | sending WebSocket message:

REGISTER sip:100.74.156.116 SIP/2.0
Via: SIP/2.0/WS hntgukqjg2hc.invalid;branch=z9hG4bK521909
Max-Forwards: 70
To: "1000" <sip:1000@100.74.156.116>
From: "1000" <sip:1000@100.74.156.116>;tag=ab7a6dqv0k
Call-ID: 52aucsstdsah4mf5499e6m
CSeq: 82 REGISTER
Authorization: Digest algorithm=MD5, username="1000", realm="100.74.156.116", nonce="f92c8e20-1906-4a61-b341-f6fd43e1be87", uri="sip:100.74.156.116", response="357518a5593937845bf92f2e961f3b4c", qop=auth, cnonce="otm5sa1unt17", nc=00000001
Contact: <sip:c0e2i9qn@hntgukqjg2hc.invalid;transport=ws>;reg-id=1;+sip.instance="<urn:uuid:e7733a3b-3480-48e6-a065-5af261036403>";expires=130
Allow: ACK,CANCEL,INVITE,MESSAGE,BYE,OPTIONS,INFO,NOTIFY
Supported: path, gruu, outbound
User-Agent: SIP.js/0.7.3
Content-Length: 0



sip.js:2884 Fri Apr 15 2016 16:56:42 GMT+0530 (India Standard Time) | sip.transport | received WebSocket text message:

SIP/2.0 200 OK
Via: SIP/2.0/WS hntgukqjg2hc.invalid;branch=z9hG4bK521909;received=100.74.156.116;rport=49654
From: "1000" <sip:1000@100.74.156.116>;tag=ab7a6dqv0k
To: "1000" <sip:1000@100.74.156.116>;tag=S22UU8S3QFN0B
Call-ID: 52aucsstdsah4mf5499e6m
CSeq: 82 REGISTER
Contact: <sip:c0e2i9qn@hntgukqjg2hc.invalid;transport=ws>;expires=130
Date: Fri, 15 Apr 2016 11:26:42 GMT
User-Agent: FreeSWITCH-mod_sofia/1.5.15b~64bit
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER, REFER, NOTIFY, PUBLISH, SUBSCRIBE
Supported: timer, path, replaces
Content-Length: 0

 sip.transport | received WebSocket text message:

NOTIFY sip:c0e2i9qn@hntgukqjg2hc.invalid;transport=ws SIP/2.0
Via: SIP/2.0/WS 100.74.156.116:5066;rport;branch=z9hG4bKmmBevgH597eDF
Route: <sip:c0e2i9qn@100.74.156.116:49654>;transport=ws
Max-Forwards: 70
From: <sip:1000@100.74.156.116>;tag=tBvmX3a7mrBKQ
To: <sip:1000@100.74.156.116>
Call-ID: c51139ce-7d9f-1234-0faa-37dc5feb612c
CSeq: 90023737 NOTIFY
Contact: <sip:mod_sofia@100.74.156.116:5060>
User-Agent: FreeSWITCH-mod_sofia/1.5.15b~64bit
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER, REFER, NOTIFY, PUBLISH, SUBSCRIBE
Supported: timer, path, replaces
Event: message-summary
Allow-Events: talk, hold, conference, presence, as-feature-event, dialog, line-seize, call-info, sla, include-session-description, presence.winfo, message-summary, refer
Subscription-State: terminated;reason=noresource
Content-Type: application/simple-message-summary
Content-Length: 66

Messages-Waiting: no
Message-Account: sip:1000@100.74.156.116


sip.transport | sending WebSocket message:

SIP/2.0 405 Method Not Allowed
Via: SIP/2.0/WS 100.74.156.116:5066;rport;branch=z9hG4bKmmBevgH597eDF
To: <sip:1000@100.74.156.116>;tag=ao6rh9rc8h
From: <sip:1000@100.74.156.116>;tag=tBvmX3a7mrBKQ
Call-ID: c51139ce-7d9f-1234-0faa-37dc5feb612c
CSeq: 90023737 NOTIFY
Supported: outbound
User-Agent: SIP.js/0.7.3
Content-Length: 0



REGISTER sip:100.74.156.116 SIP/2.0
Via: SIP/2.0/WS hntgukqjg2hc.invalid;branch=z9hG4bK9236948
Max-Forwards: 70
To: "1000" <sip:1000@100.74.156.116>
From: "1000" <sip:1000@100.74.156.116>;tag=ab7a6dqv0k
Call-ID: 52aucsstdsah4mf5499e6m
CSeq: 83 REGISTER
Authorization: Digest algorithm=MD5, username="1000", realm="100.74.156.116", nonce="f92c8e20-1906-4a61-b341-f6fd43e1be87", uri="sip:100.74.156.116", response="357518a5593937845bf92f2e961f3b4c", qop=auth, cnonce="otm5sa1unt17", nc=00000001
Contact: <sip:c0e2i9qn@hntgukqjg2hc.invalid;transport=ws>;reg-id=1;+sip.instance="<urn:uuid:e7733a3b-3480-48e6-a065-5af261036403>";expires=130
Allow: ACK,CANCEL,INVITE,MESSAGE,BYE,OPTIONS,INFO,NOTIFY
Supported: path, gruu, outbound
User-Agent: SIP.js/0.7.3
Content-Length: 0

SIP/2.0 401未经授权
Via:SIP/2.0/WS-hntgukqjg2hc.invalid；分支=z9hG4bK8046067；已接收=100.74.156.116；rport=49654
从：“1000”；标签=ab7a6dqv0k
至：“1000”；标签=rS92SD9Zt6yDg
电话号码：52AUCSTDSAH4MF5499E6M
CSeq:81寄存器
**用户代理：FreeSWITCH-mod_sofia/1.5.15b~64位**
允许：邀请、确认、再见、取消、选项、消息、信息、更新、注册、引用、通知、发布、订阅
支持：计时器、路径、替换
WWW-Authenticate:Digest realm=“100.74.156.116”，nonce=“f92c8e20-1906-4a61-b341-f6fd43e1be87”，algorithm=MD5，qop=“auth”
内容长度：0
sip.transport |发送WebSocket消息：
注册sip:100.74.156.116 sip/2.0
Via:SIP/2.0/WS-hntgukqjg2hc.invalid；分支=Z9HG4BK52199
最大前锋：70
致：“1000”
从：“1000”；标签=ab7a6dqv0k
电话号码：52AUCSTDSAH4MF5499E6M
CSeq:82寄存器
授权：Digest algorithm=MD5，username=“1000”，realm=“100.74.156.116”，nonce=“f92c8e20-1906-4a61-b341-f6fd43e1be87”，uri=“sip:100.74.156.116”，response=“357518a5593937845bf92f2e961f3b4c”，qop=auth，cnonce=“otm5sa1unt17”，nc=0000000 1
联系人：；注册id=1+sip.instance=“”；过期=130
允许：确认、取消、邀请、消息、再见、选项、信息、通知
支持：路径、gruu、出站
用户代理：SIP.js/0.7.3
内容长度：0
sip.js:2884 Fri 2016年4月15日16:56:42 GMT+0530（印度标准时间）| sip.transport |收到WebSocket短信：
SIP/2.0 200正常
Via:SIP/2.0/WS-hntgukqjg2hc.invalid；分支=Z9HG4BK52199；已接收=100.74.156.116；rport=49654
从：“1000”；标签=ab7a6dqv0k
至：“1000”；标签=S22UU8S3QFN0B
电话号码：52AUCSTDSAH4MF5499E6M
CSeq:82寄存器
联系人：；过期=130
日期：2016年4月15日星期五11:26:42 GMT
用户代理：FreeSWITCH-mod_sofia/1.5.15b~64位
允许：邀请、确认、再见、取消、选项、消息、信息、更新、注册、引用、通知、发布、订阅
支持：计时器、路径、替换
内容长度：0
sip.transport |收到WebSocket文本消息：
通知sip：c0e2i9qn@hntgukqjg2hc.invalid;传输=ws-SIP/2.0
Via:SIP/2.0/WS 100.74.156.116:5066；rport；分支=Z9HG4BKMMMBEVGH597EDF
路线：；传输=ws
最大前锋：70
发件人：；标签=tBvmX3a7mrBKQ
致：
呼叫ID:c51139ce-7d9f-1234-0faa-37dc5feb612c
CSeq:90023737通知
联系人：
用户代理：FreeSWITCH-mod_sofia/1.5.15b~64位
允许：邀请、确认、再见、取消、选项、消息、信息、更新、注册、引用、通知、发布、订阅
支持：计时器、路径、替换
事件：消息摘要
允许事件：通话、等待、会议、状态、as功能事件、对话框、线路占用、呼叫信息、sla、包括会话描述、状态。winfo、消息摘要、参考
订阅状态：已终止；原因=无来源
内容类型：应用程序/简单消息摘要
内容长度：66
等待消息：否
消息帐户：sip:1000@100.74.156.116
sip.transport |发送WebSocket消息：
不允许使用SIP/2.0 405方法
Via:SIP/2.0/WS 100.74.156.116:5066；rport；分支=Z9HG4BKMMMBEVGH597EDF
致：；标签=ao6rh9rc8h
发件人：；标签=tBvmX3a7mrBKQ
呼叫ID:c51139ce-7d9f-1234-0faa-37dc5feb612c
CSeq:90023737通知
支持：出站
用户代理：SIP.js/0.7.3
内容长度：0
注册sip:100.74.156.116 sip/2.0
Via:SIP/2.0/WS-hntgukqjg2hc.invalid；分支=z9hG4bK9236948
最大前锋：70
致：“1000”
从：“1000”；标签=ab7a6dqv0k
电话号码：52AUCSTDSAH4MF5499E6M
CSeq:83寄存器
授权：Digest algorithm=MD5，username=“1000”，realm=“100.74.156.116”，nonce=“f92c8e20-1906-4a61-b341-f6fd43e1be87”，uri=“sip:100.74.156.116”，response=“357518a5593937845bf92f2e961f3b4c”，qop=auth，cnonce=“otm5sa1unt17”，nc=0000000 1
联系人：；注册id=1+sip.instance=“”；过期=130
允许：确认、取消、邀请、消息、再见、选项、信息、通知
支持：路径、gruu、出站
用户代理：SIP.js/0.7.3
内容长度：0

以上只是注册日志，它的注册状态为200 OK。

它的工作状态为：），但我还有另一个问题，调用正常，但“call on hold”不正常，调用立即断开，没有任何错误日志。（sipjs）是否在sipjs中调用.hold（）函数？您在呼叫断开时得到的SIP响应是什么？