Hi,

I am trying to port pjsip to PPC 440EPX. I am using the following configure command:

./configure --build=i686-linux --host=powerpc-montavista-linux-gnu --target=powerpc-montavista-linux-gnu GCC=/opt/montavista/pro/devkit/ppc/440ep/bin/ppc_440ep-gcc CC=/opt/montavista/pro/devkit/ppc/440ep/bin/ppc_440ep-gcc CXX=ppc_440ep-g++ LD=ppc_440ep-ld LDD=ppc_440ep-ldd AR=ppc_440ep-ar AS=ppc_440ep-as NM=ppc_440ep-nm STRIP=ppc_440ep-strip RANLIB=ppc_440ep-ranlib OBJDUMP=ppc_440ep-objdump CPPFLAGS=-I/opt/montavista/pro/devkit/ppc/440ep/target/usr/include/ LDFLAGS=-L/opt/montavista/pro/devkit/ppc/440ep/target/usr/lib/  --prefix=/root/pjp/

I am getting the following at 'make dep' time:

root@VirtualTarget:~/DEV/pjproject-1.0.make dep
for dir in pjlib pjlib-util pjnath third_party pjmedia pjsip pjsip-apps; do
if make  -C $dir/build dep; then
true;
else
exit 1;
fi;
done
make[1]: Entering directory /root/DEV/pjproject-1.0.1/pjlib/build' make -f /root/DEV/pjproject-1.0.1/build/rules.mak APP=PJLIB app=pjlib depend make[2]: Entering directory /root/DEV/pjproject-1.0.1/pjlib/build'
.pjlib-powerpc-montavista-linux-gnu.depend:1: *** missing separator.  Stop.
make[2]: Leaving directory /root/DEV/pjproject-1.0.1/pjlib/build' make[1]: *** [depend] Error 2 make[1]: Leaving directory /root/DEV/pjproject-1.0.1/pjlib/build'
make: *** [dep] Error 1

Could you let me know what how I could fix that? I did look at

http://www.pjsip.org/porting.htm
http://www.pjsip.org/pjlib/docs/html/porting_pjlib_pg.htm

but did not find anything yet,

Thanks for any help,

seb.

Manually remove files  /root/DEV/pjproject-1.0.1/pjlib/build/.*depend
May be from /root/DEV/pjproject-1.0.1/pjlib-util/build and other directories too.
Anna

From: tic tac hotsblanc@hotmail.com
To: pjsip@lists.pjsip.org
Sent: Tuesday, February 3, 2009 7:16:42 PM
Subject: [pjsip] porting pjsip to PPC 440EPX

Hi,

I am trying to port pjsip to PPC 440EPX. I am using the following configure command:

./configure --build=i686-linux --host=powerpc-montavista-linux-gnu --target=powerpc-montavista-linux-gnu GCC=/opt/montavista/pro/devkit/ppc/440ep/bin/ppc_440ep-gcc CC=/opt/montavista/pro/devkit/ppc/440ep/bin/ppc_440ep-gcc CXX=ppc_440ep-g++ LD=ppc_440ep-ld LDD=ppc_440ep-ldd AR=ppc_440ep-ar AS=ppc_440ep-as NM=ppc_440ep-nm STRIP=ppc_440ep-strip RANLIB=ppc_440ep-ranlib OBJDUMP=ppc_440ep-objdump CPPFLAGS=-I/opt/montavista/pro/devkit/ppc/440ep/target/usr/include/ LDFLAGS=-L/opt/montavista/pro/devkit/ppc/440ep/target/usr/lib/  --prefix=/root/pjp/

I am getting the following at 'make dep' time:

root@VirtualTarget:~/DEV/pjproject-1.0.make dep
for dir in pjlib pjlib-util pjnath third_party pjmedia pjsip pjsip-apps; do
    if make  -C $dir/build dep; then
        true;
    else
        exit 1;
    fi;
