Agreed suggesting UDP port 0 is reserved in SIP to decline the RTP stream without ignoring it. The better question is WHY does linphone, when configured to use H264 then decline it. Was a linphone binary released with missing libraries or un(der)declared/documented (as in "I could not find reference to it") dependencies?

Robin



On 26/03/15 16:00, [email protected] wrote:
Send Linphone-users mailing list submissions to
        [email protected]

To subscribe or unsubscribe via the World Wide Web, visit
        https://lists.nongnu.org/mailman/listinfo/linphone-users
or, via email, send a message with subject or body 'help' to
        [email protected]

You can reach the person managing the list at
        [email protected]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Linphone-users digest..."


Today's Topics:

    1.  linphone declines video by setting RTP port of 0. (robin)
    2.  media port 0 ? (robin)
    3. Re:  media port 0 ? (Ghislain MARY)


----------------------------------------------------------------------

Message: 1
Date: Wed, 25 Mar 2015 16:05:14 +0000
From: robin <[email protected]>
To: [email protected]
Subject: [Linphone-users] linphone declines video by setting RTP port
        of 0.
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8; format=flowed

This is not the expected behaviour of a SIP client, can anyone shed some
light on this?


Linphone build is: 2.3.2-333-g59dd5e0


Config file as follows:
root@tilapia:/ # cat /data/data/org.linphone/files/linphonerc
[net]
mtu=1300

[sip]
guess_hostname=1
inc_timeout=15
register_only_when_network_is_up=1
auto_net_state_mon=0
auto_answer_replacing_calls=1
media_encryption_mandatory=0
ping_with_options=0
root_ca=/data/data/org.linphone/files/rootca.pem

[rtp]
audio_rtp_port=7076
video_rtp_port=9078
audio_jitt_comp=60
video_jitt_comp=60
nortp_timeout=30
disable_upnp=1

[sound]
playback_dev_id=
ringer_dev_id=
capture_dev_id=
remote_ring=/data/data/org.linphone/files/ringback.wav
local_ring=/data/data/org.linphone/files/oldphone_mono.wav
dtmf_player_amp=0.1

[misc]
max_calls=10


pcap in human readable form :

pastebin.com/6emaK3eQ


Robin




------------------------------

Message: 2
Date: Thu, 26 Mar 2015 01:22:31 +0000
From: robin <[email protected]>
To: [email protected]
Subject: [Linphone-users] media port 0 ?
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8; format=flowed


This is not the expected behaviour of a SIP client, can anyone shed some
light on this?


Linphone build is: 2.3.2-333-g59dd5e0


Config file as follows:
root@tilapia:/ # cat /data/data/org.linphone/files/linphonerc
[net]
mtu=1300

[sip]
guess_hostname=1
inc_timeout=15
register_only_when_network_is_up=1
auto_net_state_mon=0
auto_answer_replacing_calls=1
media_encryption_mandatory=0
ping_with_options=0
root_ca=/data/data/org.linphone/files/rootca.pem

[rtp]
audio_rtp_port=7076
video_rtp_port=9078
audio_jitt_comp=60
video_jitt_comp=60
nortp_timeout=30
disable_upnp=1

[sound]
playback_dev_id=
ringer_dev_id=
capture_dev_id=
remote_ring=/data/data/org.linphone/files/ringback.wav
local_ring=/data/data/org.linphone/files/oldphone_mono.wav
dtmf_player_amp=0.1

[misc]
max_calls=10


pcap in human readable form :

pastebin.com/6emaK3eQ


Robin



------------------------------

Message: 3
Date: Thu, 26 Mar 2015 09:40:34 +0100
From: Ghislain MARY <[email protected]>
To: [email protected]
Subject: Re: [Linphone-users] media port 0 ?
Message-ID: <[email protected]>
Content-Type: text/plain; charset="windows-1252"; Format="flowed"

Hi Robin,

There's nothing wrong with that. This is the standard way to remove a
stream. Look at the section 8.2 "Removing a Media Stream" of the SDP RFC
(3264) <https://www.ietf.org/rfc/rfc3264.txt>.
In your case, you performing a call proposing the use of H.264 for video
to a client that does not support H.264. Therefore this client answers
the call removing the video stream that it just cannot support.

Cheers,
Ghislain

Le 26/03/2015 02:22, robin a ?crit :
This is not the expected behaviour of a SIP client, can anyone shed some
light on this?


Linphone build is: 2.3.2-333-g59dd5e0


Config file as follows:
root@tilapia:/ # cat /data/data/org.linphone/files/linphonerc
[net]
mtu=1300

[sip]
guess_hostname=1
inc_timeout=15
register_only_when_network_is_up=1
auto_net_state_mon=0
auto_answer_replacing_calls=1
media_encryption_mandatory=0
ping_with_options=0
root_ca=/data/data/org.linphone/files/rootca.pem

[rtp]
audio_rtp_port=7076
video_rtp_port=9078
audio_jitt_comp=60
video_jitt_comp=60
nortp_timeout=30
disable_upnp=1

[sound]
playback_dev_id=
ringer_dev_id=
capture_dev_id=
remote_ring=/data/data/org.linphone/files/ringback.wav
local_ring=/data/data/org.linphone/files/oldphone_mono.wav
dtmf_player_amp=0.1

[misc]
max_calls=10


pcap in human readable form :

pastebin.com/6emaK3eQ


Robin

_______________________________________________
Linphone-users mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/linphone-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://lists.nongnu.org/archive/html/linphone-users/attachments/20150326/6f610e7d/attachment.html>

------------------------------

_______________________________________________
Linphone-users mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/linphone-users


End of Linphone-users Digest, Vol 148, Issue 23
***********************************************


_______________________________________________
Linphone-users mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/linphone-users

Reply via email to