Hi Paul, 

Clearwater provides a number of troubleshooting methods. They are described in 
detail at 
https://github.com/Metaswitch/clearwater-docs/wiki/Troubleshooting-and-Recovery.
 In particular, the nodes log to /var/log/<node_type>/<node_type>*.txt.

On Sprout then, you should be able to find the logs at 
/var/log/sprout/sprout*.txt. By default, it is set to log level 2, which only 
includes errors and very high-level events. To enable more detailed trace, 
change the log level to 5 by writing log_level=5 to 
/etc/clearwater/user_settings (creating it if it doesn't exist already), and 
restart sprout (using service sprout stop - monit automatically restarts it). 

In this case, the iFC wasn't matched as the RequestURI didn't match - we match 
against the "hostport" (the hostname and port), not the full URI (this is as 
defined in 3GPP TS 29.228 - see table F.1). You will need to use "example.com" 
rather than a full URI.

Hope this helps, 

Ellie 

-----Original Message-----
From: [email protected] 
[mailto:[email protected]] On Behalf Of Paul Sun
Sent: 02 July 2014 10:38
To: [email protected]
Subject: [Clearwater] Problem on making S-CSCF to redirect INVITE to AS based 
on the RequestURI

Hi

I am trying to make a SPROUT to AS based on the RequestURI, but it failed, is 
there any way to trace where goes wrong?

Below is the Cassandra information

       sip:[email protected] |             <?xml version="1.0" 
encoding="UTF-8"?><IMSSubscription><PrivateID>[email protected]</PrivateID><ServiceProfile><PublicIdentity><Identity>sip:[email protected]</Identity><Extension><IdentityType>0</IdentityType></Extension></PublicIdentity><InitialFilterCriteria><Priority>0</Priority><TriggerPoint><ConditionTypeCNF>0</ConditionTypeCNF><SPT><ConditionNegated>0</ConditionNegated><Group>0</Group><Method>INVITE</Method><Extension></Extension></SPT><SPT><ConditionNegated>0</ConditionNegated><Group>0</Group><SessionCase>0</SessionCase><Extension></Extension></SPT><SPT><ConditionNegated>0</ConditionNegated><Group>0</Group><RequestURI>sip:[email protected]</RequestURI><Extension></Extension></SPT></TriggerPoint><ApplicationServer><ServerName>sip:192.168.208.222:5060</ServerName><DefaultHandling>1</DefaultHandling></ApplicationServer></InitialFilterCriteria></ServiceProfile></IMSSubscription>
 |          True

Based on the above SPT, when it is INVITE, and the Request-URI matched with 
sip:[email protected], it will then send to sip:192.168.208.222:5060, 
any idea why it did not forward?


-          PS?
_______________________________________________
Clearwater mailing list
[email protected]
http://lists.projectclearwater.org/listinfo/clearwater
_______________________________________________
Clearwater mailing list
[email protected]
http://lists.projectclearwater.org/listinfo/clearwater

Reply via email to