done
make[1]: Entering directory /root/DEV/pjproject-1.0.1/pjlib/build' make -f /root/DEV/pjproject-1.0.1/build/rules.mak APP=PJLIB app=pjlib depend make[2]: Entering directory /root/DEV/pjproject-1.0.1/pjlib/build'
.pjlib-powerpc-montavista-linux-gnu.depend:1: *** missing separator.  Stop.
make[2]: Leaving directory /root/DEV/pjproject-1.0.1/pjlib/build' make[1]: *** [depend] Error 2 make[1]: Leaving directory /root/DEV/pjproject-1.0.1/pjlib/build'
make: *** [dep] Error 1

Could you let me know what how I could fix that? I did look at

http://www.pjsip.org/porting.htm
http://www.pjsip.org/pjlib/docs/html/porting_pjlib_pg.htm

but did not find anything yet,

Thanks for any help,

seb.

Thanks Anna. I won't use 'make dep' then :)

FYI using configure as follows:

./configure
...
GCC=/opt/montavista/pro/devkit/ppc/440ep/bin/ppc_440ep-gcc
CC=/opt/montavista/pro/devkit/ppc/440ep/bin/ppc_440ep-gcc
--host=powerpc-montavista-linux-gnu
--target=powerpc-montavista-linux-gnu
...

the configure output gives me:

...
checking for powerpc-montavista-linux-gnu-gcc... /opt/montavista/pro/devkit/ppc/440ep/bin/ppc_440ep-gcc
...

yet 'make' tried to use a gcc binary named something like host/target + '-' + gcc

mkdir -p output/pjlib-powerpc-montavista-linux-gnu
powerpc-montavista-linux-gnu-gcc -c -Wall  -DPJ_AUTOCONF=1 -O2    -I../include
-o output/pjlib-powerpc-montavista-linux-gnu/ioqueue_select.o
../src/pj/ioqueue_select.c
make[2]: powerpc-montavista-linux-gnu-gcc: Command not found
make[2]: *** [output/pjlib-powerpc-montavista-linux-gnu/ioqueue_select.o] Error 127
make[2]: Leaving directory /root/DEV/pjproject-1.0.1/pjlib/build' make[1]: *** [pjlib] Error 2 make[1]: Leaving directory /root/DEV/pjproject-1.0.1/pjlib/build'
make: *** [all] Error 1

I had to manually edit build.mak to replace

export CROSS_COMPILE := powerpc-montavista-linux-gnu-

per

export CROSS_COMPILE := ppc_440ep-

It cross compiled fine then; I'll let know if I get any problems at runtime ;-

Thanks.

Date: Tue, 3 Feb 2009 22:28:01 -0800
From: anna1.white@yahoo.com
To: pjsip@lists.pjsip.org
Subject: Re: [pjsip] porting pjsip to PPC 440EPX

Manually remove files  /root/DEV/pjproject-1.0.1/pjlib/build/.*depend
May be from /root/DEV/pjproject-1.0.1/pjlib-util/build and other directories too.
Anna

From: tic tac hotsblanc@hotmail.com
To: pjsip@lists.pjsip.org
Sent: Tuesday, February 3, 2009 7:16:42 PM
Subject: [pjsip] porting pjsip to PPC 440EPX

Hi,

I am trying to port pjsip to PPC 440EPX. I am using the following configure command:

./configure --build=i686-linux --host=powerpc-montavista-linux-gnu --target=powerpc-montavista-linux-gnu GCC=/opt/montavista/pro/devkit/ppc/440ep/bin/ppc_440ep-gcc CC=/opt/montavista/pro/devkit/ppc/440ep/bin/ppc_440ep-gcc CXX=ppc_440ep-g++ LD=ppc_440ep-ld LDD=ppc_440ep-ldd AR=ppc_440ep-ar AS=ppc_440ep-as NM=ppc_440ep-nm STRIP=ppc_440ep-strip RANLIB=ppc_440ep-ranlib OBJDUMP=ppc_440ep-objdump CPPFLAGS=-I/opt/montavista/pro/devkit/ppc/440ep/target/usr/include/ LDFLAGS=-L/opt/montavista/pro/devkit/ppc/440ep/target/usr/lib/  --prefix=/root/pjp/

