mss可以sip trunk方式直接连接mss吗？

[sipvision]

在同一个网段，想做一个mss测试。
在2台pc上各装一个mss，各装一个xlite
minisipserver1 192.168.0.1
xlite1 100 已在minisipserver1上注册成功

minisipserver2 192.168.0.2
xlite2 200 已在minisipserver2上注册成功

设置了对端服务器，设置了被叫号码规则，设置了外线（注册到对端SIP方式），总是不通。
看到的log如下：
02/10/10 17:55:07 | sip_trans_fsm(3742006A)::received event(ESIP_TRANS_EVT_RETRANS_TIME_OUT) at state (ESIP_TRANS_O_COMPLETED)
02/10/10 17:55:07 | sip_trans_fsm(3742006A)::_procSendResp
02/10/10 17:55:07 | sip_trans_fsm(3742006A)::_sendSipResp
02/10/10 17:55:07 | MSS sends following SIP message to peer GW or UA(192.168.0.1:2594):
02/10/10 17:55:07 | SIP/2.0 480 Temporarily Unavailable
Via: SIP/2.0/UDP 192.168.0.1:2594;branch=z9hG4bK-dd83d41-4b728260-3e1a950
From: "100"<sip:100@192.168.0.1:2594>;tag=12a2549a
To: "200"<sip:200@192.168.0.2>;tag=aca4158
CSeq: 1 INVITE
Call-ID: 244471461fe506e33ca15e87-35944592@192.168.0.1
Allow: REGISTER, INVITE, OPTIONS, ACK, CANCEL, BYE, REFER, SUBSCRIBE, NOTIFY, MESSAGE
User-Agent: miniSipServer V2.8.12 (100) Nov 19 2009
Contact: <sip:200@192.168.0.2>
Reason: Q.850; cause=41; text="Temporary failure"
Content-Length: 0

怎样通过sip trunk 让xlite1可以拨打xlite2？

[admin]

Hi,

It is no problem to use sip trunks to establish connection. You need configure following information:

Let's give a example in your MSS1 (192.168.0.1):

(1) configure sip server. Please click menu "data->peer servers" and add a record "id=1; description= to 192.168.1.0.2; server address=192.168.1.0.2; server port=5060";
(2) configure dial plan. Please click menu "dial plan -> caller number analysis" and add a record "dial plan=default; called number prefix=2; route type=SIP trunk; peer server id=1;

Then, in the MSS1, when user dial 2xx, the call will be routed to MSS2(192.168.0.2) directly.

You can configure MSS2 in the same way. Please attention, in the "called number analysis" table of MSS2, the called number prefix "1" should be modified to "sip trunk" route type.

[sipvision]

我按admin所说的做了配置，还是没通，pc是win xp sp2 eyebeam是1.5 中文版

