Hi all,
With the local changes (see mail below) in function t_continue() (adding the handling of
REQUEST route), I introduced some side effects.
The handling of distinct PSIs does not work correctly with examples/scscf/kamailio.cfg,
because the function t_continue() deletes the transaction, although the route in the
config file added a UAC towards the AS.
Now, when the transaction is deleted erroneously, the S-CSCF does not any more answer with
ACK to the 503 from the AS. Also retransmissions of the INVITE to AS are NOT performed.
I did another correction and added a branch in the if() clause at the end of t_continue()
(see attached file t_suspend.c).
done:
UNLOCK_ASYNC_CONTINUE(t);
if (t->async_backup.backup_route == REQUEST_ROUTE){
if (t->nr_of_outgoings < (uac ? 2 : 1)){
/* unref the transaction */
t_unref(t->uas.request);
}
} else if (t->async_backup.backup_route != TM_ONREPLY_ROUTE){
Here the transaction is only deleted, if the REQUEST route in the config file did NOT add
an UAC.
I would be glad, if someone could confirm or reject, whether those changes would be in
line with kamailio’s architecture.
Should those changes be brought to github?
Please find as additional information some tshark traces and log file before (count 62)
the recent correction and after (count 63) the recent correction.
All the best
Christoph
From: sr-users [mailto:sr-users-bounces@lists.sip-router.org] On Behalf Of Valentin
Christoph
Sent: Thursday, September 22, 2016 3:33 PM
To: Kamailio (SER) - Users Mailing List
Cc: Onic Roman
Subject: Re: [SR-Users] Addressing a distinct PSI result is: 555 AS Contacting Failed -
iFC terminated dialog
Hi Carsten,
I had to update the file modules/tm/t_suspend.c (see attachment).
I did following change and hope I did not cause any side effects:
/* which route block type were we in when we were suspended */
cb_type = FAILURE_CB_TYPE;
switch (t->async_backup.backup_route) {
case REQUEST_ROUTE:
cb_type = REQUEST_CB_TYPE;
break;
case FAILURE_ROUTE:
cb_type = FAILURE_CB_TYPE;
break;
case TM_ONREPLY_ROUTE:
cb_type = ONREPLY_CB_TYPE;
break;
case BRANCH_ROUTE:
cb_type = BRANCH_CB_TYPE;
break;
}
Currently I have a local copy of latest 4.4 branch. I’m far away from bringing changes
back to github (need to learn a lot more, before actively cooperating).
Kind regards,
Christoph
From: sr-users [mailto:sr-users-bounces@lists.sip-router.org] On Behalf Of Carsten Bock
Sent: Thursday, September 22, 2016 3:22 PM
To: Kamailio (SER) - Users Mailing List
Cc: Onic Roman
Subject: Re: [SR-Users] Addressing a distinct PSI result is: 555 AS Contacting Failed -
iFC terminated dialog
Hi Valentin,
where was it?
Greeting from Hamburg,
Carsten
2016-09-22 14:58 GMT+02:00 Valentin Christoph
<Christoph.Valentin@kapsch.net<mailto:Christoph.Valentin@kapsch.net>>:
Hi all,
No further need to investigate.
I found the bug.
Thanks,
Christoph
From: sr-users
[mailto:sr-users-bounces@lists.sip-router.org<mailto:sr-users-bounces@lists.sip-router.org>]
On Behalf Of Valentin Christoph
Sent: Tuesday, September 20, 2016 12:13 PM
To: sr-users@lists.sip-router.org<mailto:sr-users@lists.sip-router.org>
Cc: Onic Roman
Subject: [SR-Users] Addressing a distinct PSI result is: 555 AS Contacting Failed - iFC
terminated dialog
Hi all,
I’m trying to send a call to an AS via a kamailio S-CSCF (release 4.4.3). I’m addressing
the AS by a distinct PSI: sip:04325432101@domain.net;user=gsmr.
At the first try the S-CSCF sends a SAR to HSS and receives a successful SAA (tshark
traces attached), but the S-CSCF rejects the call with 555 AS Contacting Failed - iFC
terminated dialog.
At the second try (a few seconds later), the S-CSCF doesn’t exchange SAR/SAA with the
HSS, and now the call is successfully forwarded to the AS.
This problem is permanent, it is not the result of a temporary loss of connectivity
between S-CSCF and AS.
I checked the iFCs that I had configured at the HSS and I think, they are OK.
I attached
- tshark traces from the node, where the S-CSCF resides:
2016_09_19_error_555_17_scscf_filtered.pcap
- WITH_DEBUG logs from kamailio: 2016_09_19_error_555_17_kamailio_1st_try.log
- A tarball of /usr/local/etc/kamailio: 2016_09_19_error_555_17_kamailio.tar.gz
Can anybody help? Is it a bug in kamailio or is the problem on my side?
Thanks,
Christoph
The information contained in this e-mail message is privileged and confidential and is for
the exclusive use of the addressee. The person who receives this message and who is not
the addressee, one of his employees or an agent entitled to hand it over to the addressee,
is informed that he may not use, disclose or reproduce the contents thereof, and is kindly
asked to notify the sender and delete the e-mail immediately.
The information contained in this e-mail message is privileged and confidential and is for
the exclusive use of the addressee. The person who receives this message and who is not
the addressee, one of his employees or an agent entitled to hand it over to the addressee,
is informed that he may not use, disclose or reproduce the contents thereof, and is kindly
asked to notify the sender and delete the e-mail immediately.
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org<mailto:sr-users@lists.sip-router.org>
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
--
Carsten Bock
CEO (Geschäftsführer)
ng-voice GmbH
Millerntorplatz 1
20359 Hamburg / Germany
http://www.ng-voice.com
mailto:carsten@ng-voice.com<mailto:carsten@ng-voice.com>
Office +49 40 5247593-40
Fax +49 40 5247593-99
Sitz der Gesellschaft: Hamburg
Registergericht: Amtsgericht Hamburg, HRB 120189
Geschäftsführer: Carsten Bock
Ust-ID: DE279344284
Hier finden Sie unsere handelsrechtlichen Pflichtangaben:
http://www.ng-voice.com/imprint/
The information contained in this e-mail message is privileged and confidential and is for
the exclusive use of the addressee. The person who receives this message and who is not
the addressee, one of his employees or an agent entitled to hand it over to the addressee,
is informed that he may not use, disclose or reproduce the contents thereof, and is kindly
asked to notify the sender and delete the e-mail immediately.
The information contained in this e-mail message is privileged and confidential and is for
the exclusive use of the addressee. The person who receives this message and who is not
the addressee, one of his employees or an agent entitled to hand it over to the addressee,
is informed that he may not use, disclose or reproduce the contents thereof, and is kindly
asked to notify the sender and delete the e-mail immediately.