1. 首頁
  2. 問答
  3. TeleStax RestSm集成在MetaSwitch Clearwater

TeleStax RestSm集成在MetaSwitch Clearwater

2015-04-22 67 views
1

我們試圖在我們的LAB中部署RestComm服務器，但有一些麻煩將它集成到IMS。TeleStax RestSm集成在MetaSwitch Clearwater

那時我們有： 在一個網絡子網中的一臺物理設備上安裝6臺虛擬機（Clearwater IMS：萌芽，非法，ellis，homer，homestead; telestax：restcomm）。

我們測試了Restcomm AMI Demos，所有的作品都很好。文字到語音的作品，電話正在工作。

比我們試圖整合克利爾沃特IMS和restcomm（http://telestax.wpengine.netdna-cdn.com/wp-content/uploads/2013/12/ClearWater-RestComm-Integration-2013.pdf），但在這裏我們有非工作的解決方案：

10.199.200.89 -> 10.199.200.95 SIP/SDP 399 Request: INVITE sip:[email protected], with session description 
    10.199.200.95 -> 10.199.200.89 SIP 801 Status: 404 Not found 
    10.199.200.89 -> 10.199.200.95 SIP 556 Request: ACK sip:[email protected]

（10.199.200.89 - 清水 - 發芽，10.199.200.95 - restcomm，0000006606 - SIP sip number on restcomm）

restcomm迴應「404沒有找到」，因爲我們知道這是因爲該域名是「cw.domain.ru」，但沒有找到任何配置參數設置。從Clearwater IMS到Restcomm服務的工作呼叫流程

在Restcomm日誌，我們有：

12:25:32,603 INFO [org.mobicents.servlet.sip.core.session.SipApplicationSessionImpl] (RestComm-akka.actor.default-dispatcher-12908) Invalidating the following sip application session 671d0ad7-baf1-4867-b 
4c1-a1d572e3a37c;RestComm 

12:25:32,604 INFO [org.mobicents.servlet.sip.core.session.SipSessionImpl] (RestComm-akka.actor.default-dispatcher-12908) Invalidating the sip session (97067297_ba1d553a_57a5b08a_671d0ad7-baf1-4867-b4c1-a 
1d572e3a37c;[email protected];671d0ad7-baf1-4867-b4c1-a1d572e3a37c;RestComm) 

12:25:32,604 INFO [org.mobicents.servlet.sip.core.session.SipApplicationSessionImpl] (RestComm-akka.actor.default-dispatcher-12908) The following sip application session 671d0ad7-baf1-4867-b4c1-a1d572e3a 
37c;RestComm has been invalidated 

