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

[Simon Morlat]

Hi,

Linphone do answer to OPTIONS message (it even sends them). If you are
still seeing this problem of unanswered OPTIONS, please send a log
because it is surely a problem I'm not aware of, nor able to reproduce.
Thanks

SImon

Le vendredi 17 septembre 2010 à 09:28 -0400, Kevin Cross a écrit :
> Tested the INFO fix and it works :)
> I did not see the OPTIONS fix on the repo yet, but wanted to make a
> quick comment about it.
> Mirial (and apparently several other end-points) uses OPTIONS as
> keep-alive, so when it does not see a response to several of them it
> terminates the call. 
> 
> Thanks,
> K
> 
> On Fri, Sep 17, 2010 at 3:39 AM, Simon Morlat
> <address@hidden> wrote:
>         Hi Claudio,
>         
>         Thanks for reporting. I'm fixing the problem.
>         
>         Simon
>         
>         Le lundi 13 septembre 2010 à 10:29 -0400, Kevin Cross a
>         écrit :
>         
>         > 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
>         
>         > _______________________________________________
>         > Linphone-developers mailing list
>         > address@hidden
>         > http://lists.nongnu.org/mailman/listinfo/linphone-developers
>         
>         
>         
>         _______________________________________________
>         Linphone-developers mailing list
>         address@hidden
>         http://lists.nongnu.org/mailman/listinfo/linphone-developers
> 
> _______________________________________________
> Linphone-developers mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/linphone-developers