Sorry， I have no idea about what’s ‘subscriber’. It’s almost same with the environment which is setup by docker-compose (https://github.com/Metaswitch/clearwater-docker). But all call fail.
I found a PUBLISH message : The content-Length is zero. PUBLISH sip:[email protected];transport=TCP SIP/2.0^M Via: SIP/2.0/TCP 175.128.0.113:55316;branch=z9hG4bK-524287-1---4b2b34f926a6c876;rport^M Max-Forwards: 70^M Route: <sip:10.1.0.217:5054;transport=TCP;lr;orig>^M Contact: <sip:[email protected]:55316;transport=TCP>^M To: "2323"<sip:[email protected];transport=TCP>^M From: "2323"<sip:[email protected];transport=TCP>;tag=ea19e074^M Call-ID: ZuNcniFDAQplqlNX3qyFJQ..^M CSeq: 319 PUBLISH^M Expires: 600^M Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, INFO, SUBSCRIBE^M Supported: replaces, norefersub, extended-refer, timer, outbound, path, X-cisco-serviceuri^M User-Agent: Z 3.9.32144 r32121^M Event: presence^M Allow-Events: presence, kpml^M Content-Length: 0^M ^M While checking the docker-compose env, I got Max-Forwards: 70^M Route: <sip:172.17.0.5:5054;transport=TCP;lr;orig>^M Contact: <sip:[email protected]:51158;transport=TCP>^M To: "123"<sip:[email protected];transport=TCP>^M From: "123"<sip:[email protected];transport=TCP>;tag=e72f4e32^M Call-ID: vqETasJUaN4hD1h5scKyUA..^M CSeq: 1 PUBLISH^M Expires: 600^M Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, INFO, SUBSCRIBE^M Content-Type: application/pidf+xml^M Supported: replaces, norefersub, extended-refer, timer, outbound, path, X-cisco-serviceuri^M User-Agent: Z 3.9.32144 r32121^M Event: presence^M Allow-Events: presence, kpml^M Content-Length: 271^M ^M <?xml version="1.0" encoding="UTF-8"?>^M <presence xmlns="urn:ietf:params:xml:ns:pidf"^M entity="sip:[email protected];transport=TCP">^M <tuple id="6505550782" >^M <status><basic>open</basic></status>^M <note>Online</note>^M </tuple>^M </presence>^M Is that helpful? Thanks. Jia Xuan 发件人: Chris Elford [mailto:[email protected]] 发送时间: 2016年2月26日 0:27 收件人: jiaxuan 抄送: [email protected] 主题: RE: [Project Clearwater] Test Clearwater on Openshift Hi, I’ve taken a look at your Sprout logs. In order to diagnose your problem, it would be useful to have some more information about what you are seeing. ・ What are the subscribers are you trying to call between? ・ Are you seeing all calls fail or just occasional ones? We’ve looked into the two issues that you mentioned below. It looks like Ralf is configured to send billing data to a CDF at example.com. The logs in your message show that it is failing to do so. You can configure a real CDF by changing the value of ‘cdf_identity’ in the deployment’s shared config. See http://clearwater.readthedocs.org/en/latest/Clearwater_Configuration_Options _Reference/index.html for details. We have looked into the tombstone issue that you mention below. We do not think that this will cause any problems. We have raised https://github.com/Metaswitch/sprout/issues/1334 to track working around it and cleaning up those entries. Yours, Chris From: Clearwater [mailto:[email protected]] On Behalf Of jiaxuan Sent: 25 February 2016 08:44 To: [email protected] Subject: [Project Clearwater] Test Clearwater on Openshift Hi list: I have installed clearwater, following “Manual Install Instrutions”. The difference is that it’s running on Openshift which is using Kurbernetes. Currently the Ellis model is running well, as I can make my X-Lite client registered in. The problem is that: The call function doesn’t work properly. I list what I have found: 1. Ralf: from /var/log/ralf/ralf_2016XXX 24-02-2016 13:00:34.447 UTC Verbose diameterstack.cpp:1413: Sending Diameter message of type 271 on transaction 0x7f17d0005100 24-02-2016 13:00:34.447 UTC Debug diameterstack.cpp:397: Routing out callback from freeDiameter 24-02-2016 13:00:34.447 UTC Error diameterstack.cpp:293: Routing error: 'No remaining suitable candidate to route the message to' for message with Command-Code 271, Destination-Host and Destination-Realm example.com 24-02-2016 13:00:34.447 UTC Debug freeDiameter: Iterating on rules of COMMAND: '(generic error format)'. 24-02-2016 13:00:34.447 UTC Debug freeDiameter: Calling callback registered when query was sent (0x437910, 0x7f17d0005100) 24-02-2016 13:00:34.447 UTC Verbose diameterstack.cpp:1093: Got Diameter response of type 271 - calling callback on transaction 0x7f17d0005100 24-02-2016 13:00:34.447 UTC Warning peer_message_sender.cpp:125: Failed to send ACR to (number 0) 24-02-2016 13:00:34.447 UTC Error peer_message_sender.cpp:145: Failed to connect to all CCFs, message not sent 24-02-2016 13:00:34.447 UTC Warning session_manager.cpp:319: Session for 79048MzlhMGNjMzc4YmEyY2NlMGEyZmU2ODNmYjZjM2E1ZGY received error from CDF 24-02-2016 13:00:34.470 UTC Verbose httpstack.cpp:286: Process request for URL /call-id/79048MzlhMGNjMzc4YmEyY2NlMGEyZmU2ODNmYjZjM2E1ZGY, args (null) 2. Sprout:from /var/log/sprout/sprout_current.txt . We can see there’re several ‘tombstone’ element in this json. 25-02-2016 08:05:00.076 UTC Debug avstore.cpp:72: Set AV for [email protected]\7b66730d304dcdcb {"digest":{"ha1":"3fb2ca6bb49c77b0907e080079d325a0","realm":"example.com","q op":"auth"},"branch":"z9hG4bKPjbALlVrXogjQKxNGPi1wmdGhDKXTFBr7h","tombstone" :true,"tombstone":true,"tombstone":true} I attached all the log files in this email. We appreciate your response. Thanks. Jia Xuan China Mobile Research Institute
_______________________________________________ Clearwater mailing list [email protected] http://lists.projectclearwater.org/mailman/listinfo/clearwater_lists.projectclearwater.org