log如下:
02/10/10 23:32:39 | Allocate message pool.
02/10/10 23:32:39 | Get system configuration table ...
02/10/10 23:32:39 | Get local users table ...
02/10/10 23:32:39 | Get external lines informations table ...
02/10/10 23:32:39 | Get SIP peer server table ...
02/10/10 23:32:39 | Get called analysis table ...
02/10/10 23:32:39 | Load announcement files ...
02/10/10 23:32:39 | Create call process task ...
02/10/10 23:32:39 | Create SCP deamon task ...
02/10/10 23:32:39 | Create SCP task ...
02/10/10 23:32:39 | Create STUN task ...
02/10/10 23:32:39 | Create MSS trunk task ...
02/10/10 23:32:39 | Create special resource task ...
02/10/10 23:32:39 | Create SIP task ...
02/10/10 23:32:39 | Create SIP transaction factory ...
02/10/10 23:32:39 | Create SIP register factory ...
02/10/10 23:32:39 | Create SIP UA factory ...
02/10/10 23:32:39 | Create SIP SUB factory ...
02/10/10 23:32:39 | SIP transaction factory running!
02/10/10 23:32:39 | SIP register factory running!
02/10/10 23:32:39 | SIP UA factory running!
02/10/10 23:32:39 | SIP SUB factory running!
02/10/10 23:32:39 | Create ANN channels
02/10/10 23:32:39 | Call process task running!
02/10/10 23:32:39 | SCP deamon task running!
02/10/10 23:32:39 | SCP bind callback service socket 192.168.0.1:5080 ...
02/10/10 23:32:39 | SCP task running!
02/10/10 23:32:39 | STUN bind socket 192.168.0.1:3478 ...
02/10/10 23:32:39 | STUN bind socket 192.168.0.1:3479 ...
02/10/10 23:32:39 | STUN task running!
02/10/10 23:32:39 | MSS trunk bind signal socket 192.168.0.1:6060 ...
02/10/10 23:32:39 | MSS trunk task running!
02/10/10 23:32:39 | MG task running!
02/10/10 23:32:39 | SIP bind socket 192.168.0.1:5060 ...
02/10/10 23:32:39 | SIP task running!
02/10/10 23:32:39 | Load Python scripts ...
02/10/10 23:32:39 | Application run!
02/10/10 23:32:40 | Checking version online ...
02/10/10 23:32:40 | Fail to get version information.
02/10/10 23:33:15 | MSS receives SIP message:
INVITE sip:200@192.168.0.1 SIP/2.0
Via: SIP/2.0/UDP 127.0.0.1:19946;branch=z9hG4bK-d87543-ca6cab6b7261b91a-1--d87543-;rport
Max-Forwards: 70
Contact: <sip:100@127.0.0.1:19946>
To: "200"<sip:200@192.168.0.1>
From: "100"<sip:100@192.168.0.1>;tag=73528e7c
Call-ID: MzY0NDU1MjEyNDc4ODVlZGZmMzA4MDgzNDJiYTZkZjE.
CSeq: 1 INVITE
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO
Content-Type: application/sdp
User-Agent: eyeBeam release 1011d stamp 40820
Content-Length: 610

v=0
o=- 2 2 IN IP4 192.168.0.1
s=CounterPath eyeBeam 1.5
c=IN IP4 192.168.0.1
t=0 0
m=audio 24574 RTP/AVP 0 8 18 101
a=alt:1 1 : 8ZCRlaKL btzEV5jj 192.168.0.1 24574
a=fmtp:18 annexb=no
a=fmtp:101 0-15
a=rtpmap:18 G729/8000
a=rtpmap:101 telephone-event/8000
a=sendrecv
a=x-rtp-session-id:B5B4A3771A1E43C2B29AEC69555FED0A
m=video 35956 RTP/AVP 115 34
a=alt:1 1 : Jimo3VF9 DSz+62i5 192.168.0.1 35956
a=fmtp:115 QCIF=2 CIF=3 I=1 J=1 K=1 MaxBR=1048502/10/10 23:33:15 | MSS sends following SIP message to peer GW or UA

(192.168.0.1:19946):
02/10/10 23:33:15 | SIP/2.0 407 Proxy Authentication Required
Via: SIP/2.0/UDP 127.0.0.1:19946;branch=z9hG4bK-d87543-ca6cab6b7261b91a-1--d87543-
From: "100"<sip:100@192.168.0.1>;tag=73528e7c
To: "200"<sip:200@192.168.0.1>;tag=7a0f7ee5
CSeq: 1 INVITE
Call-ID: MzY0NDU1MjEyNDc4ODVlZGZmMzA4MDgzNDJiYTZkZjE.
Allow: REGISTER, INVITE, OPTIONS, ACK, CANCEL, BYE, REFER, SUBSCRIBE, NOTIFY, MESSAGE
User-Agent: miniSipServer V2.8.12 (100) Nov 19 2009
Proxy-Authenticate: Digest realm="192.168.0.1",algorithm=MD5,nonce="7db55e69414125d05be9249651e73f08",stale=FALSE
Content-Length: 0


02/10/10 23:33:15 | MSS receives SIP message:
ACK sip:200@192.168.0.1 SIP/2.0
Via: SIP/2.0/UDP 127.0.0.1:19946;branch=z9hG4bK-d87543-ca6cab6b7261b91a-1--d87543-;rport
To: "200"<sip:200@192.168.0.1>;tag=7a0f7ee5
From: "100"<sip:100@192.168.0.1>;tag=73528e7c
Call-ID: MzY0NDU1MjEyNDc4ODVlZGZmMzA4MDgzNDJiYTZkZjE.
CSeq: 1 ACK
Content-Length: 0


