PRACK and local outbound proxy

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

 



New requests within the dialog will usually go where stated in contact
header of the previous response or as you said using the record route
URI.

The outbound proxy configuration claims that any request will pass
through the proxy, regardless of the contact/RR URIs.

I use SBC instead of proxy, and I can't make it add record route,
therefore there will be no record route at all. But it does put its own
URI in the contact header - and this was ignored by pjsip as well.

 

Regards,

Noga

 

 

________________________________

From: pjsip-bounces@xxxxxxxxxxxxxxx
[mailto:pjsip-bounces at lists.pjsip.org] On Behalf Of Gang Liu
Sent: Thursday, February 05, 2009 12:26 PM
To: pjsip list
Subject: Re: PRACK and local outbound proxy

 

I didn't check pjsip source code to check how PRACK handle preloaded
route set.
But I think CANCEL goes wherever the INVITE went, using the same route.
But PRACK, UPDATE, INFO not this way.
Correct me if my understanding is wrong.

BTW, any Record-Route Header added into 200 OK respond?

regards,
Gang

On Thu, Feb 5, 2009 at 5:28 PM, Noga Yehudai <nogab at juniper.net> wrote:

Isn't that the point of local outbound proxy configuration - to always
pass through the proxy?

For example re-inv passes through the proxy with the same configuration.

 

Regards,

Noga

 

________________________________

From: pjsip-bounces@xxxxxxxxxxxxxxx
[mailto:pjsip-bounces at lists.pjsip.org] On Behalf Of Gang Liu
Sent: Thursday, February 05, 2009 10:58 AM
To: pjsip list
Subject: Re: PRACK and local outbound proxy

 

Enable record route at your proxy and try again.

180 ring from proxy don't include Record-Route Header.

regards,

Gang

On Thu, Feb 5, 2009 at 3:33 PM, Noga Yehudai <nogab at juniper.net> wrote:

Hi,

I found a problem when using Pjsua with -use-100rel and -outbound.

When using outbound proxy with PRACK, the PRACK will be sent directly to
the user and bypass the proxy.

Do you have any idea how to overcome this issue? Is it a known bug?

I attached the capture of the call you can use Wireshark to view it.

 

Thanks,

Noga


_______________________________________________
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

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.pjsip.org/pipermail/pjsip_lists.pjsip.org/attachments/20090205/3c45a98a/attachment.html>


[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