20 Jan
2015
20 Jan
'15
2:13 p.m.
Trying to call a T.38 enabled endpoint B from an endpoint A that doesn't. This
results in a "488 Not Acceptable" from A.
The kamailio (4.0.3) in between with topoh enabled (with mask_callid set to 1.
Kamailio ACKs the 488 to A, but the ACK has the wrong (masked) Call-ID,
resulting in the ACK to A being ignored, A keeps sending 488 at intervals
before just dropping the call.
My understanding is the Call-ID in the ACK has to be the same as the Call-ID
from the 488. But instead of sending the unmasked Call-ID used in all other
messages between A and Kamailio, the ACK contains the masked Call-ID used in
all messagea between A and Kamailio.
I can't find a bug report relating to this. Is this a known feature or maybe
fixed in newer versions?
A->Kamailio
SIP/2.0 488 Not acceptable here.
Via: SIP/2.0/UDP
109.235.32.40;branch=z9hG4bKf91a.c6c88747.0;received=109.235.32.40.
Via: SIP/2.0/UDP 172.19.162.1;branch=pocos-
rS4MusXox1l5QHyNxRy6uAXsEOdsxidSEAktxGZKWgeKCgeS-
RrKEAy057Nl9DEpWpefZD6AhGtwWDJjEqeuEAZgZs5iZA7*.
From: <sip:+31880100799@sip.pocos.nl:5060>;tag=as3869fe2a.
To: "+31880100705" <sip:+31880100705@sip.pocos.nl>;tag=as1b0b8097.
Call-ID: 0b5946b977210450571f767a19cd6fa0(a)99sip.pocos.nl.
CSeq: 102 INVITE.
Kamailio<-A
ACK sip:+31880100705@109.235.32.48 SIP/2.0.
Via: SIP/2.0/UDP 109.235.32.40;branch=z9hG4bKf91a.c6c88747.0.
Max-Forwards: 16.
From: <sip:+31880100799@sip.pocos.nl:5060>;tag=as3869fe2a.
To: "+31880100705" <sip:+31880100705@sip.pocos.nl>;tag=as1b0b8097.
Call-ID: !!:xqXtWRMpZAngEsX3xGMtxGrgxDZgEA9JxR4AzGz8ZRIyWR4sh.yomqlACgxoC8K*.
CSeq: 102 ACK.
--
Telefoon: 088 0100 700
Sales: sales(a)pocos.nl | Service: servicedesk(a)pocos.nl
http://www.pocos.nl/ | Croy 9c, 5653 LC Eindhoven | Kamer van Koophandel
17097024
21 Jan
21 Jan
9:45 a.m.
To understand properly, this is after the re-INVITE from B to A? I will
look in the code as I get a chance, being out of the office for few days...
Cheers,
Daniel
On 20/01/15 13:13, Daniel Tryba wrote:
Trying to call a T.38 enabled endpoint B from an
endpoint A that doesn't. This
results in a "488 Not Acceptable" from A.
The kamailio (4.0.3) in between with topoh enabled (with mask_callid set to 1.
Kamailio ACKs the 488 to A, but the ACK has the wrong (masked) Call-ID,
resulting in the ACK to A being ignored, A keeps sending 488 at intervals
before just dropping the call.
My understanding is the Call-ID in the ACK has to be the same as the Call-ID
from the 488. But instead of sending the unmasked Call-ID used in all other
messages between A and Kamailio, the ACK contains the masked Call-ID used in
all messagea between A and Kamailio.
I can't find a bug report relating to this. Is this a known feature or maybe
fixed in newer versions?
A->Kamailio
SIP/2.0 488 Not acceptable here.
Via: SIP/2.0/UDP
109.235.32.40;branch=z9hG4bKf91a.c6c88747.0;received=109.235.32.40.
Via: SIP/2.0/UDP 172.19.162.1;branch=pocos-
rS4MusXox1l5QHyNxRy6uAXsEOdsxidSEAktxGZKWgeKCgeS-
RrKEAy057Nl9DEpWpefZD6AhGtwWDJjEqeuEAZgZs5iZA7*.
From: <sip:+31880100799@sip.pocos.nl:5060>;tag=as3869fe2a.
To: "+31880100705" <sip:+31880100705@sip.pocos.nl>;tag=as1b0b8097.
Call-ID: 0b5946b977210450571f767a19cd6fa0(a)99sip.pocos.nl.
CSeq: 102 INVITE.
Kamailio<-A
ACK sip:+31880100705@109.235.32.48 SIP/2.0.
Via: SIP/2.0/UDP 109.235.32.40;branch=z9hG4bKf91a.c6c88747.0.
Max-Forwards: 16.
From: <sip:+31880100799@sip.pocos.nl:5060>;tag=as3869fe2a.
To: "+31880100705" <sip:+31880100705@sip.pocos.nl>;tag=as1b0b8097.
Call-ID: !!:xqXtWRMpZAngEsX3xGMtxGrgxDZgEA9JxR4AzGz8ZRIyWR4sh.yomqlACgxoC8K*.
CSeq: 102 ACK.
--
Daniel-Constantin Mierla
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
1:12 p.m.
On Wednesday 21 January 2015 08:45:59 Daniel-Constantin Mierla wrote:
To understand properly, this is after the re-INVITE
from B to A? I will
look in the code as I get a chance, being out of the office for few days...
Yes. Full trace below. Only the ACK to SIP_A for the 488 has the wrong Call-
ID.
Disabling masking fixes the problem, but I need topoh with callerid masking to
enable an Avaya IP Office to make calls to itself via its external extensions.
There is no hurry, it appears have been broken for a long time, a few weeks
extra makes no difference to me :) I'll try a test server with a more recent
version to see if the problem was fixed since 4.0.3.
U SIP_A:5060 -> KAMAILIO:5060
INVITE sip:+31880100799@sip.pocos.nl:5060 SIP/2.0.
Via: SIP/2.0/UDP SIP_A:5060;branch=z9hG4bK396cd222;rport.
From: "+31880100705" <sip:+31880100705@sip.pocos.nl>;tag=as1b0b8097.
To: <sip:+31880100799@sip.pocos.nl:5060>.
Contact: <sip:+31880100705@sipA>.
Call-ID: 0b5946b977210450571f767a19cd6fa0(a)99sip.pocos.nl.
U KAMAILIO:5060 -> SIP_A:5060
SIP/2.0 100 trying -- your call is important to us.
Via: SIP/2.0/UDP SIP_A:5060;branch=z9hG4bK396cd222;rport=5060.
From: "+31880100705" <sip:+31880100705@sip.pocos.nl>;tag=as1b0b8097.
To: <sip:+31880100799@sip.pocos.nl:5060>.
Call-ID: 0b5946b977210450571f767a19cd6fa0(a)99sip.pocos.nl.
U KAMAILIO:5060 -> SIP_B:5060
INVITE sip:+31880100799@fax.pocos.nl SIP/2.0.
Record-Route: <sip:KAMAILIO;lr;ftag=as1b0b8097;did=fc2.c39>.
Via: SIP/2.0/UDP KAMAILIO;branch=z9hG4bK0a1a.d2ac1e03.0.
Via: SIP/2.0/UDP 172.19.162.1;branch=pocos-
rS4MusXox1l5QHyNxRy6uAXsEOdsxidSWGktxGZKWtQX-
DQV9Acim8HoZpNlaA4kQsQiOsx6E8EnxAXfWgeKCgeS-RrKEAy*.
From: "+31880100705" <sip:+31880100705@sip.pocos.nl>;tag=as1b0b8097.
To: <sip:+31880100799@sip.pocos.nl:5060>.
Contact: <sip:172.19.162.1;line=pcs-mp4KWiTsxRNdxG7KxGmKEry3xGnoxAxtuAxfuAMd>.
Call-ID: !!:xqXtWRMpZAngEsX3xGMtxGrgxDZgEA9JxR4AzGz8ZRIyWR4sh.yomqlACgxoC8K*.
U SIP_B:5060 -> KAMAILIO:5060
SIP/2.0 100 Trying.
Via: SIP/2.0/UDP KAMAILIO;branch=z9hG4bK0a1a.d2ac1e03.0;received=KAMAILIO.
Via: SIP/2.0/UDP 172.19.162.1;branch=pocos-
rS4MusXox1l5QHyNxRy6uAXsEOdsxidSWGktxGZKWtQX-
DQV9Acim8HoZpNlaA4kQsQiOsx6E8EnxAXfWgeKCgeS-RrKEAy*.
Record-Route: <sip:KAMAILIO;lr;ftag=as1b0b8097;did=fc2.c39>.
From: "+31880100705" <sip:+31880100705@sip.pocos.nl>;tag=as1b0b8097.
To: <sip:+31880100799@sip.pocos.nl:5060>.
Call-ID: !!:xqXtWRMpZAngEsX3xGMtxGrgxDZgEA9JxR4AzGz8ZRIyWR4sh.yomqlACgxoC8K*.
U SIP_B:5060 -> KAMAILIO:5060
SIP/2.0 180 Ringing.
Via: SIP/2.0/UDP KAMAILIO;branch=z9hG4bK0a1a.d2ac1e03.0;received=KAMAILIO.
Via: SIP/2.0/UDP 172.19.162.1;branch=pocos-
rS4MusXox1l5QHyNxRy6uAXsEOdsxidSWGktxGZKWtQX-
DQV9Acim8HoZpNlaA4kQsQiOsx6E8EnxAXfWgeK
CgeS-RrKEAy*.
Record-Route: <sip:KAMAILIO;lr;ftag=as1b0b8097;did=fc2.c39>.
From: "+31880100705" <sip:+31880100705@sip.pocos.nl>;tag=as1b0b8097.
To: <sip:+31880100799@sip.pocos.nl:5060>;tag=as3869fe2a.
Call-ID: !!:xqXtWRMpZAngEsX3xGMtxGrgxDZgEA9JxR4AzGz8ZRIyWR4sh.yomqlACgxoC8K*.
U KAMAILIO:5060 -> SIP_A:5060
SIP/2.0 180 Ringing.
Via: SIP/2.0/UDP SIP_A:5060;branch=z9hG4bK396cd222;rport=5060.
Record-Route: <sip:KAMAILIO;lr;ftag=as1b0b8097;did=fc2.c39>.
From: "+31880100705" <sip:+31880100705@sip.pocos.nl>;tag=as1b0b8097.
To: <sip:+31880100799@sip.pocos.nl:5060>;tag=as3869fe2a.
Call-ID: 0b5946b977210450571f767a19cd6fa0(a)99sip.pocos.nl.
U SIP_B:5060 -> KAMAILIO:5060
SIP/2.0 200 OK.
Via: SIP/2.0/UDP KAMAILIO;branch=z9hG4bK0a1a.d2ac1e03.0;received=KAMAILIO.
Via: SIP/2.0/UDP 172.19.162.1;branch=pocos-
rS4MusXox1l5QHyNxRy6uAXsEOdsxidSWGktxGZKWtQX-
DQV9Acim8HoZpNlaA4kQsQiOsx6E8EnxAXfWgeKCgeS-RrKEAy*.
Record-Route: <sip:KAMAILIO;lr;ftag=as1b0b8097;did=fc2.c39>.
From: "+31880100705" <sip:+31880100705@sip.pocos.nl>;tag=as1b0b8097.
To: <sip:+31880100799@sip.pocos.nl:5060>;tag=as3869fe2a.
Call-ID: !!:xqXtWRMpZAngEsX3xGMtxGrgxDZgEA9JxR4AzGz8ZRIyWR4sh.yomqlACgxoC8K*.
U KAMAILIO:5060 -> SIP_A:5060
SIP/2.0 200 OK.
Via: SIP/2.0/UDP SIP_A:5060;branch=z9hG4bK396cd222;rport=5060.
Record-Route: <sip:KAMAILIO;lr;ftag=as1b0b8097;did=fc2.c39>.
From: "+31880100705" <sip:+31880100705@sip.pocos.nl>;tag=as1b0b8097.
To: <sip:+31880100799@sip.pocos.nl:5060>;tag=as3869fe2a.
Call-ID: 0b5946b977210450571f767a19cd6fa0(a)99sip.pocos.nl.
U SIP_A:5060 -> KAMAILIO:5060
ACK sip:172.19.162.1;line=pcs-mp4KWiTsxRNdxG7KxGm6Wry3xGnoxAxtuAxfuAMpWArKEAy*
SIP/2.0.
Via: SIP/2.0/UDP SIP_A:5060;branch=z9hG4bK766d39a2;rport.
Route: <sip:KAMAILIO;lr;ftag=as1b0b8097;did=fc2.c39>.
From: "+31880100705" <sip:+31880100705@sip.pocos.nl>;tag=as1b0b8097.
To: <sip:+31880100799@sip.pocos.nl:5060>;tag=as3869fe2a.
Contact: <sip:+31880100705@sipA>.
Call-ID: 0b5946b977210450571f767a19cd6fa0(a)99sip.pocos.nl.
U KAMAILIO:5060 -> SIP_B:5060
ACK sip:+31880100799@SIP_B:5060 SIP/2.0.
Via: SIP/2.0/UDP KAMAILIO;branch=z9hG4bKcydzigwkX.
Via: SIP/2.0/UDP 172.19.162.1;branch=pocos-
rS4MusXox1l5QHyNxRy6uAXsEOdsxidSWGktxGZKWtQX-
DQA9Acim8HoZpNlaA4kQsQiOsmpE8MsWD7fWgeKCgeS-RrKEAy*.
From: "+31880100705" <sip:+31880100705@sip.pocos.nl>;tag=as1b0b8097.
To: <sip:+31880100799@sip.pocos.nl:5060>;tag=as3869fe2a.
Contact: <sip:172.19.162.1;line=pcs-mp4KWiTsxRNdxG7KxGmKEry3xGnoxAxtuAxfuAMd>.
Call-ID: !!:xqXtWRMpZAngEsX3xGMtxGrgxDZgEA9JxR4AzGz8ZRIyWR4sh.yomqlACgxoC8K*.
U SIP_B:5060 -> KAMAILIO:5060
INVITE sip:172.19.162.1;line=pcs-mp4KWiTsxRNdxG7KxGmKEry3xGnoxAxtuAxfuAMd
SIP/2.0.
Via: SIP/2.0/UDP SIP_B:5060;branch=z9hG4bK667c5bb1.
Route: <sip:KAMAILIO;lr;ftag=as1b0b8097;did=fc2.c39>.
Max-Forwards: 70.
From: <sip:+31880100799@sip.pocos.nl:5060>;tag=as3869fe2a.
To: "+31880100705" <sip:+31880100705@sip.pocos.nl>;tag=as1b0b8097.
Contact: <sip:+31880100799@SIP_B:5060>.
Call-ID: !!:xqXtWRMpZAngEsX3xGMtxGrgxDZgEA9JxR4AzGz8ZRIyWR4sh.yomqlACgxoC8K*.
U KAMAILIO:5060 -> SIP_B:5060
SIP/2.0 100 trying -- your call is important to us.
Via: SIP/2.0/UDP SIP_B:5060;branch=z9hG4bK667c5bb1;rport=5060.
From: <sip:+31880100799@sip.pocos.nl:5060>;tag=as3869fe2a.
To: "+31880100705" <sip:+31880100705@sip.pocos.nl>;tag=as1b0b8097.
Call-ID: !!:xqXtWRMpZAngEsX3xGMtxGrgxDZgEA9JxR4AzGz8ZRIyWR4sh.yomqlACgxoC8K*.
U KAMAILIO:5060 -> SIP_A:5060
INVITE sip:+31880100705@sipA SIP/2.0.
Via: SIP/2.0/UDP KAMAILIO;branch=z9hG4bKf91a.c6c88747.0.
Via: SIP/2.0/UDP 172.19.162.1;branch=pocos-
rS4MusXox1l5QHyNxRy6uAXsEOdsxidSEAktxGZKWgeKCgeS-
RrKEAy057Nl9DEpWpefZD6AhGtwWDJjEqeuEAZgZs5iZA7*.
Max-Forwards: 16.
From: <sip:+31880100799@sip.pocos.nl:5060>;tag=as3869fe2a.
To: "+31880100705" <sip:+31880100705@sip.pocos.nl>;tag=as1b0b8097.
Contact: <sip:172.19.162.1;line=pcs-
mp4KWiTsxRNdxG7KxGm6Wry3xGnoxAxtuAxfuAMpWArKEAy*>.
Call-ID: 0b5946b977210450571f767a19cd6fa0(a)99sip.pocos.nl.
U SIP_A:5060 -> KAMAILIO:5060
SIP/2.0 488 Not acceptable here.
Via: SIP/2.0/UDP KAMAILIO;branch=z9hG4bKf91a.c6c88747.0;received=KAMAILIO.
Via: SIP/2.0/UDP 172.19.162.1;branch=pocos-
rS4MusXox1l5QHyNxRy6uAXsEOdsxidSEAktxGZKWgeKCgeS-
RrKEAy057Nl9DEpWpefZD6AhGtwWDJjEqeuEAZgZs5iZA7*.
From: <sip:+31880100799@sip.pocos.nl:5060>;tag=as3869fe2a.
To: "+31880100705" <sip:+31880100705@sip.pocos.nl>;tag=as1b0b8097.
Call-ID: 0b5946b977210450571f767a19cd6fa0(a)99sip.pocos.nl.
U KAMAILIO:5060 -> SIP_A:5060
ACK sip:+31880100705@sipA SIP/2.0.
Via: SIP/2.0/UDP KAMAILIO;branch=z9hG4bKf91a.c6c88747.0.
Max-Forwards: 16.
From: <sip:+31880100799@sip.pocos.nl:5060>;tag=as3869fe2a.
To: "+31880100705" <sip:+31880100705@sip.pocos.nl>;tag=as1b0b8097.
Call-ID: !!:xqXtWRMpZAngEsX3xGMtxGrgxDZgEA9JxR4AzGz8ZRIyWR4sh.yomqlACgxoC8K*.
U KAMAILIO:5060 -> SIP_B:5060
SIP/2.0 488 Not acceptable here.
Via: SIP/2.0/UDP SIP_B:5060;rport=5060;branch=z9hG4bK667c5bb1.
From: <sip:+31880100799@sip.pocos.nl:5060>;tag=as3869fe2a.
To: "+31880100705" <sip:+31880100705@sip.pocos.nl>;tag=as1b0b8097.
Call-ID: !!:xqXtWRMpZAngEsX3xGMtxGrgxDZgEA9JxR4AzGz8ZRIyWR4sh.yomqlACgxoC8K*.
U SIP_B:5060 -> KAMAILIO:5060
ACK sip:172.19.162.1;line=pcs-mp4KWiTsxRNdxG7KxGmKEry3xGnoxAxtuAxfuAMd
SIP/2.0.
Via: SIP/2.0/UDP SIP_B:5060;branch=z9hG4bK667c5bb1.
Route: <sip:KAMAILIO;lr;ftag=as1b0b8097;did=fc2.c39>.
Max-Forwards: 70.
From: <sip:+31880100799@sip.pocos.nl:5060>;tag=as3869fe2a.
To: "+31880100705" <sip:+31880100705@sip.pocos.nl>;tag=as1b0b8097.
Contact: <sip:+31880100799@SIP_B:5060>.
Call-ID: !!:xqXtWRMpZAngEsX3xGMtxGrgxDZgEA9JxR4AzGz8ZRIyWR4sh.yomqlACgxoC8K*.
U SIP_B:5060 -> KAMAILIO:5060
INVITE sip:172.19.162.1;line=pcs-mp4KWiTsxRNdxG7KxGmKEry3xGnoxAxtuAxfuAMd
SIP/2.0.
Via: SIP/2.0/UDP SIP_B:5060;branch=z9hG4bK2f3d85eb.
Route: <sip:KAMAILIO;lr;ftag=as1b0b8097;did=fc2.c39>.
Max-Forwards: 70.
From: <sip:+31880100799@sip.pocos.nl:5060>;tag=as3869fe2a.
To: "+31880100705" <sip:+31880100705@sip.pocos.nl>;tag=as1b0b8097.
Contact: <sip:+31880100799@SIP_B:5060>.
Call-ID: !!:xqXtWRMpZAngEsX3xGMtxGrgxDZgEA9JxR4AzGz8ZRIyWR4sh.yomqlACgxoC8K*.
U KAMAILIO:5060 -> SIP_B:5060
SIP/2.0 100 trying -- your call is important to us.
Via: SIP/2.0/UDP SIP_B:5060;branch=z9hG4bK2f3d85eb;rport=5060.
From: <sip:+31880100799@sip.pocos.nl:5060>;tag=as3869fe2a.
To: "+31880100705" <sip:+31880100705@sip.pocos.nl>;tag=as1b0b8097.
Call-ID: !!:xqXtWRMpZAngEsX3xGMtxGrgxDZgEA9JxR4AzGz8ZRIyWR4sh.yomqlACgxoC8K*.
U KAMAILIO:5060 -> SIP_A:5060
INVITE sip:+31880100705@sipA SIP/2.0.
Via: SIP/2.0/UDP KAMAILIO;branch=z9hG4bK0a1a.e2ac1e03.0.
Via: SIP/2.0/UDP 172.19.162.1;branch=pocos-
rS4MusXox1l5QHyNxRy6uAXsEOdsxidSEAktxGZKWgeKCgeS-
RrKEAy057Nl9DEpWpefZD6AhGtwWDJjEqeux8ZszGNtzDX*.
Max-Forwards: 16.
From: <sip:+31880100799@sip.pocos.nl:5060>;tag=as3869fe2a.
To: "+31880100705" <sip:+31880100705@sip.pocos.nl>;tag=as1b0b8097.
Contact: <sip:172.19.162.1;line=pcs-
mp4KWiTsxRNdxG7KxGm6Wry3xGnoxAxtuAxfuAMpWArKEAy*>.
Call-ID: 0b5946b977210450571f767a19cd6fa0(a)99sip.pocos.nl.
U SIP_A:5060 -> KAMAILIO:5060
SIP/2.0 491 Request Pending.
Via: SIP/2.0/UDP KAMAILIO;branch=z9hG4bK0a1a.e2ac1e03.0;received=KAMAILIO.
Via: SIP/2.0/UDP 172.19.162.1;branch=pocos-
rS4MusXox1l5QHyNxRy6uAXsEOdsxidSEAktxGZKWgeKCgeS-
RrKEAy057Nl9DEpWpefZD6AhGtwWDJjEqeux8ZszGNtzDX*.
From: <sip:+31880100799@sip.pocos.nl:5060>;tag=as3869fe2a.
To: "+31880100705" <sip:+31880100705@sip.pocos.nl>;tag=as1b0b8097.
Call-ID: 0b5946b977210450571f767a19cd6fa0(a)99sip.pocos.nl.
--
Telefoon: 088 0100 700
Sales: sales(a)pocos.nl | Service: servicedesk(a)pocos.nl
http://www.pocos.nl/ | Croy 9c, 5653 LC Eindhoven | Kamer van Koophandel
17097024
22 Jan
22 Jan
12:52 a.m.
It is an ACK for a negative response, therefore it is hop-by-hop
(received and discared by kamailio, then a new one is generated to the
next hop). The information of direction which was detected with Route
header ftag cannot be done in this case. I will try to figure out how
can be solved...
Cheers,
Daniel
On 21/01/15 12:12, Daniel Tryba wrote:
On Wednesday 21 January 2015 08:45:59
Daniel-Constantin Mierla wrote:
--
Daniel-Constantin Mierla
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
To understand properly, this is after the
re-INVITE from B to A? I will
look in the code as I get a chance, being out of the office for few days...
Yes.
Full trace below. Only the ACK to SIP_A for the 488 has the wrong Call-
ID.
Disabling masking fixes the problem, but I need topoh with callerid masking to
enable an Avaya IP Office to make calls to itself via its external extensions.
There is no hurry, it appears have been broken for a long time, a few weeks
extra makes no difference to me :) I'll try a test server with a more recent
version to see if the problem was fixed since 4.0.3.
U SIP_A:5060 -> KAMAILIO:5060
INVITE sip:+31880100799@sip.pocos.nl:5060 SIP/2.0.
Via: SIP/2.0/UDP SIP_A:5060;branch=z9hG4bK396cd222;rport.
From: "+31880100705" <sip:+31880100705@sip.pocos.nl>;tag=as1b0b8097.
To: <sip:+31880100799@sip.pocos.nl:5060>.
Contact: <sip:+31880100705@sipA>.
Call-ID: 0b5946b977210450571f767a19cd6fa0(a)99sip.pocos.nl.
U KAMAILIO:5060 -> SIP_A:5060
SIP/2.0 100 trying -- your call is important to us.
Via: SIP/2.0/UDP SIP_A:5060;branch=z9hG4bK396cd222;rport=5060.
From: "+31880100705" <sip:+31880100705@sip.pocos.nl>;tag=as1b0b8097.
To: <sip:+31880100799@sip.pocos.nl:5060>.
Call-ID: 0b5946b977210450571f767a19cd6fa0(a)99sip.pocos.nl.
U KAMAILIO:5060 -> SIP_B:5060
INVITE sip:+31880100799@fax.pocos.nl SIP/2.0.
Record-Route: <sip:KAMAILIO;lr;ftag=as1b0b8097;did=fc2.c39>.
Via: SIP/2.0/UDP KAMAILIO;branch=z9hG4bK0a1a.d2ac1e03.0.
Via: SIP/2.0/UDP 172.19.162.1;branch=pocos-
rS4MusXox1l5QHyNxRy6uAXsEOdsxidSWGktxGZKWtQX-
DQV9Acim8HoZpNlaA4kQsQiOsx6E8EnxAXfWgeKCgeS-RrKEAy*.
From: "+31880100705" <sip:+31880100705@sip.pocos.nl>;tag=as1b0b8097.
To: <sip:+31880100799@sip.pocos.nl:5060>.
Contact: <sip:172.19.162.1;line=pcs-mp4KWiTsxRNdxG7KxGmKEry3xGnoxAxtuAxfuAMd>.
Call-ID: !!:xqXtWRMpZAngEsX3xGMtxGrgxDZgEA9JxR4AzGz8ZRIyWR4sh.yomqlACgxoC8K*.
U SIP_B:5060 -> KAMAILIO:5060
SIP/2.0 100 Trying.
Via: SIP/2.0/UDP KAMAILIO;branch=z9hG4bK0a1a.d2ac1e03.0;received=KAMAILIO.
Via: SIP/2.0/UDP 172.19.162.1;branch=pocos-
rS4MusXox1l5QHyNxRy6uAXsEOdsxidSWGktxGZKWtQX-
DQV9Acim8HoZpNlaA4kQsQiOsx6E8EnxAXfWgeKCgeS-RrKEAy*.
Record-Route: <sip:KAMAILIO;lr;ftag=as1b0b8097;did=fc2.c39>.
From: "+31880100705" <sip:+31880100705@sip.pocos.nl>;tag=as1b0b8097.
To: <sip:+31880100799@sip.pocos.nl:5060>.
Call-ID: !!:xqXtWRMpZAngEsX3xGMtxGrgxDZgEA9JxR4AzGz8ZRIyWR4sh.yomqlACgxoC8K*.
U SIP_B:5060 -> KAMAILIO:5060
SIP/2.0 180 Ringing.
Via: SIP/2.0/UDP KAMAILIO;branch=z9hG4bK0a1a.d2ac1e03.0;received=KAMAILIO.
Via: SIP/2.0/UDP 172.19.162.1;branch=pocos-
rS4MusXox1l5QHyNxRy6uAXsEOdsxidSWGktxGZKWtQX-
DQV9Acim8HoZpNlaA4kQsQiOsx6E8EnxAXfWgeK
CgeS-RrKEAy*.
Record-Route: <sip:KAMAILIO;lr;ftag=as1b0b8097;did=fc2.c39>.
From: "+31880100705" <sip:+31880100705@sip.pocos.nl>;tag=as1b0b8097.
To: <sip:+31880100799@sip.pocos.nl:5060>;tag=as3869fe2a.
Call-ID: !!:xqXtWRMpZAngEsX3xGMtxGrgxDZgEA9JxR4AzGz8ZRIyWR4sh.yomqlACgxoC8K*.
U KAMAILIO:5060 -> SIP_A:5060
SIP/2.0 180 Ringing.
Via: SIP/2.0/UDP SIP_A:5060;branch=z9hG4bK396cd222;rport=5060.
Record-Route: <sip:KAMAILIO;lr;ftag=as1b0b8097;did=fc2.c39>.
From: "+31880100705" <sip:+31880100705@sip.pocos.nl>;tag=as1b0b8097.
To: <sip:+31880100799@sip.pocos.nl:5060>;tag=as3869fe2a.
Call-ID: 0b5946b977210450571f767a19cd6fa0(a)99sip.pocos.nl.
U SIP_B:5060 -> KAMAILIO:5060
SIP/2.0 200 OK.
Via: SIP/2.0/UDP KAMAILIO;branch=z9hG4bK0a1a.d2ac1e03.0;received=KAMAILIO.
Via: SIP/2.0/UDP 172.19.162.1;branch=pocos-
rS4MusXox1l5QHyNxRy6uAXsEOdsxidSWGktxGZKWtQX-
DQV9Acim8HoZpNlaA4kQsQiOsx6E8EnxAXfWgeKCgeS-RrKEAy*.
Record-Route: <sip:KAMAILIO;lr;ftag=as1b0b8097;did=fc2.c39>.
From: "+31880100705" <sip:+31880100705@sip.pocos.nl>;tag=as1b0b8097.
To: <sip:+31880100799@sip.pocos.nl:5060>;tag=as3869fe2a.
Call-ID: !!:xqXtWRMpZAngEsX3xGMtxGrgxDZgEA9JxR4AzGz8ZRIyWR4sh.yomqlACgxoC8K*.
U KAMAILIO:5060 -> SIP_A:5060
SIP/2.0 200 OK.
Via: SIP/2.0/UDP SIP_A:5060;branch=z9hG4bK396cd222;rport=5060.
Record-Route: <sip:KAMAILIO;lr;ftag=as1b0b8097;did=fc2.c39>.
From: "+31880100705" <sip:+31880100705@sip.pocos.nl>;tag=as1b0b8097.
To: <sip:+31880100799@sip.pocos.nl:5060>;tag=as3869fe2a.
Call-ID: 0b5946b977210450571f767a19cd6fa0(a)99sip.pocos.nl.
U SIP_A:5060 -> KAMAILIO:5060
ACK sip:172.19.162.1;line=pcs-mp4KWiTsxRNdxG7KxGm6Wry3xGnoxAxtuAxfuAMpWArKEAy*
SIP/2.0.
Via: SIP/2.0/UDP SIP_A:5060;branch=z9hG4bK766d39a2;rport.
Route: <sip:KAMAILIO;lr;ftag=as1b0b8097;did=fc2.c39>.
From: "+31880100705" <sip:+31880100705@sip.pocos.nl>;tag=as1b0b8097.
To: <sip:+31880100799@sip.pocos.nl:5060>;tag=as3869fe2a.
Contact: <sip:+31880100705@sipA>.
Call-ID: 0b5946b977210450571f767a19cd6fa0(a)99sip.pocos.nl.
U KAMAILIO:5060 -> SIP_B:5060
ACK sip:+31880100799@SIP_B:5060 SIP/2.0.
Via: SIP/2.0/UDP KAMAILIO;branch=z9hG4bKcydzigwkX.
Via: SIP/2.0/UDP 172.19.162.1;branch=pocos-
rS4MusXox1l5QHyNxRy6uAXsEOdsxidSWGktxGZKWtQX-
DQA9Acim8HoZpNlaA4kQsQiOsmpE8MsWD7fWgeKCgeS-RrKEAy*.
From: "+31880100705" <sip:+31880100705@sip.pocos.nl>;tag=as1b0b8097.
To: <sip:+31880100799@sip.pocos.nl:5060>;tag=as3869fe2a.
Contact: <sip:172.19.162.1;line=pcs-mp4KWiTsxRNdxG7KxGmKEry3xGnoxAxtuAxfuAMd>.
Call-ID: !!:xqXtWRMpZAngEsX3xGMtxGrgxDZgEA9JxR4AzGz8ZRIyWR4sh.yomqlACgxoC8K*.
U SIP_B:5060 -> KAMAILIO:5060
INVITE sip:172.19.162.1;line=pcs-mp4KWiTsxRNdxG7KxGmKEry3xGnoxAxtuAxfuAMd
SIP/2.0.
Via: SIP/2.0/UDP SIP_B:5060;branch=z9hG4bK667c5bb1.
Route: <sip:KAMAILIO;lr;ftag=as1b0b8097;did=fc2.c39>.
Max-Forwards: 70.
From: <sip:+31880100799@sip.pocos.nl:5060>;tag=as3869fe2a.
To: "+31880100705" <sip:+31880100705@sip.pocos.nl>;tag=as1b0b8097.
Contact: <sip:+31880100799@SIP_B:5060>.
Call-ID: !!:xqXtWRMpZAngEsX3xGMtxGrgxDZgEA9JxR4AzGz8ZRIyWR4sh.yomqlACgxoC8K*.
U KAMAILIO:5060 -> SIP_B:5060
SIP/2.0 100 trying -- your call is important to us.
Via: SIP/2.0/UDP SIP_B:5060;branch=z9hG4bK667c5bb1;rport=5060.
From: <sip:+31880100799@sip.pocos.nl:5060>;tag=as3869fe2a.
To: "+31880100705" <sip:+31880100705@sip.pocos.nl>;tag=as1b0b8097.
Call-ID: !!:xqXtWRMpZAngEsX3xGMtxGrgxDZgEA9JxR4AzGz8ZRIyWR4sh.yomqlACgxoC8K*.
U KAMAILIO:5060 -> SIP_A:5060
INVITE sip:+31880100705@sipA SIP/2.0.
Via: SIP/2.0/UDP KAMAILIO;branch=z9hG4bKf91a.c6c88747.0.
Via: SIP/2.0/UDP 172.19.162.1;branch=pocos-
rS4MusXox1l5QHyNxRy6uAXsEOdsxidSEAktxGZKWgeKCgeS-
RrKEAy057Nl9DEpWpefZD6AhGtwWDJjEqeuEAZgZs5iZA7*.
Max-Forwards: 16.
From: <sip:+31880100799@sip.pocos.nl:5060>;tag=as3869fe2a.
To: "+31880100705" <sip:+31880100705@sip.pocos.nl>;tag=as1b0b8097.
Contact: <sip:172.19.162.1;line=pcs-
mp4KWiTsxRNdxG7KxGm6Wry3xGnoxAxtuAxfuAMpWArKEAy*>.
Call-ID: 0b5946b977210450571f767a19cd6fa0(a)99sip.pocos.nl.
U SIP_A:5060 -> KAMAILIO:5060
SIP/2.0 488 Not acceptable here.
Via: SIP/2.0/UDP KAMAILIO;branch=z9hG4bKf91a.c6c88747.0;received=KAMAILIO.
Via: SIP/2.0/UDP 172.19.162.1;branch=pocos-
rS4MusXox1l5QHyNxRy6uAXsEOdsxidSEAktxGZKWgeKCgeS-
RrKEAy057Nl9DEpWpefZD6AhGtwWDJjEqeuEAZgZs5iZA7*.
From: <sip:+31880100799@sip.pocos.nl:5060>;tag=as3869fe2a.
To: "+31880100705" <sip:+31880100705@sip.pocos.nl>;tag=as1b0b8097.
Call-ID: 0b5946b977210450571f767a19cd6fa0(a)99sip.pocos.nl.
U KAMAILIO:5060 -> SIP_A:5060
ACK sip:+31880100705@sipA SIP/2.0.
Via: SIP/2.0/UDP KAMAILIO;branch=z9hG4bKf91a.c6c88747.0.
Max-Forwards: 16.
From: <sip:+31880100799@sip.pocos.nl:5060>;tag=as3869fe2a.
To: "+31880100705" <sip:+31880100705@sip.pocos.nl>;tag=as1b0b8097.
Call-ID: !!:xqXtWRMpZAngEsX3xGMtxGrgxDZgEA9JxR4AzGz8ZRIyWR4sh.yomqlACgxoC8K*.
U KAMAILIO:5060 -> SIP_B:5060
SIP/2.0 488 Not acceptable here.
Via: SIP/2.0/UDP SIP_B:5060;rport=5060;branch=z9hG4bK667c5bb1.
From: <sip:+31880100799@sip.pocos.nl:5060>;tag=as3869fe2a.
To: "+31880100705" <sip:+31880100705@sip.pocos.nl>;tag=as1b0b8097.
Call-ID: !!:xqXtWRMpZAngEsX3xGMtxGrgxDZgEA9JxR4AzGz8ZRIyWR4sh.yomqlACgxoC8K*.
U SIP_B:5060 -> KAMAILIO:5060
ACK sip:172.19.162.1;line=pcs-mp4KWiTsxRNdxG7KxGmKEry3xGnoxAxtuAxfuAMd
SIP/2.0.
Via: SIP/2.0/UDP SIP_B:5060;branch=z9hG4bK667c5bb1.
Route: <sip:KAMAILIO;lr;ftag=as1b0b8097;did=fc2.c39>.
Max-Forwards: 70.
From: <sip:+31880100799@sip.pocos.nl:5060>;tag=as3869fe2a.
To: "+31880100705" <sip:+31880100705@sip.pocos.nl>;tag=as1b0b8097.
Contact: <sip:+31880100799@SIP_B:5060>.
Call-ID: !!:xqXtWRMpZAngEsX3xGMtxGrgxDZgEA9JxR4AzGz8ZRIyWR4sh.yomqlACgxoC8K*.
U SIP_B:5060 -> KAMAILIO:5060
INVITE sip:172.19.162.1;line=pcs-mp4KWiTsxRNdxG7KxGmKEry3xGnoxAxtuAxfuAMd
SIP/2.0.
Via: SIP/2.0/UDP SIP_B:5060;branch=z9hG4bK2f3d85eb.
Route: <sip:KAMAILIO;lr;ftag=as1b0b8097;did=fc2.c39>.
Max-Forwards: 70.
From: <sip:+31880100799@sip.pocos.nl:5060>;tag=as3869fe2a.
To: "+31880100705" <sip:+31880100705@sip.pocos.nl>;tag=as1b0b8097.
Contact: <sip:+31880100799@SIP_B:5060>.
Call-ID: !!:xqXtWRMpZAngEsX3xGMtxGrgxDZgEA9JxR4AzGz8ZRIyWR4sh.yomqlACgxoC8K*.
U KAMAILIO:5060 -> SIP_B:5060
SIP/2.0 100 trying -- your call is important to us.
Via: SIP/2.0/UDP SIP_B:5060;branch=z9hG4bK2f3d85eb;rport=5060.
From: <sip:+31880100799@sip.pocos.nl:5060>;tag=as3869fe2a.
To: "+31880100705" <sip:+31880100705@sip.pocos.nl>;tag=as1b0b8097.
Call-ID: !!:xqXtWRMpZAngEsX3xGMtxGrgxDZgEA9JxR4AzGz8ZRIyWR4sh.yomqlACgxoC8K*.
U KAMAILIO:5060 -> SIP_A:5060
INVITE sip:+31880100705@sipA SIP/2.0.
Via: SIP/2.0/UDP KAMAILIO;branch=z9hG4bK0a1a.e2ac1e03.0.
Via: SIP/2.0/UDP 172.19.162.1;branch=pocos-
rS4MusXox1l5QHyNxRy6uAXsEOdsxidSEAktxGZKWgeKCgeS-
RrKEAy057Nl9DEpWpefZD6AhGtwWDJjEqeux8ZszGNtzDX*.
Max-Forwards: 16.
From: <sip:+31880100799@sip.pocos.nl:5060>;tag=as3869fe2a.
To: "+31880100705" <sip:+31880100705@sip.pocos.nl>;tag=as1b0b8097.
Contact: <sip:172.19.162.1;line=pcs-
mp4KWiTsxRNdxG7KxGm6Wry3xGnoxAxtuAxfuAMpWArKEAy*>.
Call-ID: 0b5946b977210450571f767a19cd6fa0(a)99sip.pocos.nl.
U SIP_A:5060 -> KAMAILIO:5060
SIP/2.0 491 Request Pending.
Via: SIP/2.0/UDP KAMAILIO;branch=z9hG4bK0a1a.e2ac1e03.0;received=KAMAILIO.
Via: SIP/2.0/UDP 172.19.162.1;branch=pocos-
rS4MusXox1l5QHyNxRy6uAXsEOdsxidSEAktxGZKWgeKCgeS-
RrKEAy057Nl9DEpWpefZD6AhGtwWDJjEqeux8ZszGNtzDX*.
From: <sip:+31880100799@sip.pocos.nl:5060>;tag=as3869fe2a.
To: "+31880100705" <sip:+31880100705@sip.pocos.nl>;tag=as1b0b8097.
Call-ID: 0b5946b977210450571f767a19cd6fa0(a)99sip.pocos.nl.
11:05 a.m.
On Wednesday 21 January 2015 23:52:46 Daniel-Constantin Mierla wrote:
It is an ACK for a negative response, therefore it is
hop-by-hop
(received and discared by kamailio, then a new one is generated to the
next hop). The information of direction which was detected with Route
header ftag cannot be done in this case. I will try to figure out how
can be solved...
Am I to naive to think that these ACKs to negatives always (callid masking and
whether topoh is active or not) need to use the Call-ID from the negative (in
this case 488) response? Call-ID has only to be rewritten in forwarding the
negative response towards the endpoint that triggered it (which is done
correctly in my call trace)
--
Telefoon: 088 0100 700
Sales: sales(a)pocos.nl | Service: servicedesk(a)pocos.nl
http://www.pocos.nl/ | Croy 9c, 5653 LC Eindhoven | Kamer van Koophandel
17097024
27 Jan
27 Jan
12:24 p.m.
Am I to naive to think that these ACKs to negatives
always (callid masking
and whether topoh is active or not) need to use the Call-ID from the
negative (in this case 488) response? Call-ID has only to be rewritten in
forwarding the negative response towards the endpoint that triggered it
(which is done correctly in my call trace)
Attached is a diff to topoh_mod.c that implements above (with my limited
knowledge). Locally generated ACKs don't get masked Call-IDs to downstream.
Works for my 488, will test some more to see if nothing else is broken. But
maybe somebody more in touch with kamailio source code could take a look to
see it this patch looks alright?
--
Telefoon: 088 0100 700
Sales: sales(a)pocos.nl | Service: servicedesk(a)pocos.nl
http://www.pocos.nl/ | Croy 9c, 5653 LC Eindhoven | Kamer van Koophandel
17097024
6:40 p.m.
On Tuesday 27 January 2015 11:24:59 Daniel Tryba wrote:
Works for my 488, will test some more to see if
nothing else is broken.
I was a bit optimistic, patch breaks if the called endpoint responds with a
4xx :(
--
Telefoon: 088 0100 700
Sales: sales(a)pocos.nl | Service: servicedesk(a)pocos.nl
http://www.pocos.nl/ | Croy 9c, 5653 LC Eindhoven | Kamer van Koophandel
17097024
28 Jan
28 Jan
2:52 p.m.
On 27/01/15 17:40, Daniel Tryba wrote:
On Tuesday 27 January 2015 11:24:59 Daniel Tryba
wrote:
One solution I thought of is to propagate the direction via topoh
'cookie' header, as it is done by the dialog module for the local
generated BYE. Tm code needs to be changed, but I haven't found the time
for it yet.
Being an hob-by-hop ack for a within dialog request, there is no info
that can be used to determine the direction. Topoh hooks are in the
core, after the new sip message is printed, with no relation to
transaction (or in this case, the reply).
Cheers,
Daniel
--
Daniel-Constantin Mierla
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Works for my 488, will test some more to see if
nothing else is broken.
I was a bit optimistic, patch breaks if the called endpoint
responds with a
4xx :(
23 Apr
23 Apr
7:26 p.m.
On Wednesday 28 January 2015 13:52:26 Daniel-Constantin Mierla wrote:
One solution I thought of is to propagate the
direction via topoh
'cookie' header, as it is done by the dialog module for the local
generated BYE. Tm code needs to be changed, but I haven't found the time
for it yet.
Being an hob-by-hop ack for a within dialog request, there is no info
that can be used to determine the direction. Topoh hooks are in the
core, after the new sip message is printed, with no relation to
transaction (or in this case, the reply).
I also found a similar flaw with reINVITEs due to session timers in 4.2.4
A new random callid gets generated and sent to an endpoint, which reacts with
a 481.
109.235.34.226 contain the endpoints
109.235.32.240 is a loadbalancer
109.235.32.243 is the sipserver doing the topoh stuff
--
Telefoon: 088 0100 700
Sales: sales(a)pocos.nl | Service: servicedesk(a)pocos.nl
http://www.pocos.nl/ | Croy 9c, 5653 LC Eindhoven | Kamer van Koophandel
17097024
25 Mar
25 Mar
6 p.m.
New subject: X-RTP-Statistics interpret ?
Hello,
I added code to include insertion of "X-RTP-Statistics" header into the BYE
message. I do see some numbers in it but I have no clue what they mean ? Any pointers ? Is
it defined somewhere. I searched a lot and could not find any info.
X-RTP-Statistics: 60 359 435 794 0
thank you very much
Sharath
6:37 p.m.
New subject: X-RTP-Statistics interpret ?
On Wednesday 25 March 2015 16:00:18 Sharath Kumar wrote:
I added code to include insertion of
"X-RTP-Statistics" header into the BYE
message. I do see some numbers in it but I have no clue what they mean ?
Any pointers ? Is it defined somewhere. I searched a lot and could not find
any info.
My conclusion is here:
http://lists.sip-router.org/pipermail/sr-users/2014-September/084666.html
--
Telefoon: 088 0100 700
Sales: sales(a)pocos.nl | Service: servicedesk(a)pocos.nl
http://www.pocos.nl/ | Croy 9c, 5653 LC Eindhoven | Kamer van Koophandel
17097024
7:33 p.m.
New subject: X-RTP-Statistics interpret ?
Thank you Daniel!!
-----Original Message-----
From: sr-users [mailto:sr-users-bounces@lists.sip-router.org] On Behalf Of Daniel Tryba
Sent: Wednesday, March 25, 2015 12:37 PM
To: sr-users(a)lists.sip-router.org
Subject: Re: [SR-Users] X-RTP-Statistics interpret ?
On Wednesday 25 March 2015 16:00:18 Sharath Kumar wrote:
I added code to include insertion of
"X-RTP-Statistics" header into
the BYE message. I do see some numbers in it but I have no clue what they mean ?
Any pointers ? Is it defined somewhere. I searched a lot and could not
find any info.
My conclusion is here:
http://lists.sip-router.org/pipermail/sr-users/2014-September/084666.html
--
Telefoon: 088 0100 700
Sales: sales(a)pocos.nl | Service: servicedesk(a)pocos.nl http://www.pocos.nl/ | Croy 9c, 5653
LC Eindhoven | Kamer van Koophandel
17097024
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
3501
days inactive
3594
days old
11 comments
3 participants
participants (3)
-
Daniel Tryba -
Daniel-Constantin Mierla -
Sharath Kumar