12:26:30,998 INFO [gov.nist.javax.sip.stack.SIPTransactionStack] (SIP-TCP-Core-PipelineThreadpool-7) <message 
from="10.199.200.89:51730" 
to="10.199.200.95:5080" 
time="1429521990997" 
isSender="false" 
transactionId="z9hg4bkpjyfeolh7nut46itlpj376kiq3nchyw7ga" 
callId="[email protected]" 
firstLine="INVITE sip:[email protected] SIP/2.0" 
> 
<![CDATA[INVITE sip:[email protected] SIP/2.0 
Via: SIP/2.0/TCP 10.199.200.89:51730;rport=51730;branch=z9hG4bKPjyfeOlh7NUt46itlpj376kIQ3ncHyW7ga;received=10.199.200.89 
Via: SIP/2.0/TCP 10.199.200.87:42302;rport=42302;received=10.199.200.87;branch=z9hG4bKPjjmliVkif1UEiatjnn-ja0uL8bw3zF7RD 
Via: SIP/2.0/TCP 10.199.30.122:5062;rport=50235;received=10.199.30.122;branch=z9hG4bK2054587840;alias 
Record-Route: <sip:sprout.cw.domain.ru:5054;transport=TCP;lr;service=scscf;billing-role=charge-orig> 
Record-Route: <sip:10.199.200.87:5058;transport=TCP;lr> 
Record-Route: <sip:[email protected]:5060;transport=TCP;lr> 
From: "[email protected]" <sip:[email protected]>;tag=71152997 
To: <sip:[email protected]> 
Call-ID: [email protected] 
CSeq: 10 INVITE 
Contact: "[email protected]" <sip:[email protected]:5062;transport=tcp> 
Max-Forwards: 64 
User-Agent: Grandstream GXP1405 1.0.7.4 
Supported: replaces,path,timer 
Allow: INVITE,ACK,OPTIONS,CANCEL,BYE,SUBSCRIBE,NOTIFY,INFO,REFER,UPDATE,MESSAGE 
Accept: application/sdp,application/dtmf-relay 
P-Asserted-Identity: <sip:[email protected]> 
Session-Expires: 600 
Privacy: none 
Route: <sip:10.199.200.95:5080;lr> 
Route: <sip:[email protected]:5054;lr> 
P-Served-User: <sip:[email protected]>;regstate=reg;sescase=term 
Content-Type: application/sdp 
Content-Length: 410 
v=0 
o=0000006625 8001 8000 IN IP4 10.199.30.122 
s=SIP Call 
c=IN IP4 10.199.30.122 
t=0 0 
m=audio 5008 RTP/AVP 0 8 18 97 9 4 2 101 
a=sendrecv 
a=rtpmap:0 PCMU/8000 
a=ptime:20 
a=rtpmap:8 PCMA/8000 
a=rtpmap:18 G729/8000 
a=fmtp:18 annexb=no 
a=rtpmap:97 iLBC/8000 
a=fmtp:97 mode=30 
a=rtpmap:9 G722/8000 
a=rtpmap:4 G723/8000 
a=rtpmap:2 G726-32/8000 
a=rtpmap:101 telephone-event/8000 
a=fmtp:101 0-15 
]]> 
</message> 

12:26:31,006 INFO [gov.nist.javax.sip.stack.SIPTransactionStack] (RestComm-akka.actor.default-dispatcher-12910) <message 
from="10.199.200.95:5080" 
to="10.199.200.89:51730" 
time="1429521991006" 
isSender="true" 
transactionId="z9hg4bkpjyfeolh7nut46itlpj376kiq3nchyw7ga" 
callId="[email protected]" 
firstLine="SIP/2.0 404 Not found" 
> 
<![CDATA[SIP/2.0 404 Not found 
To: <sip:[email protected]>;tag=57299471_ba1d553a_57a5b08a_a01b3174-c173-4651-8c15-8b5cf0ecbfd9 
Via: SIP/2.0/TCP 10.199.200.89:51730;rport=51730;branch=z9hG4bKPjyfeOlh7NUt46itlpj376kIQ3ncHyW7ga;received=10.199.200.89 
Via: SIP/2.0/TCP 10.199.200.87:42302;rport=42302;received=10.199.200.87;branch=z9hG4bKPjjmliVkif1UEiatjnn-ja0uL8bw3zF7RD 
Via: SIP/2.0/TCP 10.199.30.122:5062;rport=50235;received=10.199.30.122;branch=z9hG4bK2054587840;alias 
CSeq: 10 INVITE 
Call-ID: [email protected] 
From: "[email protected]" <sip:[email protected]>;tag=71152997 
Server: Mobicents Restcomm MAJOR_VERSION_NUMBER.BUILD_NUMBER 
Contact: <sip:10.199.200.95:5080;transport=tcp> 
Content-Length: 0 
]]> 
</message> 

12:26:31,007 INFO [org.mobicents.servlet.sip.core.dispatchers.InitialRequestDispatcher] (SIP-TCP-Core-PipelineThreadpool-7) Request event dispatched to RestComm 