02/10/10 23:33:15 | MSS receives SIP message:
INVITE sip:200@192.168.0.1 SIP/2.0
Via: SIP/2.0/UDP 127.0.0.1:19946;branch=z9hG4bK-d87543-d245421566086d07-1--d87543-;rport
Max-Forwards: 70
Contact: <sip:100@127.0.0.1:19946>
To: "200"<sip:200@192.168.0.1>
From: "100"<sip:100@192.168.0.1>;tag=73528e7c
Call-ID: MzY0NDU1MjEyNDc4ODVlZGZmMzA4MDgzNDJiYTZkZjE.
CSeq: 2 INVITE
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO
Content-Type: application/sdp
Proxy-Authorization: Digest

username="100",realm="192.168.0.1",nonce="7db55e69414125d05be9249651e73f08",uri="sip:200@192.168.0.1",response="ace23c107c733

0eb6b876bed1b0e3c60",algorithm=MD5
User-Agent: eyeBeam release 1011d stamp 40820
Content-Length: 610

v=0
o=- 2 2 IN IP4 192.168.0.1
s=CounterPath eyeBeam 1.5
c=IN IP4 192.168.0.1
t=0 0
m=audio 24574 RTP/AVP 0 8 18 101
a=alt:1 1 : 8ZCRlaKL btzEV5jj 192.168.0.1 24574
a=fmtp:18 annexb=no
a=fmtp:101 0-15
a=rtpmap:18 G729/8000
a=rtpmap:101 telephone-event/8000
a=s
02/10/10 23:33:15 | sip_trans_fsm(166D0003)::received event(ESIP_TRANS_EVT_IF_INVITE) at state (ESIP_TRANS_STATE_IDLE)
02/10/10 23:33:15 | sip_trans_fsm(166D0003)::change state: ESIP_TRANS_STATE_IDLE-->ESIP_TRANS_O_PROCEEDING
02/10/10 23:33:15 | sip_ua_fsm(5A990003)::received event(UA_EVT_T_U_INVITE) at state (UAS_IDLE)
02/10/10 23:33:15 | sip_ua_fsm(5A990003)::INVITE from local user.
02/10/10 23:33:16 | mg_fsm(1BCE0002):: received event(ESRF_EVT_BIND_REQ_MSG) at state (ESRF_IDLE)
02/10/10 23:33:16 | sip_ua_fsm(5A990003)::change state: UAS_IDLE-->UAS_O_WAIT_BIND_RESP
02/10/10 23:33:16 | mg_fsm(1BCE0002)::_procBindReq
02/10/10 23:33:16 | sip_trans_fsm(166D0003)::received event(ESIP_TRANS_EVT_UT_RESP_MSG) at state (ESIP_TRANS_O_PROCEEDING)
02/10/10 23:33:16 | mg_fsm(1BCE0002):: change state: ESRF_IDLE-->ESRF_ONE_PARTY_BINDED
02/10/10 23:33:16 | sip_trans_fsm(166D0003)::_procUTResp
02/10/10 23:33:16 | sip_trans_fsm(166D0003)::received event(ESIP_TRANS_EVT_UT_1XX_RESP) at state (ESIP_TRANS_O_PROCEEDING)
02/10/10 23:33:16 | sip_trans_fsm(166D0003)::_procSendResp
02/10/10 23:33:16 | sip_trans_fsm(166D0003)::_sendSipResp
02/10/10 23:33:16 | MSS receives SIP message:
INVITE sip:200@192.168.0.1 SIP/2.0
Via: SIP/2.0/UDP 127.0.0.1:19946;branch=z9hG4bK-d87543-d245421566086d07-1--d87543-;rport
Max-Forwards: 70
Contact: <sip:100@127.0.0.1:19946>
To: "200"<sip:200@192.168.0.1>
From: "100"<sip:100@192.168.0.1>;tag=73528e7c
Call-ID: MzY0NDU1MjEyNDc4ODVlZGZmMzA4MDgzNDJiYTZkZjE.
CSeq: 2 INVITE
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO
Content-Type: application/sdp
Proxy-Authorization: Digest

username="100",realm="192.168.0.1",nonce="7db55e69414125d05be9249651e73f08",uri="sip:200@192.168.0.1",response="ace23c107c733

