[OpenSIPS-Users] What does mean "a=inactive"?

[Rodrigo Pimenta Carvalho]

Hi.


Thank you very much!


Your explanation was sufficient and now I understood what is happening.

There is no changes caused by OpenSIPS. Is the UAC that decides to put that "inactive" there.


Best regards.


RODRIGO PIMENTA CARVALHO
Inatel Competence Center
Software
Ph: +55 35 3471 9200 RAMAL 979


________________________________
De: users-bounces at lists.opensips.org <users-bounces at lists.opensips.org> em nome de Benjamin Cropley <benjamin.cropley at gmail.com>
Enviado: quarta-feira, 7 de setembro de 2016 09:01
Para: OpenSIPS users mailling list
Assunto: Re: [OpenSIPS-Users] What does mean "a=inactive"?

I would start by looking at a trace. Is it A changing the SDP attribute? or is OpenSIPS doing it?

Inactive obviously means "Keep the session live, but dont send me any audio, and I won't send you any audio".

I've seen that happen once, when both end points couldnt establish a codec.. due to processing error or something like that, but instead of sending an appropriate error, it just connects the call and send that.

Hope that helps,
Ben Cropley

On Thu, Sep 1, 2016 at 1:12 PM, Rodrigo Pimenta Carvalho <pimenta at inatel.br<mailto:pimenta at inatel.br>> wrote:


Dear OpenSIPS users;

I'm not sure if the following question is about OpenSIPS, or SIP, or SDP, but...

I have 2 softphones (Microsip) with SIP UAC: in phone A and in phone B. There is a SIP Proxy (OpenSIPS) between they too.


When A calls B, I can see the SIP messages (via wireshark) and in some moment A sends a SIP UPDATE do B.

The SIP UPDATE has SDP with lines like this:


v=0
o=- 3681643549 3681643550 IN IP4 XXX.YYY.240.204
s=pjmedia
b=AS:84
t=0 0
a=X-nat:1
m=audio 64568 RTP/AVP 110 8 101
c=IN IP4 XXX.YYY.240.204
b=TIAS:64000
a=rtpmap:110 speex/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=ice-ufrag:139d7049
a=ice-pwd:692c4a80
a=rtcp:64571 IN IP4 XXX.YYY.240.204
a=candidate:Sc0a81485 1 UDP 1862270975 XXX.YYY.240.204 64568 typ srflx raddr 192.168.20.133 rport 64568
a=candidate:Sc0a81485 2 UDP 1862270974 XXX.YYY.240.204 64571 typ srflx raddr 192.168.20.133 rport 64571
a=remote-candidates:1 XXX.YYY.240.71 64993 2 XXX.YYY.240.71 64996
a=sendrecv

However, if I replace the SIP Proxy with another one containing the same software (Same OpenSIPS, database, network, etc. Just hardware is different) and run the same call (A calls B), that "a=sendrecv" in SIP UPDATE changes to "a=inactive". If the peers are still the same, how could a media attribute changes?


I have no idea what could cause this difference related to media attribute! Could OpenSIPS take care of this case?

Could someone here give me some examples of what could cause an "a=inactive", so that I will have a point to start my analyze of the problem?

I will also take a look in the SIP RFC to get some hint.

Any hint will be very very helpful!

Best regards.



RODRIGO PIMENTA CARVALHO
Inatel Competence Center
Software
Ph: +55 35 3471 9200<tel:%2B55%2035%203471%209200> RAMAL 979

_______________________________________________
Users mailing list
Users at lists.opensips.org<mailto:Users at lists.opensips.org>
http://lists.opensips.org/cgi-bin/mailman/listinfo/users




--
All the best,
Ben Cropley
07539 366 905
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20160908/ce04901a/attachment.htm>