12:26:31,012 INFO [gov.nist.javax.sip.stack.SIPTransactionStack] (SIP-TCP-Core-PipelineThreadpool-8) <message 
from="10.199.200.89:51730" 
to="10.199.200.95:5080" 
time="1429521991011" 
isSender="false" 
transactionId="z9hg4bkpjyfeolh7nut46itlpj376kiq3nchyw7ga" 
callId="[email protected]" 
firstLine="ACK sip:[email protected] SIP/2.0" 
> 
<![CDATA[ACK sip:[email protected] SIP/2.0 
Via: SIP/2.0/TCP 10.199.200.89:51730;rport=51730;branch=z9hG4bKPjyfeOlh7NUt46itlpj376kIQ3ncHyW7ga;received=10.199.200.89 
Max-Forwards: 70 
From: "[email protected]" <sip:[email protected]>;tag=71152997 
To: <sip:[email protected]>;tag=57299471_ba1d553a_57a5b08a_a01b3174-c173-4651-8c15-8b5cf0ecbfd9 
Call-ID: [email protected] 
CSeq: 10 ACK 
Route: <sip:10.199.200.95:5080;lr> 
Route: <sip:[email protected]:5054;lr> 
Content-Length: 0 
]]> 
</message> 

12:26:32,645 INFO [gov.nist.javax.sip.stack.SIPTransactionStack] (RestComm-akka.actor.default-dispatcher-12910) <message 
from="10.199.200.95:5080" 
to="10.199.30.107:43240" 
time="1429521992644" 
isSender="true" 
transactionId="z9hg4bk79f90da6-eedd-48e9-9298-0de946eb7ac4_57a5b08a_d9ab1446-96ab-402f-b751-cd728cb74353" 
callId="[email protected]" 
firstLine="OPTIONS sip:[email protected]:43240;transport=tcp;lr SIP/2.0" 
> 
<![CDATA[OPTIONS sip:[email protected]:43240;transport=tcp;lr SIP/2.0 
Call-ID: [email protected] 
CSeq: 1 OPTIONS 
From: <sip:[email protected]>;tag=94331963_ba1d553a_57a5b08a_79f90da6-eedd-48e9-9298-0de946eb7ac4 
To: <sip:[email protected]:43240> 
Max-Forwards: 70 
User-Agent: Mobicents Restcomm MAJOR_VERSION_NUMBER.BUILD_NUMBER 
Contact: <sip:[email protected]:5080;transport=tcp> 
Via: SIP/2.0/TCP 10.199.200.95:5080;branch=z9hG4bK79f90da6-eedd-48e9-9298-0de946eb7ac4_57a5b08a_d9ab1446-96ab-402f-b751-cd728cb74353 
Route: <sip:[email protected]:43240;transport=tcp;lr> 
Content-Length: 0 
]]> 
</message> 

12:26:32,692 INFO [gov.nist.javax.sip.stack.SIPTransactionStack] (SIP-TCP-Core-PipelineThreadpool-9) <message 
from="10.199.30.107:43240" 
to="10.199.200.95:5080" 
time="1429521992692" 
isSender="false" 
transactionId="z9hg4bk79f90da6-eedd-48e9-9298-0de946eb7ac4_57a5b08a_d9ab1446-96ab-402f-b751-cd728cb74353" 
callId="[email protected]" 
firstLine="SIP/2.0 200 OK" 
> 
<![CDATA[SIP/2.0 200 OK 
Via: SIP/2.0/TCP 10.199.200.95:5080;branch=z9hG4bK79f90da6-eedd-48e9-9298-0de946eb7ac4_57a5b08a_d9ab1446-96ab-402f-b751-cd728cb74353 
From: <sip:[email protected]>;tag=94331963_ba1d553a_57a5b08a_79f90da6-eedd-48e9-9298-0de946eb7ac4 
To: <sip:[email protected]:43240>;tag=995341531 
Call-ID: [email protected] 
CSeq: 1 OPTIONS 
Supported: replaces,path,timer 
User-Agent: Grandstream GXP1405 1.0.7.8 
Allow: INVITE,ACK,OPTIONS,CANCEL,BYE,SUBSCRIBE,NOTIFY,INFO,REFER,UPDATE,MESSAGE 
Content-Length: 0 
]]> 
</message> 