0eb6b876bed1b0e3c60",algorithm=MD5
User-Agent: eyeBeam release 1011d stamp 40820
Content-Length: 610

v=0
o=- 2 2 IN IP4 192.168.0.1
s=CounterPath eyeBeam 1.5
c=IN IP4 192.168.0.1
t=0 0
m=audio 24574 RTP/AVP 0 8 18 101
a=alt:1 1 : 8ZCRlaKL btzEV5jj 192.168.0.1 24574
a=fmtp:18 annexb=no
a=fmtp:101 0-15
a=rtpmap:18 G729/8000
a=rtpmap:101 telephone-event/8000
a=s
02/10/10 23:33:16 | MSS sends following SIP message to peer GW or UA(192.168.0.1:19946):
02/10/10 23:33:16 | SIP/2.0 100 Trying
Via: SIP/2.0/UDP 127.0.0.1:19946;branch=z9hG4bK-d87543-d245421566086d07-1--d87543-
From: "100"<sip:100@192.168.0.1>;tag=73528e7c
To: "200"<sip:200@192.168.0.1>;tag=7de801e1
CSeq: 2 INVITE
Call-ID: MzY0NDU1MjEyNDc4ODVlZGZmMzA4MDgzNDJiYTZkZjE.
Allow: REGISTER, INVITE, OPTIONS, ACK, CANCEL, BYE, REFER, SUBSCRIBE, NOTIFY, MESSAGE
User-Agent: miniSipServer V2.8.12 (100) Nov 19 2009
Contact: <sip:200@192.168.0.1>
Content-Length: 0


