[Linphone-developers] No response to OPTIONS or INFO messages?

[Kevin Cross]

Hello,

I was testing linphone against other endpoints and by looking at the trace I noticed that linphone does not reply to INFO msgs with media control messages it cannot handle.
This causes the other endpoint to continuously send the same packet during the session.

INFO sip:address@hidden SIP/2.0
Content-Type: application/media_control+xml
Content-Length: 163
To: <sip:address@hidden>;tag=2063506250
From: "user004" <sip:address@hidden>;tag=DLc57bafead1;epid=0x1ede7e0
CSeq: 1 INFO
Call-ID: 1119294776
Max-Forwards: 70
Via: SIP/2.0/UDP 192.168.100.19:5060;branch=z9hG4bK-2e4a9fa1ed-DL
Contact: "user004" <sip:address@hidden:5060>

<?xml version="1.0" encoding="utf-8" ?><media_control><vc_primitive><to_encoder><change_bitrate>408400</change_bitrate></to_encoder></vc_primitive></media_control>


Also, linphone did not response to an std OPTIONS request causing the other endpoint to continuously send the OPTIONS msg.

OPTIONS sip:address@hidden SIP/2.0
To: <sip:address@hidden>;tag=2063506250
From: "user004" <sip:address@hidden>;tag=DLc57bafead1;epid=0x1ede7e0
CSeq: 4 OPTIONS
Call-ID: 1119294776
Max-Forwards: 70
Via: SIP/2.0/UDP 192.168.100.19:5060;branch=z9hG4bK-98abd6bea2-DL
Contact: "user004" <sip:address@hidden:5060>
Content-Length: 0


All the calls where made using the other endpoint private ip address on a private network.

I am not a VoIP expert by any means but shouldn't those packets be acknowledge in some way? A quick look at the RFC shows several ways of responding.

Thanks,
Claudio