12:26:32,696 INFO [org.mobicents.servlet.sip.core.session.SipApplicationSessionImpl] (RestComm-akka.actor.default-dispatcher-12910) Invalidating the following sip application session 79f90da6-eedd-48e9-9298-0de946eb7ac4;RestComm 

12:26:32,696 INFO [org.mobicents.servlet.sip.core.session.SipSessionImpl] (RestComm-akka.actor.default-dispatcher-12910) Invalidating the sip session (94331963_ba1d553a_57a5b08a_79f90da6-eedd-48e9-9298-0de946eb7ac4;[email protected];79f90da6-eedd-48e9-9298-0de946eb7ac4;RestComm) 

12:26:32,697 INFO [org.mobicents.servlet.sip.core.session.SipApplicationSessionImpl] (RestComm-akka.actor.default-dispatcher-12910) The following sip application session 79f90da6-eedd-48e9-9298-0de946eb7ac4;RestComm has been invalidated 

12:26:39,510 INFO [org.mobicents.servlet.sip.core.session.SipSessionImpl] (MSS-Executor-Thread-3) Invalidating the sip session (71152997;[email protected];a01b3174-c173-4651-8c15-8b5cf0ecbfd9;RestComm) 

12:26:39,511 INFO [org.mobicents.servlet.sip.core.session.SipApplicationSessionImpl] (MSS-Executor-Thread-3) Invalidating the following sip application session a01b3174-c173-4651-8c15-8b5cf0ecbfd9;RestComm 

12:26:39,511 INFO [org.mobicents.servlet.sip.core.session.SipApplicationSessionImpl] (MSS-Executor-Thread-3) The following sip application session a01b3174-c173-4651-8c15-8b5cf0ecbfd9;RestComm has been invalidated 

12:27:12,016 INFO [gov.nist.javax.sip.stack.SIPTransactionStack] (SIP-TCP-Core-PipelineThreadpool-10) <message 
from="10.199.200.89:34239" 
to="10.199.200.95:5080" 
time="1429522032014" 
isSender="false" 
transactionId="z9hg4bkpjvmnmgxo253hvm75so5qm.sn-vccrqjfa" 
callId="231825113" 
firstLine="INVITE sip:[email protected] SIP/2.0"
  1. RestComm版本：mobicents-Restcomm-JBoss的AS7-7.0.2
  2. 0000006606已於restcomm配置：
 
    { 
    "sid": "PN9905e897237440aaad83af5ee9b8d502", 
    "account_sid": "ACae6e420f425248d6a26948c17a9e2acf", 
    "friendly_name": "0000006606", 
    "phone_number": "0000006606", 
    "voice_url": "/restcomm-rvd/services/apps/rvdSayVerbDemo/controller", 
    "voice_method": "POST", 
    "voice_fallback_url": null, 
    "voice_fallback_method": "POST", 
    "status_callback": null, 
    "status_callback_method": "POST", 
    "voice_caller_id_lookup": false, 
    "voice_application_sid": null, 
    "date_created": "Mon, 20 Apr 2015 19:00:34 +0300", 
    "date_updated": "Mon, 20 Apr 2015 19:00:34 +0300", 
    "sms_url": null, 
    "sms_method": "POST", 
    "sms_fallback_url": null, 
    "sms_fallback_method": "POST", 
    "sms_application_sid": null, 
    "capabilities": { 
    "voice_capable": false, 
    "sms_capable": false, 
    "mms_capable": false, 
    "fax_capable": false 
    }, 
    "api_version": "2012-04-24", 
    "uri": "/restcomm/2012-04-24/Accounts/ACae6e420f425248d6a26948c17a9e2acf/IncomingPhoneNumbers/PN9905e897237440aaad83af5ee9b8d502.json" 
    }
  1. 我試圖用軟電話撥打1234號碼，在restcomm上註冊。它的工作原理。
  2. 是的，我已經看到了它在restcomm http://docs.telestax.com/restcomm-understanding-autoconfigure-script/和網口：
 