02/10/10 23:33:16 | sip_ua_fsm(5A990003)::received event(UA_EVT_SRF_BIND_RESP) at state (UAS_O_WAIT_BIND_RESP)
02/10/10 23:33:16 | sip_ua_fsm(5A990003)::_procSendPBSetup
02/10/10 23:33:16 | sip_ua_fsm(5A990003):: -> cCallerSrfInfo= srf_id:466485250, leg_idx=0
02/10/10 23:33:16 | sip_ua_fsm(5A990003)::change state: UAS_O_WAIT_BIND_RESP-->UAS_O_WAIT_SETUP_ACK
02/10/10 23:33:16 | cc_fsm(232D0003)::received event(EVT_CALLPROC_P_B_SETUP) at state (CSA_IDLE)
02/10/10 23:33:16 | cc_fsm(232D0003)::_procOSetup
02/10/10 23:33:16 | cc_fsm(232D0003)::_savePBSetupInfo
02/10/10 23:33:16 | cc_fsm(232D0003):: --> caller:100, routeNbr:200
02/10/10 23:33:16 | cc_fsm(232D0003)::change state: CSA_IDLE-->CSA_DP_OA
02/10/10 23:33:16 | sip_ua_fsm(5A990003)::received event(UA_EVT_B_P_SETUP_ACK) at state (UAS_O_WAIT_SETUP_ACK)
02/10/10 23:33:16 | cc_fsm(232D0003)::received event(EVT_CALLPROC_DP_REPORT) at state (CSA_DP_OA)
02/10/10 23:33:16 | sip_ua_fsm(5A990003)::change state: UAS_O_WAIT_SETUP_ACK-->UAS_O_WAIT_ALERT
02/10/10 23:33:16 | cc_fsm(232D0003)::received event(EVT_CALLPROC_PIC_RESUME) at state (CSA_DP_OA)
02/10/10 23:33:16 | cc_fsm(232D0003)::change state: CSA_DP_OA-->CSA_DP_CI
02/10/10 23:33:16 | cc_fsm(232D0003)::received event(EVT_CALLPROC_DP_REPORT) at state (CSA_DP_CI)
02/10/10 23:33:17 | cc_fsm(232D0003)::received event(EVT_CALLPROC_PIC_RESUME) at state (CSA_DP_CI)
02/10/10 23:33:17 | cc_fsm(232D0003)::result of analyisis information: route_type=2
02/10/10 23:33:17 | cc_fsm(232D0003)::change state: CSA_DP_CI-->CSA_DP_AI
02/10/10 23:33:17 | cc_fsm(232D0003)::received event(EVT_CALLPROC_DP_REPORT) at state (CSA_DP_AI)
02/10/10 23:33:17 | cc_fsm(232D0003)::received event(EVT_CALLPROC_PIC_RESUME) at state (CSA_DP_AI)
02/10/10 23:33:17 | cc_fsm(232D0003)::change state: CSA_DP_AI-->CSA_AUTH_CALL
02/10/10 23:33:17 | cc_fsm(232D0003)::received event(EVT_CALLPROC_O_FIND_CALL) at state (CSA_AUTH_CALL)
02/10/10 23:33:17 | cc_fsm(232D0003)::change state: CSA_AUTH_CALL-->CSA_O_WAIT_SETUP_ACK
02/10/10 23:33:17 | cc_fsm(483D0004)::received event(EVT_CALLPROC_O_T_SETUP) at state (CSA_IDLE)
02/10/10 23:33:17 | cc_fsm(483D0004)::_procTPreSetup
02/10/10 23:33:17 | cc_fsm(483D0004)::received event(EVT_CALLPROC_O_T_SETUP_CALL) at state (CSA_IDLE)
02/10/10 23:33:17 | cc_fsm(483D0004)::_procTSetup
02/10/10 23:33:17 | cc_fsm(483D0004)::_procTAnaFollowMe
02/10/10 23:33:17 | cc_fsm(483D0004):: no need to invoke follow me procedure.
02/10/10 23:33:17 | sip_ua_fsm(5D130004)::received event(UA_EVT_B_P_SETUP) at state (UAS_IDLE)
02/10/10 23:33:17 | cc_fsm(483D0004)::change state: CSA_IDLE-->CSA_T_WAIT_SETUP_ACK
02/10/10 23:33:17 | sip_ua_fsm(5D130004)::_procTBPSetup
02/10/10 23:33:17 | cc_fsm(232D0003)::received event(EVT_CALLPROC_T_O_SETUP_ACK) at state (CSA_O_WAIT_SETUP_ACK)
02/10/10 23:33:17 | mg_fsm(1BCE0002):: received event(ESRF_EVT_BIND_REQ_MSG) at state (ESRF_ONE_PARTY_BINDED)
02/10/10 23:33:18 | cc_fsm(232D0003)::change state: CSA_O_WAIT_SETUP_ACK-->CSA_O_WAIT_ALERT
02/10/10 23:33:18 | mg_fsm(1BCE0002)::_procBindReq
02/10/10 23:33:18 | sip_ua_fsm(5D130004)::change state: UAS_IDLE-->UAS_T_WAIT_BIND_RESP
02/10/10 23:33:18 | cc_fsm(483D0004)::received event(EVT_CALLPROC_P_B_SETUP_ACK) at state (CSA_T_WAIT_SETUP_ACK)
02/10/10 23:33:18 | mg_fsm(1BCE0002):: change state: ESRF_ONE_PARTY_BINDED-->ESRF_TWO_PARTIES_BINDED
02/10/10 23:33:18 | cc_fsm(483D0004)::change state: CSA_T_WAIT_SETUP_ACK-->CSA_T_WAIT_ALERT
02/10/10 23:33:18 | sip_ua_fsm(5D130004)::received event(UA_EVT_SRF_BIND_RESP) at state (UAS_T_WAIT_BIND_RESP)
02/10/10 23:33:18 | sip_ua_fsm(5D130004)::_procTSrfBindResp
02/10/10 23:33:18 | sip_ua_fsm(5D130004):: -> calledSrfInfo= nSrfId:466485250, nLegidx:1
02/10/10 23:33:18 | sip_ua_fsm(5D130004)::change state: UAS_T_WAIT_BIND_RESP-->UAS_T_WAIT_TRANS_ACK
02/10/10 23:33:18 | sip_trans_fsm(4EB40004)::received event(ESIP_TRANS_EVT_UT_INVITE_MSG) at state (ESIP_TRANS_STATE_IDLE)
02/10/10 23:33:18 | MSS sends following SIP message to peer GW or UA(192.168.0.2:5060):
02/10/10 23:33:18 | INVITE sip:200@192.168.0.2 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.1:5060;branch=z9hG4bK-2b590ed3-4b72d1be-4c89d90
To: "200"<sip:200@192.168.0.2>
From: "100"<sip:100@192.168.0.1>;tag=cd27d64
Contact: <sip:100@192.168.0.1>
Max-Forwards: 70
Call-ID: 129c2944136f4fec79882280-36809920@192.168.0.1
Allow: REGISTER, INVITE, OPTIONS, ACK, CANCEL, BYE, REFER, SUBSCRIBE, NOTIFY, MESSAGE
User-Agent: miniSipServer V2.8.12 (100) Nov 19 2009
CSeq: 1 INVITE
Content-Type: application/sdp
Content-Length: 610

