Hi Juan
Thank you for your questions and the diagnostics you have provided.
I think there are two different bits of configuration here that are incorrect
which are causing the symptoms you are seeing.
Looking through the Sprout log file you sent me I can see on line 773 "Signal 6
caught" after which Sprout crashes. This typically means that monit has killed
the process.
It looks like the reason for monit killing the process comes from a routing
error. Looking through the logs I can see:
18-04-2017 07:40:46.895 UTC Debug uri_classifier.cpp:204: Classified URI as 4
this suggests some incorrect configuration such as home_domain in
/etc/clearwater/shared config being set to an IP address. home_domain should be
the main SIP domain of the deployment, and determines which SIP URIs Clearwater
will treat as local. Using an IP address here rather than a domain name could
cause a SIP address to be routed as a home domain URI rather than a node-local
one.
In addition I can also see in the logs:
18-04-2017 07:40:26.466 UTC Error bgcfservice.cpp:98: Failed to read BGCF
configuration data: {
"routes" : [
{ "name" : "route to GB 42",
"domain" : "192.168.38.42",
"route" : ["sip:192.168.38.42:5060;transport=UDP"]
},
]
}
This log suggests that there is something wrong with the BGCF routing record
used above, if you look through it you can the final comma is unnecessary
because there is only one routing rule. This probably isn't causing the loop
you are seeing but it would cause off-net calls to fail.
Could you please:
* Send me the contents of your /etc/clearwater/shared_config file
* If home_domain is indeed an IP address could you change it to the
domain name of your deployment and run "sudo cw-upload_shared_config"
* Delete the comma in /etc/clearwater/bgcf.json and run "sudo
cw-upload_bgcf_json"
Once you have done this you can try making a call, please let me know how this
goes.
Thanks,
Andrew
From: Clearwater [mailto:[email protected]] On
Behalf Of Juan Sepulveda
Sent: Monday, April 24, 2017 8:36 AM
To: [email protected]
Subject: Re: [Project Clearwater] Sprout scratch
Hi,
please can you check why a loop is detected? We are in the max log level. No
more info to explain the loop.
Please help us.
***********************************************************************************************************************************************
--start msg--
OPTIONS sip:[email protected]:5054 SIP/2.0
Route: <sip:cw-sprout1.ims02.as20650.net;transport=tcp;lr;service=registrar>
Via: SIP/2.0/TCP
192.168.38.55;rport=34358;received=192.168.38.55;branch=z9hG4bK-319922
Max-Forwards: 1
To: <sip:[email protected]>
From: "poll-sip" <sip:[email protected]>;tag=319922
Call-ID: poll-sip-319922
CSeq: 319922 OPTIONS
Contact: <sip:192.168.38.55>
Accept: application/sdp
User-Agent: poll-sip
Content-Length: 0
--end msg--
24-04-2017 07:20:32.545 UTC Debug pjutils.cpp:741: Cloned tdta0x7f891800f080 to
tdta0x7f8918013500
24-04-2017 07:20:32.545 UTC Debug sproutletproxy.cpp:1238: Remove top Route
header Route:
<sip:cw-sprout1.ims02.as20650.net;transport=tcp;lr;service=registrar>
24-04-2017 07:20:32.545 UTC Debug sproutletproxy.cpp:1813: Adding message
0x7f8918013b10 => txdata 0x7f89180135a8 mapping
24-04-2017 07:20:32.545 UTC Verbose sproutletproxy.cpp:1658:
registrar-0x7f891800d180 pass initial request Request msg OPTIONS/cseq=319922
(tdta0x7f8918013500) to Sproutlet
24-04-2017 07:20:32.545 UTC Info registrarsproutlet.cpp:172: Registrar
sproutlet received initial request
24-04-2017 07:20:32.545 UTC Debug uri_classifier.cpp:174: home domain: true,
local_to_node: true, is_gruu: false, enforce_user_phone: false, prefer_sip:
true, treat_number_as_phone: false
24-04-2017 07:20:32.545 UTC Debug uri_classifier.cpp:204: Classified URI as 4
24-04-2017 07:20:32.545 UTC Debug sproutletproxy.cpp:384: Creating URI for
service subscription
24-04-2017 07:20:32.545 UTC Debug sproutletproxy.cpp:405: Constructed URI
sip:cw-sprout1.ims02.as20650.net;transport=tcp;lr;service=subscription
24-04-2017 07:20:32.545 UTC Debug sproutletproxy.cpp:1409: Sproutlet
send_request 0x7f8918013b10
24-04-2017 07:20:32.545 UTC Verbose sproutletproxy.cpp:1445:
registrar-0x7f891800d180 sending Request msg OPTIONS/cseq=319922
(tdta0x7f8918013500) on fork 0
24-04-2017 07:20:32.545 UTC Debug sproutletproxy.cpp:1828: Processing actions
from sproutlet - 0 responses, 1 requests, 0 timers
24-04-2017 07:20:32.545 UTC Debug sproutletproxy.cpp:1868: Processing request
0x7f89180135a8, fork = 0
24-04-2017 07:20:32.545 UTC Debug sproutletproxy.cpp:1992:
registrar-0x7f891800d180 transmitting request on fork 0
24-04-2017 07:20:32.545 UTC Debug sproutletproxy.cpp:2006:
registrar-0x7f891800d180 store reference to non-ACK request Request msg
OPTIONS/cseq=319922 (tdta0x7f8918013500) on fork 0
24-04-2017 07:20:32.545 UTC Debug sproutletproxy.cpp:1820: Removing message
0x7f8918013b10 => txdata 0x7f89180135a8 mapping
24-04-2017 07:20:32.545 UTC Info sproutletproxy.cpp:818: Loop detected -
rejecting request with 483 status code
24-04-2017 07:20:32.545 UTC Verbose sproutletproxy.cpp:2140: Routing Response
msg 483/OPTIONS/cseq=319922 (tdta0x7f8918076070) (297 bytes) to upstream
sproutlet registrar:
--start msg--
SIP/2.0 483 Too Many Hops
Via: SIP/2.0/TCP
192.168.38.55;rport=34358;received=192.168.38.55;branch=z9hG4bK-319922
Call-ID: poll-sip-319922
From: "poll-sip" <sip:[email protected]>;tag=319922
To: <sip:[email protected]>;tag=z9hG4bK-319922
CSeq: 319922 OPTIONS
Content-Length: 0
--end msg--
THx
Kr
Juan
From: Clearwater [mailto:[email protected]] On
Behalf Of Juan Sepulveda
Sent: mardi 18 avril 2017 10:02
To: '[email protected]'
Subject: [Project Clearwater] Sprout scratch
Hi,
Since Friday for an unknown reason, the sprout start to scratch permanently. We
can see in the log internal loop and the poll_sprout_sip process restarting.
Logs are in attached file. Please can you debug this issue?
The only actions we performed last Friday is to fix a etcd process failure and
we add 2 lines in the shared_config file:
billing_realm=ims02.as20650.net
cdf_identity=192.169.38.56
Currently, those 2 lines are commented.
In the attached file, you have also the version and the monit command output.
Let me know if you need more info.
Thx
Kr
Juan
IP Nexia, a new brand of Toledo Telecom.
[Description: http://www.ipnexia.com/images/pix.gif]
Juan Sepulveda
Voip and Network Engineer
M + 32 478 97 98 79 T +32 2 600 16 69 @
[email protected]<mailto:[email protected]>
IP Nexia Kouterveldstraat, 2 - 1831 Diegem
Tel +32 2 648 08 48 Fax +32 2 646 44 24
www.ipnexia.com<http://www.ipnexia.com/>
Disclaimer<http://www.ipnexia.com/disclaimer/disclaimer.html>
[Description: http://www.ipnexia.com/images/back-sign2_02.jpg]
[Description: http://www.ipnexia.com/images/back-sign2_03.jpg]
> Please consider the environmental impact of needlessly printing this e-mail.
_______________________________________________
Clearwater mailing list
[email protected]
http://lists.projectclearwater.org/mailman/listinfo/clearwater_lists.projectclearwater.org