I am getting the following at 'make dep' time:

root@VirtualTarget:~/DEV/pjproject-1.0.make dep
for dir in pjlib pjlib-util pjnath third_party pjmedia pjsip pjsip-apps; do
if make  -C $dir/build dep; then
true;

else
exit 1;
fi;
done
make[1]: Entering directory /root/DEV/pjproject-1.0.1/pjlib/build' make -f /root/DEV/pjproject-1.0.1/build/rules.mak APP=PJLIB app=pjlib depend make[2]: Entering directory /root/DEV/pjproject-1.0.1/pjlib/build'
.pjlib-powerpc-montavista-linux-gnu.depend:1: *** missing separator.  Stop.
make[2]: Leaving directory /root/DEV/pjproject-1.0.1/pjlib/build' make[1]: *** [depend] Error 2 make[1]: Leaving directory /root/DEV/pjproject-1.0.1/pjlib/build'
make: *** [dep] Error 1

Could you let me know what how I could fix that? I did look at

http://www.pjsip.org/porting.htm
http://www.pjsip.org/pjlib/docs/html/porting_pjlib_pg.htm

but did not find
anything yet,

Thanks for any help,

seb.

Hi,

I am getting the following link error at runtime

root@sebastien:/data/work/pjsip-apps/bin# ./pjsua-powerpc-montavista-linux-gnu
./pjsua-powerpc-montavista-linux-gnu: error while loading shared libraries: libasound.so.2: cannot open shared object file: No such file or directory

I however don't see any asound library in my runtime tree (plus it looks like I am not configured to generate shared libraries, only static ones).

root@VirtualTarget:~/DEV/pjproject-1.0.1# find . -name asound
./pjmedia/src/pjmedia/pasound.c
./pjmedia/build/output/pjmedia-powerpc-montavista-linux-gnu/pasound.o

root@VirtualTarget:~/DEV/pjproject-1.0.1# find . -name Makefile -exec grep -i sound {} ; -print
NULLSOUND_OBJS := nullsound.o
session.o silencedet.o sound_port.o stereo_port.o
wsola.o $(SOUND_OBJS) $(NULLSOUND_OBJS)
./pjmedia/build/Makefile

Do you know where this library is supposed to be located ?

Thanks,

seb.

it seems to be coming from ALSA, is that a required external dependency or would I be able to remove it from build if I just want to run SIP and RTP (and no prompts for instance) ...?

From: hotsblanc@hotmail.com
To: pjsip@lists.pjsip.org
Date: Wed, 4 Feb 2009 09:34:52 -0600
Subject: Re: [pjsip] porting pjsip to PPC 440EPX

Hi,

I am getting the following link error at runtime

root@sebastien:/data/work/pjsip-apps/bin# ./pjsua-powerpc-montavista-linux-gnu
./pjsua-powerpc-montavista-linux-gnu: error while loading shared libraries: libasound.so.2: cannot open shared object file: No such file or directory

I however don't see any asound library in my runtime tree (plus it looks like I am not configured to generate shared libraries, only static ones).

root@VirtualTarget:~/DEV/pjproject-1.0.1# find . -name asound
./pjmedia/src/pjmedia/pasound.c
./pjmedia/build/output/pjmedia-powerpc-montavista-linux-gnu/pasound.o

root@VirtualTarget:~/DEV/pjproject-1.0.1# find . -name Makefile -exec grep -i sound {} ; -print
NULLSOUND_OBJS := nullsound.o
session.o silencedet.o sound_port.o stereo_port.o
wsola.o $(SOUND_OBJS) $(NULLSOUND_OBJS)
./pjmedia/build/Makefile

Do you know where this library is supposed to be located ?

Thanks,