v=0
o=- 2 2 IN IP4 192.168.0.1
s=CounterPath eyeBeam 1.5
c=IN IP4 192.168.0.1
t=0 0
m=audio 24574 RTP/AVP 0 8 18 101
a=alt:1 1 : 8ZCRlaKL btzEV5jj 192.168.0.1 24574
a=fmtp:18 annexb=no
a=fmtp:101 0-15
a=rtpmap:18 G729/8000
a=rtpmap:101 telephone-event/8000
a=sendrecv
a=x-rtp-session-id:B5B4A3771A1E43C2B29AEC69555FED0A
m=video 35956 RTP/AVP 115 34
a=alt:1 1 : Jimo3VF9 DSz+62i5 192.168.0.1 35956
a=fmtp:115 QCIF=2 CIF=3 I=1 J=1 K=1 MaxBR=10485
a=fmtp:34 QCIF=2 MaxBR=10485
a=rtpm
02/10/10 23:33:18 | sip_trans_fsm(4EB40004)::change state: ESIP_TRANS_STATE_IDLE-->ESIP_TRANS_T_CALLING
02/10/10 23:33:18 | MSS receives SIP message:
02/10/10 23:33:18 | sip_ua_fsm(5D130004)::received event(UA_EVT_T_U_INVITE_ACK) at state (UAS_T_WAIT_TRANS_ACK)
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.0.1:5060;branch=z9hG4bK-2b590ed3-4b72d1be-4c89d90
From: "100"<sip:100@192.168.0.1>;tag=cd27d64
To: "200"<sip:200@192.168.0.2>;tag=bc50ac
CSeq: 1 INVITE
Call-ID: 129c2944136f4fec79882280-36809920@192.168.0.1
Allow: REGISTER, INVITE, OPTIONS, ACK, CANCEL, BYE, REFER, SUBSCRIBE, NOTIFY, MESSAGE
User-Agent: miniSipServer V2.8.12 (100) Nov 19 2009
Contact: <sip:200@192.168.0.2>
Content-Length: 0


02/10/10 23:33:18 | MSS receives SIP message:
SIP/2.0 480 Temporarily Unavailable
Via: SIP/2.0/UDP 192.168.0.1:5060;branch=z9hG4bK-2b590ed3-4b72d1be-4c89d90
From: "100"<sip:100@192.168.0.1>;tag=cd27d64
To: "200"<sip:200@192.168.0.2>;tag=bc50ac
CSeq: 1 INVITE
Call-ID: 129c2944136f4fec79882280-36809920@192.168.0.1
Allow: REGISTER, INVITE, OPTIONS, ACK, CANCEL, BYE, REFER, SUBSCRIBE, NOTIFY, MESSAGE
User-Agent: miniSipServer V2.8.12 (100) Nov 19 2009
Contact: <sip:200@192.168.0.2>
Reason: Q.850; cause=41; text="Temporary failure"
Content-Length: 0


