Handling INFO request responses

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Benny,

I tested with two commercial proxies, one do not answer INFO request at all,
and the other answers with a 481. But both answer to BYE with 200/OK.

So I will wait on your fix.

Thanks

Philippe Leuba

-----Original Message-----
From: pjsip-bounces@xxxxxxxxxxxxxxx [mailto:pjsip-bounces at lists.pjsip.org]
On Behalf Of Benny Prijono
Sent: mardi, 19. f?vrier 2008 09:26
To: pjsip list
Subject: Re: Handling INFO request responses

On 2/18/08, Philippe <philippe.leuba at eyepmedia.com> wrote:
>
> Hello,
>
> When we send an INFO request in an INVITE initiated dialog and receive
back
> a 481 or 408 response, the pj stack invokes the on_state_changed callback
of
> the invite session with the PJSIP_INV_STATE_DISCONNECTED state.
>
> This result in the termination of the dialog and is compliant with section
> 12.2.1.2 of RFC 3261, however a BYE request is not sent.
>
> Is it the application responsibility to do it or is it a mistake?
>

Hi Philippe,

I think you should first find out why the proxy sends 481/408, if the
remote dialog is still alive in the first place. I decided not to send
BYE because I would think that the BYE most likely will be responded
with 481 anyway, so why bother wasting another transaction?

But you're right, this is not strictly compliant with the RFC. I've
just added http://trac.pjsip.org/repos/ticket/488 to fix this.

thanks,
 -benny

>
>
> Best regards
>
>
>
> Philippe Leuba
>
> eyeP Media SA
> _______________________________________________
> Visit our blog: http://blog.pjsip.org
>
> pjsip mailing list
> pjsip at lists.pjsip.org
> http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org
>
>

_______________________________________________
Visit our blog: http://blog.pjsip.org

pjsip mailing list
pjsip at lists.pjsip.org
http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org




[Index of Archives]     [Asterisk Users]     [Asterisk App Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [Linux API]
  Powered by Linux