seb.

Hi,

When cross-compiling, configure as per what the executables are in the /opt/montavista/pro/devkit/ppc/440ep/bin/ directory

./configure --host=ppc_440ep

Then theres probably no need to change any of the GCC or CC variables.

If u get a missing separator error, do a make distclean

make dep

make

make install

Then  ./pjsua-powerpc-montavista-linux-gnu --help

best,

Nigel

From: hotsblanc@hotmail.com
To: pjsip@lists.pjsip.org
Date: Wed, 4 Feb 2009 09:41:45 -0600
Subject: Re: [pjsip] porting pjsip to PPC 440EPX

it seems to be coming from ALSA, is that a required external dependency or would I be able to remove it from build if I just want to run SIP and RTP (and no prompts for instance) ...?

From: hotsblanc@hotmail.com
To: pjsip@lists.pjsip.org
Date: Wed, 4 Feb 2009 09:34:52 -0600
Subject: Re: [pjsip] porting pjsip to PPC 440EPX

Hi,

I am getting the following link error at runtime

root@sebastien:/data/work/pjsip-apps/bin# ./pjsua-powerpc-montavista-linux-gnu
./pjsua-powerpc-montavista-linux-gnu: error while loading shared libraries: libasound.so.2: cannot open shared object file: No such file or directory

I however don't see any asound library in my runtime tree (plus it looks like I am not configured to generate shared libraries, only static ones).

root@VirtualTarget:~/DEV/pjproject-1.0.1# find . -name asound
./pjmedia/src/pjmedia/pasound.c
./pjmedia/build/output/pjmedia-powerpc-montavista-linux-gnu/pasound.o

root@VirtualTarget:~/DEV/pjproject-1.0.1# find . -name Makefile -exec grep -i sound {} ; -print
NULLSOUND_OBJS := nullsound.o
session.o silencedet.o sound_port.o stereo_port.o
wsola.o $(SOUND_OBJS) $(NULLSOUND_OBJS)
./pjmedia/build/Makefile

Do you know where this library is supposed to be located ?

Thanks,

seb.

More than messages–check out the rest of the Windows Live™.
http://www.microsoft.com/windows/windowslive/

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

Hello,

Are IPP codec libs from Intel supposed to work on Windows mobile phones
also?...I mean can pjsip work with IPP libs and be installed on windows
mobile phones?

Regards,

Manoj

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@lists.pjsip.org
[mailto:pjsip-bounces@lists.pjsip.org] On Behalf Of Gang Liu
Sent: Thursday, February 05, 2009 10:58 AM
To: pjsip list
Subject: Re: [pjsip] 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@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@lists.pjsip.org
http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org

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@lists.pjsip.org
[mailto:pjsip-bounces@lists.pjsip.org] On Behalf Of Gang Liu
Sent: Thursday, February 05, 2009 12:26 PM
To: pjsip list
Subject: Re: [pjsip] 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@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@lists.pjsip.org
[mailto:pjsip-bounces@lists.pjsip.org] On Behalf Of Gang Liu
Sent: Thursday, February 05, 2009 10:58 AM
To: pjsip list
Subject: Re: [pjsip] 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@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@lists.pjsip.org
http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org

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

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

I think that is about what I said in the last e-mail, is it a bug then?

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

from RFC 3261

8.1.1.1 Request-URI

A pre-existing route

set is an ordered set of URIs that identify a chain of servers, to

which a UAC will send outgoing requests that are outside of a dialog.

When a provider

wishes to configure a UA with an outbound proxy, it is RECOMMENDED

that this be done by providing it with a pre-existing route set with

a single URI, that of the outbound proxy.

12.1.2 UAC Behavior

If no Record-Route header field is present in

the response, the route set MUST be set to the empty set.  This route

set, even if empty, overrides any pre-existing route set for future

requests in this dialog.  The remote target MUST be set to the URI

from the Contact header field of the response.