02/10/10 23:33:18 | sip_ua_fsm(5D130004)::_procTUInviteAck
02/10/10 23:33:18 | sip_ua_fsm(5D130004)::change state: UAS_T_WAIT_TRANS_ACK-->UAS_T_WAIT_ALERT
02/10/10 23:33:18 | sip_trans_fsm(4EB40004)::received event(ESIP_TRANS_EVT_IF_RESP) at state (ESIP_TRANS_T_CALLING)
02/10/10 23:33:19 | sip_trans_fsm(4EB40004)::_TprocSipResp
02/10/10 23:33:19 | sip_trans_fsm(4EB40004)::_stopRetransTimer
02/10/10 23:33:19 | sip_trans_fsm(4EB40004)::received event(ESIP_TRANS_EVT_IF_1XX_RESP) at state (ESIP_TRANS_T_CALLING)
02/10/10 23:33:19 | sip_trans_fsm(4EB40004)::change state: ESIP_TRANS_T_CALLING-->ESIP_TRANS_T_PROCEEDING
02/10/10 23:33:19 | sip_trans_fsm(4EB40004)::received event(ESIP_TRANS_EVT_IF_RESP) at state (ESIP_TRANS_T_PROCEEDING)
02/10/10 23:33:19 | sip_trans_fsm(4EB40004)::_TprocSipResp
02/10/10 23:33:19 | sip_trans_fsm(4EB40004)::received event(ESIP_TRANS_EVT_IF_4XX_RESP) at state (ESIP_TRANS_T_PROCEEDING)
02/10/10 23:33:19 | MSS receives SIP message:
02/10/10 23:33:19 | sip_trans_fsm(4EB40004)::_TprocSendACK
SIP/2.0 480 Temporarily Unavailable
Via: SIP/2.0/UDP 192.168.0.1:5060;branch=z9hG4bK-2b590ed3-4b72d1be-4c89d90
From: "100"<sip:100@192.168.0.1>;tag=cd27d64
To: "200"<sip:200@192.168.0.2>;tag=bc50ac
CSeq: 1 INVITE
Call-ID: 129c2944136f4fec79882280-36809920@192.168.0.1
Allow: REGISTER, INVITE, OPTIONS, ACK, CANCEL, BYE, REFER, SUBSCRIBE, NOTIFY, MESSAGE
User-Agent: miniSipServer V2.8.12 (100) Nov 19 2009
Contact: <sip:200@192.168.0.2>
Reason: Q.850; cause=41; text="Temporary failure"
Content-Length: 0


02/10/10 23:33:19 | sip_trans_fsm(4EB40004):: _nInviteSDP=1173356546, _nOfferAns=1
02/10/10 23:33:19 | MSS sends following SIP message to peer GW or UA(192.168.0.2:5060):
02/10/10 23:33:19 | ACK sip:200@192.168.0.2 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.1:5060;branch=z9hG4bK-2b590ed3-4b72d1be-4c89d90
To: "200"<sip:200@192.168.0.2>;tag=bc50ac
From: "100"<sip:100@192.168.0.1>;tag=cd27d64
Call-ID: 129c2944136f4fec79882280-36809920@192.168.0.1
User-Agent: miniSipServer V2.8.12 (100) Nov 19 2009
CSeq: 1 ACK
Max-Forwards: 70
Content-Length: 0


