Thanks Ellie,
I control the session timer on Sprout and Bono as your suggestion. My issue is
fixed.
Regards,Tam Vo
On Tuesday, July 14, 2015 5:38 PM, Eleanor Merry
<[email protected]> wrote:
<!--#yiv0793431346 _filtered #yiv0793431346 {font-family:Calibri;panose-1:2
15 5 2 2 2 4 3 2 4;} _filtered #yiv0793431346 {font-family:Tahoma;panose-1:2 11
6 4 3 5 4 4 2 4;} _filtered #yiv0793431346 {font-family:"Helvetica
Neue";}#yiv0793431346 #yiv0793431346 p.yiv0793431346MsoNormal, #yiv0793431346
li.yiv0793431346MsoNormal, #yiv0793431346 div.yiv0793431346MsoNormal
{margin:0cm;margin-bottom:.0001pt;font-size:12.0pt;font-family:"Times New
Roman", "serif";}#yiv0793431346 a:link, #yiv0793431346
span.yiv0793431346MsoHyperlink
{color:blue;text-decoration:underline;}#yiv0793431346 a:visited, #yiv0793431346
span.yiv0793431346MsoHyperlinkFollowed
{color:purple;text-decoration:underline;}#yiv0793431346
span.yiv0793431346EmailStyle17 {font-family:"Calibri",
"sans-serif";color:#1F497D;}#yiv0793431346 .yiv0793431346MsoChpDefault
{font-size:10.0pt;} _filtered #yiv0793431346 {margin:72.0pt 72.0pt 72.0pt
72.0pt;}#yiv0793431346 div.yiv0793431346WordSection1 {}-->Hi, Sprout rejects
the call because the Session-Expires header is too large (it looks like the AS
has updated the Session-Expires value). 13-07-2015 09:30:06.065 UTC Info
pjutils.cpp:2242: Requested session expiry is too large We control the
session-expires time as we use session refreshes in our RF billing solution
(and the length of the refresh is the margin of error for billing in the case
where a call disappears without a BYE transaction). If you need a higher
Session-Expires time, you can control this using the max_session_expires
configuration option – please
seehttp://clearwater.readthedocs.org/en/latest/Clearwater_Configuration_Options_Reference/index.html
for more details on the available options, and how to update them. Ellie
From: [email protected]
[mailto:[email protected]]On Behalf Of atva angel
Sent: 13 July 2015 18:06
To: Clearwater Mail
Subject: [Clearwater] Using external AS: IMS call fails since Sprout returns
480 Temporarily Unavailable Hi community, I has Clearwater IMSCore done
with my Application Server connected for the integration. I define 3 IFCs for
my AS to allow the IMS client to do Register and Call. Although 2 IMS clients
can register successfully via X-lite but they failed to call each others.
Sprout always returns 480 Temporarily Unavailable. Could you please help to
check and share your advice? Below is my config and debug log on Sprout.
##clearwater configuration
root@ubun3:~# cat /etc/clearwater/config
# Deployment definitions
home_domain=example.com
bono_hostname=137.116.157.173
sprout_hostname=137.116.157.174
#chronos_hostname=137.116.157.174:7253
hs_hostname=137.116.157.176:8888
hs_provisioning_hostname=137.116.157.176:8889
ralf_hostname=137.116.157.177:10888
xdms_hostname=137.116.157.175:7888
# Local IP configuration
local_ip=137.116.157.174
public_ip=137.116.157.174
public_hostname=137.116.157.174
# Email server configuration
smtp_smarthost=127.0.0.1
smtp_username=username
smtp_password=password
[email protected]
# Keys
signup_key=secret
turn_workaround=secret
ellis_api_key=secret
ellis_cookie_key=secret
# I-CSCF/S-CSCF configuration
icscf=5052
scscf=5054
upstream_hostname=137.116.157.174
#ENUM
#enum_server=137.116.158.98
enum_file=enum.json
# Additional domains
#additional_home_domains=<domain 1>,<domain 2>,<domain 3>...
<truncated logs>
Thanks, Tam Vo
_______________________________________________
Clearwater mailing list
[email protected]
http://lists.projectclearwater.org/listinfo/clearwater