On Thu, Feb 5, 2009 at 6:25 PM, Gang Liu gangban.lau@gmail.com wrote:

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@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@lists.pjsip.org
[mailto:pjsip-bounces@lists.pjsip.org] On Behalf Of Gang Liu
Sent: Thursday, February 05, 2009 10:58 AM
To: pjsip list
Subject: Re: [pjsip] 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@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@lists.pjsip.org
http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org

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

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

Inline

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

inline.

On Thu, Feb 5, 2009 at 6:42 PM, Noga Yehudai nogab@juniper.net wrote:

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.

This isn't true for RFC 3261.

[Noga] you are right, only apply to req' uri.

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.

I don't think it is SBC. It didn't change contact of 180 respond.

[Noga] it does change the contact; please see line 5 in cap file as
opposed to line 4.

Regards,

Noga

 

 

From: pjsip-bounces@lists.pjsip.org

[mailto:pjsip-bounces@lists.pjsip.org] On Behalf Of Gang Liu
Sent: Thursday, February 05, 2009 12:26 PM
To: pjsip list
Subject: Re: [pjsip] 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@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@lists.pjsip.org

[mailto:pjsip-bounces@lists.pjsip.org] On Behalf Of Gang Liu
Sent: Thursday, February 05, 2009 10:58 AM
To: pjsip list
Subject: Re: [pjsip] 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@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@lists.pjsip.org
http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org

 


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

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

 


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

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

Hi,

That's what I'm trying to find out as well.
In the meantime check http://lists.pjsip.org/pipermail/pjsip_lists.pjsip.org/2008-August/004513.html and http://lists.pjsip.org/pipermail/pjsip_lists.pjsip.org/2009-February/006203.html

Good luck, and please let us know if you manage to successfuly build it for Windows mobile.

Regards,
Elias.

From: manoj@ascenttelecom.comTo: pjsip@lists.pjsip.orgDate: Thu, 5 Feb 2009 13:25:55 +0530Subject: [pjsip] IPP Codecs

Hello,

Are IPP codec libs from Intel supposed to work on Windows mobile phones also?...I mean can pjsip work with IPP libs and be installed on windows mobile phones?

Regards,

Manoj

Windows Live™: E-mail. Chat. Share. Get more ways to connect.
http://windowslive.com/online/hotmail?ocid=TXT_TAGLM_WL_HM_AE_Faster_022009

It should deliver the next request to the URI from the contact - which
is the sbc uri.

Noga.

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

Pls consider, how can pjsua know where callee is if your SBC hide the
callee contact.

On Thu, Feb 5, 2009 at 8:47 PM, Noga Yehudai nogab@juniper.net wrote:

Inline

From: pjsip-bounces@lists.pjsip.org
[mailto:pjsip-bounces@lists.pjsip.org] On Behalf Of Gang Liu
Sent: Thursday, February 05, 2009 12:58 PM

To: pjsip list
Subject: Re: [pjsip] PRACK and local outbound proxy

inline.

On Thu, Feb 5, 2009 at 6:42 PM, Noga Yehudai nogab@juniper.net wrote:

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.

This isn't true for RFC 3261.

[Noga] you are right, only apply to req' uri.

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.

I don't think it is SBC. It didn't change contact of 180 respond.

[Noga] it does change the contact; please see line 5 in cap file as
opposed to line 4.

Regards,

Noga

 

 

From: pjsip-bounces@lists.pjsip.org

[mailto:pjsip-bounces@lists.pjsip.org] On Behalf Of Gang Liu
Sent: Thursday, February 05, 2009 12:26 PM
To: pjsip list
Subject: Re: [pjsip] 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@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@lists.pjsip.org

[mailto:pjsip-bounces@lists.pjsip.org] On Behalf Of Gang Liu
Sent: Thursday, February 05, 2009 10:58 AM
To: pjsip list
Subject: Re: [pjsip] 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@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 <http://blog.pjsip.org/> 

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

 


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

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

 


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

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

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

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