02/10/10 23:33:19 | sip_trans_fsm(4EB40004)::change state: ESIP_TRANS_T_PROCEEDING-->ESIP_TRANS_T_COMPLETED
02/10/10 23:33:19 | sip_ua_fsm(5D130004)::received event(UA_EVT_T_U_1XX_RESP) at state (UAS_T_WAIT_ALERT)
02/10/10 23:33:19 | sip_ua_fsm(5D130004)::received event(UA_EVT_T_U_4XX_RESP) at state (UAS_T_WAIT_ALERT)
02/10/10 23:33:19 | sip_trans_fsm(4EB40004)::received event(ESIP_TRANS_EVT_IF_RESP) at state (ESIP_TRANS_T_COMPLETED)
02/10/10 23:33:19 | cc_fsm(483D0004)::received event(EVT_CALLPROC_P_B_RLC_T) at state (CSA_T_WAIT_ALERT)
02/10/10 23:33:19 | mg_fsm(1BCE0002):: received event(ESRF_EVT_CLEAR_BIND_MSG) at state (ESRF_TWO_PARTIES_BINDED)
02/10/10 23:33:19 | sip_trans_fsm(4EB40004)::_TprocSipResp
02/10/10 23:33:19 | cc_fsm(483D0004)::received event(EVT_CALLPROC_EXCEPTION) at state (CSA_T_WAIT_ALERT)
02/10/10 23:33:19 | mg_fsm(1BCE0002):: received event(ESRF_EVT_ONE_LEG_BIND) at state (ESRF_TWO_PARTIES_BINDED)
02/10/10 23:33:19 | sip_trans_fsm(4EB40004):: receive a re-transfer response message
02/10/10 23:33:19 | cc_fsm(483D0004)::_procKillFsm
02/10/10 23:33:20 | mg_fsm(1BCE0002):: change state: ESRF_TWO_PARTIES_BINDED-->ESRF_ONE_PARTY_BINDED
02/10/10 23:33:20 | sip_trans_fsm(4EB40004)::received event(ESIP_TRANS_EVT_UT_END_MSG) at state (ESIP_TRANS_T_COMPLETED)
02/10/10 23:33:20 | cc_fsm(483D0004)::Destroy
02/10/10 23:33:20 | cc_fsm(232D0003)::received event(EVT_CALLPROC_T_O_RLC) at state (CSA_O_WAIT_ALERT)
02/10/10 23:33:20 | cc_fsm(232D0003)::Destroy
02/10/10 23:33:20 | sip_ua_fsm(5A990003)::received event(UA_EVT_B_P_RLC) at state (UAS_O_WAIT_ALERT)
02/10/10 23:33:20 | sip_trans_fsm(166D0003)::received event(ESIP_TRANS_EVT_UT_RESP_MSG) at state (ESIP_TRANS_O_PROCEEDING)
02/10/10 23:33:20 | mg_fsm(1BCE0002):: received event(ESRF_EVT_CLEAR_BIND_MSG) at state (ESRF_ONE_PARTY_BINDED)
02/10/10 23:33:20 | sip_trans_fsm(166D0003)::_procUTResp
02/10/10 23:33:20 | sip_trans_fsm(166D0003)::received event(ESIP_TRANS_EVT_UT_4XX_RESP) at state (ESIP_TRANS_O_PROCEEDING)
02/10/10 23:33:20 | sip_trans_fsm(166D0003)::_procSendResp
02/10/10 23:33:20 | sip_trans_fsm(166D0003)::_sendSipResp
02/10/10 23:33:20 | MSS sends following SIP message to peer GW or UA(192.168.0.1:19946):
02/10/10 23:33:20 | SIP/2.0 480 Temporarily Unavailable
Via: SIP/2.0/UDP 127.0.0.1:19946;branch=z9hG4bK-d87543-d245421566086d07-1--d87543-
From: "100"<sip:100@192.168.0.1>;tag=73528e7c
To: "200"<sip:200@192.168.0.1>;tag=7de801e1
CSeq: 2 INVITE
Call-ID: MzY0NDU1MjEyNDc4ODVlZGZmMzA4MDgzNDJiYTZkZjE.
Allow: REGISTER, INVITE, OPTIONS, ACK, CANCEL, BYE, REFER, SUBSCRIBE, NOTIFY, MESSAGE
User-Agent: miniSipServer V2.8.12 (100) Nov 19 2009
Contact: <sip:200@192.168.0.1>
Reason: Q.850; cause=41; text="Temporary failure"
Content-Length: 0


02/10/10 23:33:20 | sip_trans_fsm(166D0003)::change state: ESIP_TRANS_O_PROCEEDING-->ESIP_TRANS_O_COMPLETED
02/10/10 23:33:20 | MSS receives SIP message:
ACK sip:200@192.168.0.1 SIP/2.0
Via: SIP/2.0/UDP 127.0.0.1:19946;branch=z9hG4bK-d87543-d245421566086d07-1--d87543-;rport
To: "200"<sip:200@192.168.0.1>;tag=7de801e1
From: "100"<sip:100@192.168.0.1>;tag=73528e7c
Call-ID: MzY0NDU1MjEyNDc4ODVlZGZmMzA4MDgzNDJiYTZkZjE.
CSeq: 2 ACK
Content-Length: 0


02/10/10 23:33:20 | sip_trans_fsm(166D0003)::received event(ESIP_TRANS_EVT_IF_ACK) at state (ESIP_TRANS_O_COMPLETED)
02/10/10 23:33:20 | sip_trans_fsm(166D0003)::_stopRetransTimer
02/10/10 23:33:20 | sip_trans_fsm(166D0003)::change state: ESIP_TRANS_O_COMPLETED-->ESIP_TRANS_O_CONFIRMED
02/10/10 23:33:25 | sip_trans_fsm(166D0003)::received event(ESIP_TRANS_EVT_TIME_OUT) at state (ESIP_TRANS_O_CONFIRMED)

[sipvision]

miniSipServer 2.8.12是否有Lic限制？

[admin]

Hi,

What's Lic?

For the SIP trunk configuration, please send your configuration to us. You can find the configuration in 'config' sub-directory.