@rcomm01:~$ netstat -nlptu 
(Not all processes could be identified, non-owned process info 
will not be shown, you would have to be root to see it all.) 
Active Internet connections (only servers) 
Proto Recv-Q Send-Q Local Address   Foreign Address   State  PID/Program name 
tcp  0  0 127.0.0.1:9999   0.0.0.0:*  LISTEN  3049/java 
tcp  0  0 10.199.200.95:8080  0.0.0.0:*    LISTEN  3049/java   
tcp  0  0 0.0.0.0:8787   0.0.0.0:*    LISTEN  3049/java   
tcp  0  0 0.0.0.0:22    0.0.0.0:*    LISTEN  -     
tcp  0  0 10.199.200.95:5080  0.0.0.0:*    LISTEN  3049/java   
tcp  0  0 10.199.200.95:5081  0.0.0.0:*    LISTEN  3049/java   
tcp  0  0 10.199.200.95:5082  0.0.0.0:*    LISTEN  3049/java   
tcp  0  0 10.199.200.95:4447  0.0.0.0:*    LISTEN  3049/java   
tcp  0  0 127.0.0.1:9990   0.0.0.0:*    LISTEN  3049/java   
tcp6  0  0 :::22     :::*     LISTEN  -     
udp  0  0 10.199.200.95:5080  0.0.0.0:*       3049/java   
udp  0  0 0.0.0.0:48637   0.0.0.0:*       -     
udp  0  0 0.0.0.0:68    0.0.0.0:*       -     
udp  0  0 10.199.200.95:2427  0.0.0.0:*       3050/java   
udp  0  0 10.199.200.95:2727  0.0.0.0:*       3049/java   
udp6  0  0 :::39678    :::*        -

來源

2015-04-22 boboba

回答

2

你使用哪種版本RestComm的？ 您是否將0000006606配置爲RestComm應用程序？您是否嘗試先打電話給1234以查看是否將媒體公告作爲煙霧測試回放？ 您可以使用來自https://mobicents.ci.cloudbees.com/view/RestComm/job/RestComm/lastSuccessfulBuild/artifact/的最新二進制數來克服404錯誤。 順便說一句http://telestax.wpengine.netdna-cdn.com/wp-content/uploads/2013/12/ClearWater-RestComm-Integration-2013.pdf有點過時了，請使用http://docs.telestax.com/restcomm-understanding-autoconfigure-script/，「綁定到不同的IP地址」部分來啓動RestComm。這樣它將自動修改所有配置文件中的IP地址。

來源

2015-04-22 14:52:55 jeand

+1

你好，我增加了主要問題的附加信息。 – boboba

+1

我下載了最新版本：mobicents-Restcomm-JBoss-AS7-7.2.2.4。 而在這個版本上，我沒有收到消息「SIP：未找到」。 但還有其他問題，在restcomm啓動後，第一個調用正常進行（但不總是）。以下調用沒有聲音，因爲restcomm不發送rtp數據包。我附加了網絡捕獲日誌，獨立日誌和mobicent媒體日誌可以分析此行爲。 https://www.dropbox.com/s/wf039wu66ihp285/restcomm_logs.zip?dl=0 預先感謝您。 – boboba

+0

@boboba檢查pcap文件，我可以看到最初的INVITE來自IP地址10.199.200.89，這是一個Grandstream sip設備，我可以從User-Agent頭部看到，但SDP提供了在RTP連接時要求IP地址「IN IP4 10.199.30.122」端口5008。這看起來是錯誤的，這似乎是導致沒有公告的問題。 – GeorgeVagenas

相關問題

 相關問題