On 21 Jan 2015 23:00, "Johan Pascal" <
address@hidden> wrote:
Hi Kevin,
it's not the same error now, but there is still a strange thing in your SDP 200 Ok, the media port (m line audio) is set to 0 which doesn't seem very good.
johan
On 21/01/15 16:07, kevin barnard wrote:
Hello
Thanks for the quick reply !
>>The [] around the IPV6 address are not valid on the c line.
sorry, I had thought I had removed that ( should not have been present
in a later call )
I have ran again, and captured both Linphone log and pcap from
originating system ( Linux running Linphone which sends the invite ) and
the destination system , where I don't think the [] are present anymore,
though the call is still dropped
I only have the one failing call logged now.
let me know what you think
Can you reproduce using TLS connection instead of UDP
On UDP at present : if the new logs don't help I may be able to switch
to that
regards
kevin
On 21 January 2015 at 14:33, Johan Pascal <address@hidden
<mailto:address@hiddenorg>> wrote:
Hi Kevin,
thanks for the complete traces, it helps a lot.
On your fail case linphone is unable to parse the SDP 200Ok message
sent by the remote client. This is because the incoming message have
this line:(see trace line 304)
c=IN IP6 [fd9f:af1c:a25b:0:6ab5:99ff:__feea:62fc]
The [] around the IPV6 address are not valid on the c line.
In your wireshark log I can't see the [] around the address. Did you
capture the packets on the remote client computer or the linphone's one?
It looks like some router messed the SDP 200Ok. Can you reproduce
using TLS connection instead of UDP?
Can you capture both the packet outgoing from the remote client side
and the incoming packet arriving on the machine running linphone
just to check that the incoming packet has been corrupted as I suspect?
regards,
Johan
On 21/01/15 11:53, kevin barnard wrote:
Hello
My first attempt at trying to help out with a bug report
Attached is zip file with pcap and Linphone logs
two calls are of interest, one failing and one working
a difference I see is that the failing one has an (a) rtmap section,
which may be causing the call to be dropped by Linphone, though that
rtpmap should be optional ?
another is that the working one has "message: Adding PCMU/8000 for
compatibility, just in case"
anyway, let me know what you think
regards
kevin
GOOD
v=0
o=aculab-01841801 15724 15724 IN IP6
fd9f:af1c:a25b:0:6ab5:99ff:__feea:62fc
s=-
c=IN IP6 fd9f:af1c:a25b:0:6ab5:99ff:__feea:62fc
t=0 0
m=audio 10720 RTP/AVP 8 101
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
message: channel [0xcfde40] [593] bytes parsed
message: Found transaction matching response.
message: Changing [client] [INVITE] transaction [0xdd7e80], from
state
[PROCEEDING] to [ACCEPTED]
message: Dialog [0xd7d2a0]: now updated by transaction [0xdd7e80].
message: op [0xdbbb80] : set_or_update_dialog() current=[0xd7d2a0]
new=[0xd7d2a0]
message: Op [0xdbbb80] receiving call response [200], dialog is
[0xd7d2a0] in state [BELLE_SIP_DIALOG_CONFIRMED]
message: Found payload PCMA/8000 fmtp=
message: Found payload telephone-event/8000 fmtp=0-15
message: Doing SDP offer/answer process of type outgoing
message: Processing for stream 0
message: Adding PCMU/8000 for compatibility, just in case.
BAD
v=0
o=aculab-01642001 26500 26500 IN IP6
fd9f:af1c:a25b:0:6ab5:99ff:__feea:62fc
s=-
c=IN IP6 fd9f:af1c:a25b:0:6ab5:99ff:__feea:62fc
t=0 0
m=audio 0 RTP/AVP 8 101
*a=rtpmap:8 PCMA/8000*
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
message: channel [0xcfde40] [593] bytes parsed
message: Found transaction matching response.
message: Changing [client] [INVITE] transaction [0xdccdd0], from
state
[PROCEEDING] to [ACCEPTED]
message: Dialog [0xdcfea0]: now updated by transaction [0xdccdd0].
message: op [0xd9a580] : set_or_update_dialog() current=[0xdcfea0]
new=[0xdcfea0]
message: Op [0xd9a580] receiving call response [200], dialog is
[0xdcfea0] in state [BELLE_SIP_DIALOG_CONFIRMED]
message: Found payload PCMA/8000 fmtp=
message: Found payload telephone-event/8000 fmtp=0-15
message: Doing SDP offer/answer process of type outgoing
message: Processing for stream 0
warning: No matching stream for 0
_________________________________________________
Linphone-developers mailing list
address@hidden
<mailto:Linphone-developers@nongnu.org>
https://lists.nongnu.org/__mailman/listinfo/linphone-__developers <https://lists.nongnu.org/mailman/listinfo/linphone-developers>
_________________________________________________
Linphone-developers mailing list
address@hidden <mailto:Linphone-developers@nongnu.org>
https://lists.nongnu.org/__mailman/listinfo/linphone-__developers
<https://lists.nongnu.org/mailman/listinfo/linphone-developers>
_______________________________________________
Linphone-developers mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/linphone-developers
_______________________________________________
Linphone-developers mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/linphone-developers