Lewis Liu | 30 Oct 01:46 2008
Picon

Re: question about make call out

Thanks Nanang,
Yes, I use version 1.0.
I follow your commands. But it still can not work.
The parameters are :
cfg.id = pj_str("sip:07010174608 <at> chiefcall.com.tw");
cfg.reg_uri = pj_str("sip:202.153.167.4;lr");
cfg.cred_count = 1;
cfg.cred_info[0].realm = pj_str("*");
cfg.cred_info[0].scheme = pj_str("digest");
cfg.cred_info[0].username = pj_str(SIP_USER);
cfg.cred_info[0].data_type = PJSIP_CRED_DATA_PLAIN_PASSWD;
cfg.cred_info[0].data = pj_str(SIP_PASSWD);
I use the command "simple_pjsua xxx".
This operation can be successful to register to server.
But it can not get any response when make "INVITE" message to server.
Please help me whats wrong??
I use another sip phone - X-Lite.
It can work to make call out.
So I log all files to let someone help me!!

All log files are as attachment.
The "ok1" and "fail" are generated from Ethereal.
"ok1" is okay from X-Lite. and "fail" is not okay from "simple_pjsua xxxxx".
Anther one attachment "callout.txt" is log file for "simple_pjsua xxxxx".
Please help me again!!
Thanks a lot.


2008/10/28 Nanang Izzuddin <nanang <at> pjsip.org>
Hi again,

Please try to add ";lr" in the proxy setting, e.g:
--proxy sip:chiefcall.com.tw;lr

And please see ticket #611 (http://trac.pjsip.org/repos/ticket/611),
so in 1.0 (the version you are using) actually this should be
automatically added by pjsua-lib, did you disable that feature?

Regards,
nanang


On Sat, Oct 25, 2008 at 10:27 PM, Lewis Liu <lewisppp <at> gmail.com> wrote:
> Hi sir,
>
> Sorry to ask again because I wait for 3 days but have not gotten any answer.
> I use the pjsua sample to make call out.
> "simple_pjsua xxx"    (xxx is called party)
> But xxx has not gotten any incoming call.
> So anyone can help me, please??
> Attachment is the log file.
> Thanks a lot!!
> Lewis
>
> _______________________________________________
> 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

Attachment (ok1): application/octet-stream, 115 KiB
Attachment (fail): application/octet-stream, 19 KiB
 17:55:11.719 os_core_win32.  pjlib 1.0 for win32 initialized
 17:55:11.730 sip_endpoint.c  Creating endpoint instance...
 17:55:11.730          pjlib  WinNT IOCP I/O Queue created (003CD288)
 17:55:11.730 sip_endpoint.c  Module "mod-msg-print" registered
 17:55:11.730 sip_transport.  Transport manager created.
 17:55:11.730 sip_endpoint.c  Module "mod-pjsua-log" registered
 17:55:11.730 sip_endpoint.c  Module "mod-tsx-layer" registered
 17:55:11.730 sip_endpoint.c  Module "mod-stateful-util" registered
 17:55:11.730 sip_endpoint.c  Module "mod-ua" registered
 17:55:11.730 sip_endpoint.c  Module "mod-100rel" registered
 17:55:11.730 sip_endpoint.c  Module "mod-pjsua" registered
 17:55:11.730 sip_endpoint.c  Module "mod-invite" registered
 17:55:12.020      pasound.c  PortAudio sound library initialized, status=0
 17:55:12.020      pasound.c  PortAudio host api count=3
 17:55:12.020      pasound.c  Sound device count=12
 17:55:12.020          pjlib  WinNT IOCP I/O Queue created (004F15FC)
 17:55:12.020 sip_endpoint.c  Module "mod-evsub" registered
 17:55:12.020 sip_endpoint.c  Module "mod-presence" registered
 17:55:12.020 sip_endpoint.c  Module "mod-refer" registered
 17:55:12.020 sip_endpoint.c  Module "mod-pjsua-pres" registered
 17:55:12.020 sip_endpoint.c  Module "mod-pjsua-im" registered
 17:55:12.020 sip_endpoint.c  Module "mod-pjsua-options" registered
 17:55:12.020   pjsua_core.c  1 SIP worker threads created
 17:55:12.020   pjsua_core.c  pjsua version 1.0 for win32 initialized
 17:55:12.040   pjsua_core.c  SIP UDP socket reachable at 210.68.184.193:5060
 17:55:12.040    udp004FD2E8  SIP UDP transport started, published address is 210.68.184.193:5060
 17:55:12.040  pjsua_media.c  RTP socket reachable at 210.68.184.193:4000
 17:55:12.040  pjsua_media.c  RTCP socket reachable at 210.68.184.193:4001
 17:55:12.040  pjsua_media.c  RTP socket reachable at 210.68.184.193:4002
 17:55:12.040  pjsua_media.c  RTCP socket reachable at 210.68.184.193:4003
 17:55:12.050  pjsua_media.c  RTP socket reachable at 210.68.184.193:4004
 17:55:12.050  pjsua_media.c  RTCP socket reachable at 210.68.184.193:4005
 17:55:12.050  pjsua_media.c  RTP socket reachable at 210.68.184.193:4006
 17:55:12.050  pjsua_media.c  RTCP socket reachable at 210.68.184.193:4007
 17:55:12.050    pjsua_acc.c  Account sip:07010174608 <at> chiefcall.com.tw added with id 0
 17:55:12.050   pjsua_core.c  TX 418 bytes Request msg REGISTER/cseq=18217 (tdta00509568) to UDP 202.153.167.4:5060:
REGISTER sip:202.153.167.4;lr SIP/2.0

Via: SIP/2.0/UDP 210.68.184.193:5060;rport;branch=z9hG4bKPjce4f8deba36b46b59af333a68e55cf55

Max-Forwards: 70

From: <sip:07010174608 <at> chiefcall.com.tw>;tag=f2571058533a4fb39514d6d0e9eb608f

To: <sip:07010174608 <at> chiefcall.com.tw>

Call-ID: e0c9fb583b784d28aceaafc0277c456f

CSeq: 18217 REGISTER

Contact: <sip:07010174608 <at> 210.68.184.193:5060>

Expires: 300

Content-Length:  0




--end msg--
 17:55:12.050    pjsua_acc.c  Registration sent
 17:55:12.050  pjsua_media.c  pjsua_set_snd_dev(): attempting to open devices  <at> 16000 Hz
 17:55:12.060     ec004F6110  AEC created, clock_rate=16000, channel=1, samples per frame=320, tail
length=200 ms, latency=100 ms
 17:55:12.060   pjsua_call.c  Making call with acc #0 to sip:0921632134 <at> chiefcall.com.tw
 17:55:12.070  pjsua_media.c  Media index 0 selected for call 0
 17:55:12.070   pjsua_core.c  TX 1038 bytes Request msg INVITE/cseq=22653 (tdta0053CF58) to UDP 202.153.199.51:5060:
INVITE sip:0921632134 <at> chiefcall.com.tw SIP/2.0

Via: SIP/2.0/UDP 210.68.184.193:5060;rport;branch=z9hG4bKPj999534a5ad9d40a7a63e575acfee67b4

Max-Forwards: 70

From: sip:07010174608 <at> chiefcall.com.tw;tag=3ff39e49434c47f99437b28e7232959e

To: sip:0921632134 <at> chiefcall.com.tw

Contact: <sip:07010174608 <at> 210.68.184.193:5060>

Call-ID: eb0d20bbf7df49959e94b51fd97e5b42

CSeq: 22653 INVITE

Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS

Supported: replaces, 100rel, norefersub

Content-Type: application/sdp

Content-Length:   465



v=0

o=- 3434291712 3434291712 IN IP4 210.68.184.193

s=pjmedia

c=IN IP4 210.68.184.193

t=0 0

a=X-nat:0

m=audio 4000 RTP/AVP 103 102 104 117 3 0 8 9 101

a=rtcp:4001 IN IP4 210.68.184.193

a=rtpmap:103 speex/16000

a=rtpmap:102 speex/8000

a=rtpmap:104 speex/32000

a=rtpmap:117 iLBC/8000

a=fmtp:117 mode=30

a=rtpmap:3 GSM/8000

a=rtpmap:0 PCMU/8000

a=rtpmap:8 PCMA/8000

a=rtpmap:9 G722/8000

a=sendrecv

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-15


--end msg--
 17:55:12.070            APP  Call 0 state=CALLING
Press 'h' to hangup all calls, 'q' to quit
 17:55:12.100   pjsua_core.c  RX 347 bytes Response msg 100/REGISTER/cseq=18217 (rdata004FD75C) from UDP 202.153.167.4:5060:
SIP/2.0 100 Trying

Via: SIP/2.0/UDP 210.68.184.193:5060;received=210.68.184.193;branch=z9hG4bKPjce4f8deba36b46b59af333a68e55cf55;rport=5060

From: <sip:07010174608 <at> chiefcall.com.tw>;tag=f2571058533a4fb39514d6d0e9eb608f

To: <sip:07010174608 <at> chiefcall.com.tw>

Call-ID: e0c9fb583b784d28aceaafc0277c456f

CSeq: 18217 REGISTER

Content-Length: 0




--end msg--
 17:55:12.100   pjsua_core.c  RX 610 bytes Response msg 407/REGISTER/cseq=18217 (rdata004FD75C) from UDP 202.153.167.4:5060:
SIP/2.0 407 Proxy Authentication Required

Via: SIP/2.0/UDP 210.68.184.193:5060;received=210.68.184.193;branch=z9hG4bKPjce4f8deba36b46b59af333a68e55cf55;rport=5060

From: <sip:07010174608 <at> chiefcall.com.tw>;tag=f2571058533a4fb39514d6d0e9eb608f

To: <sip:07010174608 <at> chiefcall.com.tw>;tag=619626302

Call-ID: e0c9fb583b784d28aceaafc0277c456f

CSeq: 18217 REGISTER

supported: com.nortelnetworks.firewall,p-3rdpartycontrol,nosec,join

proxy-authenticate: Digest realm="Realm",nonce="MTIyNTI3MzkxNzMyODYyMjRjYzBjNTNmZGQ2MmIxZTVlMGJlOTBhZGFjMzZk",stale=false,algorithm=MD5,qop="auth,auth-int"

Content-Length: 0




--end msg--
 17:55:12.100   pjsua_core.c  TX 709 bytes Request msg REGISTER/cseq=18218 (tdta00509568) to UDP 202.153.167.4:5060:
REGISTER sip:202.153.167.4;lr SIP/2.0

Via: SIP/2.0/UDP 210.68.184.193:5060;rport;branch=z9hG4bKPj775b6e3d62d64774b8987392be18a789

Max-Forwards: 70

From: <sip:07010174608 <at> chiefcall.com.tw>;tag=f2571058533a4fb39514d6d0e9eb608f

To: <sip:07010174608 <at> chiefcall.com.tw>

Call-ID: e0c9fb583b784d28aceaafc0277c456f

CSeq: 18218 REGISTER

Contact: <sip:07010174608 <at> 210.68.184.193:5060>

Expires: 300

Proxy-Authorization: Digest username="07010174608", realm="Realm",
nonce="MTIyNTI3MzkxNzMyODYyMjRjYzBjNTNmZGQ2MmIxZTVlMGJlOTBhZGFjMzZk",
uri="sip:202.153.167.4;lr", response="ed03ea882adc1b792fe0b7c642b325f9", algorithm=MD5,
cnonce="0b1d67ecef9d4248a75b379ec73dfd80", qop=auth, nc=00000001

Content-Length:  0




--end msg--
 17:55:12.160   pjsua_core.c  RX 347 bytes Response msg 100/REGISTER/cseq=18218 (rdata004FD75C) from UDP 202.153.167.4:5060:
SIP/2.0 100 Trying

Via: SIP/2.0/UDP 210.68.184.193:5060;received=210.68.184.193;branch=z9hG4bKPj775b6e3d62d64774b8987392be18a789;rport=5060

From: <sip:07010174608 <at> chiefcall.com.tw>;tag=f2571058533a4fb39514d6d0e9eb608f

To: <sip:07010174608 <at> chiefcall.com.tw>

Call-ID: e0c9fb583b784d28aceaafc0277c456f

CSeq: 18218 REGISTER

Content-Length: 0




--end msg--
 17:55:12.160   pjsua_core.c  RX 507 bytes Response msg 200/REGISTER/cseq=18218 (rdata004FD75C) from UDP 202.153.167.4:5060:
SIP/2.0 200 Registration Successful

Via: SIP/2.0/UDP 210.68.184.193:5060;received=210.68.184.193;branch=z9hG4bKPj775b6e3d62d64774b8987392be18a789;rport=5060

From: <sip:07010174608 <at> chiefcall.com.tw>;tag=f2571058533a4fb39514d6d0e9eb608f

To: <sip:07010174608 <at> chiefcall.com.tw>;tag=477497600

Call-ID: e0c9fb583b784d28aceaafc0277c456f

CSeq: 18218 REGISTER

Contact: <sip:07010174608 <at> 210.68.184.193:5060>;expires=282

supported: com.nortelnetworks.firewall,p-3rdpartycontrol,nosec,join

Content-Length: 0




--end msg--
 17:55:12.160    pjsua_acc.c  sip:07010174608 <at> chiefcall.com.tw: registration success, status=200
(Registration Successful), will re-register in 282 seconds
 17:55:12.160    pjsua_acc.c  Keep-alive timer started for acc 0, destination:202.153.167.4:5060, interval:15s
 17:55:12.571   pjsua_core.c  TX 1038 bytes Request msg INVITE/cseq=22653 (tdta0053CF58) to UDP 202.153.199.51:5060:
INVITE sip:0921632134 <at> chiefcall.com.tw SIP/2.0

Via: SIP/2.0/UDP 210.68.184.193:5060;rport;branch=z9hG4bKPj999534a5ad9d40a7a63e575acfee67b4

Max-Forwards: 70

From: sip:07010174608 <at> chiefcall.com.tw;tag=3ff39e49434c47f99437b28e7232959e

To: sip:0921632134 <at> chiefcall.com.tw

Contact: <sip:07010174608 <at> 210.68.184.193:5060>

Call-ID: eb0d20bbf7df49959e94b51fd97e5b42

CSeq: 22653 INVITE

Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS

Supported: replaces, 100rel, norefersub

Content-Type: application/sdp

Content-Length:   465



v=0

o=- 3434291712 3434291712 IN IP4 210.68.184.193

s=pjmedia

c=IN IP4 210.68.184.193

t=0 0

a=X-nat:0

m=audio 4000 RTP/AVP 103 102 104 117 3 0 8 9 101

a=rtcp:4001 IN IP4 210.68.184.193

a=rtpmap:103 speex/16000

a=rtpmap:102 speex/8000

a=rtpmap:104 speex/32000

a=rtpmap:117 iLBC/8000

a=fmtp:117 mode=30

a=rtpmap:3 GSM/8000

a=rtpmap:0 PCMU/8000

a=rtpmap:8 PCMA/8000

a=rtpmap:9 G722/8000

a=sendrecv

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-15


--end msg--
 17:55:12.871     ec004F6110  Underflow, buf_cnt=0, will generate 1 frame
 17:55:13.282     ec004F6110  Underflow, buf_cnt=0, will generate 1 frame
 17:55:13.572   pjsua_core.c  TX 1038 bytes Request msg INVITE/cseq=22653 (tdta0053CF58) to UDP 202.153.199.51:5060:
INVITE sip:0921632134 <at> chiefcall.com.tw SIP/2.0

Via: SIP/2.0/UDP 210.68.184.193:5060;rport;branch=z9hG4bKPj999534a5ad9d40a7a63e575acfee67b4

Max-Forwards: 70

From: sip:07010174608 <at> chiefcall.com.tw;tag=3ff39e49434c47f99437b28e7232959e

To: sip:0921632134 <at> chiefcall.com.tw

Contact: <sip:07010174608 <at> 210.68.184.193:5060>

Call-ID: eb0d20bbf7df49959e94b51fd97e5b42

CSeq: 22653 INVITE

Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS

Supported: replaces, 100rel, norefersub

Content-Type: application/sdp

Content-Length:   465



v=0

o=- 3434291712 3434291712 IN IP4 210.68.184.193

s=pjmedia

c=IN IP4 210.68.184.193

t=0 0

a=X-nat:0

m=audio 4000 RTP/AVP 103 102 104 117 3 0 8 9 101

a=rtcp:4001 IN IP4 210.68.184.193

a=rtpmap:103 speex/16000

a=rtpmap:102 speex/8000

a=rtpmap:104 speex/32000

a=rtpmap:117 iLBC/8000

a=fmtp:117 mode=30

a=rtpmap:3 GSM/8000

a=rtpmap:0 PCMU/8000

a=rtpmap:8 PCMA/8000

a=rtpmap:9 G722/8000

a=sendrecv

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-15


--end msg--
 17:55:14.473     ec004F6110  Underflow, buf_cnt=0, will generate 1 frame
 17:55:15.275     ec004F6110  Underflow, buf_cnt=0, will generate 1 frame
 17:55:15.575   pjsua_core.c  TX 1038 bytes Request msg INVITE/cseq=22653 (tdta0053CF58) to UDP 202.153.199.51:5060:
INVITE sip:0921632134 <at> chiefcall.com.tw SIP/2.0

Via: SIP/2.0/UDP 210.68.184.193:5060;rport;branch=z9hG4bKPj999534a5ad9d40a7a63e575acfee67b4

Max-Forwards: 70

From: sip:07010174608 <at> chiefcall.com.tw;tag=3ff39e49434c47f99437b28e7232959e

To: sip:0921632134 <at> chiefcall.com.tw

Contact: <sip:07010174608 <at> 210.68.184.193:5060>

Call-ID: eb0d20bbf7df49959e94b51fd97e5b42

CSeq: 22653 INVITE

Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS

Supported: replaces, 100rel, norefersub

Content-Type: application/sdp

Content-Length:   465



v=0

o=- 3434291712 3434291712 IN IP4 210.68.184.193

s=pjmedia

c=IN IP4 210.68.184.193

t=0 0

a=X-nat:0

m=audio 4000 RTP/AVP 103 102 104 117 3 0 8 9 101

a=rtcp:4001 IN IP4 210.68.184.193

a=rtpmap:103 speex/16000

a=rtpmap:102 speex/8000

a=rtpmap:104 speex/32000

a=rtpmap:117 iLBC/8000

a=fmtp:117 mode=30

a=rtpmap:3 GSM/8000

a=rtpmap:0 PCMU/8000

a=rtpmap:8 PCMA/8000

a=rtpmap:9 G722/8000

a=sendrecv

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-15


--end msg--
 17:55:16.076     ec004F6110  Underflow, buf_cnt=0, will generate 1 frame
 17:55:16.877     ec004F6110  Underflow, buf_cnt=0, will generate 1 frame
 17:55:17.217   sound_port.c  EC suspended because of inactivity
 17:55:19.581   pjsua_core.c  TX 1038 bytes Request msg INVITE/cseq=22653 (tdta0053CF58) to UDP 202.153.199.51:5060:
INVITE sip:0921632134 <at> chiefcall.com.tw SIP/2.0

Via: SIP/2.0/UDP 210.68.184.193:5060;rport;branch=z9hG4bKPj999534a5ad9d40a7a63e575acfee67b4

Max-Forwards: 70

From: sip:07010174608 <at> chiefcall.com.tw;tag=3ff39e49434c47f99437b28e7232959e

To: sip:0921632134 <at> chiefcall.com.tw

Contact: <sip:07010174608 <at> 210.68.184.193:5060>

Call-ID: eb0d20bbf7df49959e94b51fd97e5b42

CSeq: 22653 INVITE

Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS

Supported: replaces, 100rel, norefersub

Content-Type: application/sdp

Content-Length:   465



v=0

o=- 3434291712 3434291712 IN IP4 210.68.184.193

s=pjmedia

c=IN IP4 210.68.184.193

t=0 0

a=X-nat:0

m=audio 4000 RTP/AVP 103 102 104 117 3 0 8 9 101

a=rtcp:4001 IN IP4 210.68.184.193

a=rtpmap:103 speex/16000

a=rtpmap:102 speex/8000

a=rtpmap:104 speex/32000

a=rtpmap:117 iLBC/8000

a=fmtp:117 mode=30

a=rtpmap:3 GSM/8000

a=rtpmap:0 PCMU/8000

a=rtpmap:8 PCMA/8000

a=rtpmap:9 G722/8000

a=sendrecv

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-15


--end msg--
 17:55:27.582   pjsua_core.c  TX 1038 bytes Request msg INVITE/cseq=22653 (tdta0053CF58) to UDP 202.153.199.51:5060:
INVITE sip:0921632134 <at> chiefcall.com.tw SIP/2.0

Via: SIP/2.0/UDP 210.68.184.193:5060;rport;branch=z9hG4bKPj999534a5ad9d40a7a63e575acfee67b4

Max-Forwards: 70

From: sip:07010174608 <at> chiefcall.com.tw;tag=3ff39e49434c47f99437b28e7232959e

To: sip:0921632134 <at> chiefcall.com.tw

Contact: <sip:07010174608 <at> 210.68.184.193:5060>

Call-ID: eb0d20bbf7df49959e94b51fd97e5b42

CSeq: 22653 INVITE

Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS

Supported: replaces, 100rel, norefersub

Content-Type: application/sdp

Content-Length:   465



v=0

o=- 3434291712 3434291712 IN IP4 210.68.184.193

s=pjmedia

c=IN IP4 210.68.184.193

t=0 0

a=X-nat:0

m=audio 4000 RTP/AVP 103 102 104 117 3 0 8 9 101

a=rtcp:4001 IN IP4 210.68.184.193

a=rtpmap:103 speex/16000

a=rtpmap:102 speex/8000

a=rtpmap:104 speex/32000

a=rtpmap:117 iLBC/8000

a=fmtp:117 mode=30

a=rtpmap:3 GSM/8000

a=rtpmap:0 PCMU/8000

a=rtpmap:8 PCMA/8000

a=rtpmap:9 G722/8000

a=sendrecv

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-15


--end msg--
 17:55:11.719 os_core_win32.  pjlib 1.0 for win32 initialized
 17:55:11.730 sip_endpoint.c  Creating endpoint instance...
 17:55:11.730          pjlib  WinNT IOCP I/O Queue created (003CD288)
 17:55:11.730 sip_endpoint.c  Module "mod-msg-print" registered
 17:55:11.730 sip_transport.  Transport manager created.
 17:55:11.730 sip_endpoint.c  Module "mod-pjsua-log" registered
 17:55:11.730 sip_endpoint.c  Module "mod-tsx-layer" registered
 17:55:11.730 sip_endpoint.c  Module "mod-stateful-util" registered
 17:55:11.730 sip_endpoint.c  Module "mod-ua" registered
 17:55:11.730 sip_endpoint.c  Module "mod-100rel" registered
 17:55:11.730 sip_endpoint.c  Module "mod-pjsua" registered
 17:55:11.730 sip_endpoint.c  Module "mod-invite" registered
 17:55:12.020      pasound.c  PortAudio sound library initialized, status=0
 17:55:12.020      pasound.c  PortAudio host api count=3
 17:55:12.020      pasound.c  Sound device count=12
 17:55:12.020          pjlib  WinNT IOCP I/O Queue created (004F15FC)
 17:55:12.020 sip_endpoint.c  Module "mod-evsub" registered
 17:55:12.020 sip_endpoint.c  Module "mod-presence" registered
 17:55:12.020 sip_endpoint.c  Module "mod-refer" registered
 17:55:12.020 sip_endpoint.c  Module "mod-pjsua-pres" registered
 17:55:12.020 sip_endpoint.c  Module "mod-pjsua-im" registered
 17:55:12.020 sip_endpoint.c  Module "mod-pjsua-options" registered
 17:55:12.020   pjsua_core.c  1 SIP worker threads created
 17:55:12.020   pjsua_core.c  pjsua version 1.0 for win32 initialized
 17:55:12.040   pjsua_core.c  SIP UDP socket reachable at 210.68.184.193:5060
 17:55:12.040    udp004FD2E8  SIP UDP transport started, published address is 210.68.184.193:5060
 17:55:12.040  pjsua_media.c  RTP socket reachable at 210.68.184.193:4000
 17:55:12.040  pjsua_media.c  RTCP socket reachable at 210.68.184.193:4001
 17:55:12.040  pjsua_media.c  RTP socket reachable at 210.68.184.193:4002
 17:55:12.040  pjsua_media.c  RTCP socket reachable at 210.68.184.193:4003
 17:55:12.050  pjsua_media.c  RTP socket reachable at 210.68.184.193:4004
 17:55:12.050  pjsua_media.c  RTCP socket reachable at 210.68.184.193:4005
 17:55:12.050  pjsua_media.c  RTP socket reachable at 210.68.184.193:4006
 17:55:12.050  pjsua_media.c  RTCP socket reachable at 210.68.184.193:4007
 17:55:12.050    pjsua_acc.c  Account sip:07010174608 <at> chiefcall.com.tw added with id 0
 17:55:12.050   pjsua_core.c  TX 418 bytes Request msg REGISTER/cseq=18217 (tdta00509568) to UDP 202.153.167.4:5060:
REGISTER sip:202.153.167.4;lr SIP/2.0

Via: SIP/2.0/UDP 210.68.184.193:5060;rport;branch=z9hG4bKPjce4f8deba36b46b59af333a68e55cf55

Max-Forwards: 70

From: <sip:07010174608 <at> chiefcall.com.tw>;tag=f2571058533a4fb39514d6d0e9eb608f

To: <sip:07010174608 <at> chiefcall.com.tw>

Call-ID: e0c9fb583b784d28aceaafc0277c456f

CSeq: 18217 REGISTER

Contact: <sip:07010174608 <at> 210.68.184.193:5060>

Expires: 300

Content-Length:  0




--end msg--
 17:55:12.050    pjsua_acc.c  Registration sent
 17:55:12.050  pjsua_media.c  pjsua_set_snd_dev(): attempting to open devices  <at> 16000 Hz
 17:55:12.060     ec004F6110  AEC created, clock_rate=16000, channel=1, samples per frame=320, tail
length=200 ms, latency=100 ms
 17:55:12.060   pjsua_call.c  Making call with acc #0 to sip:0921632134 <at> chiefcall.com.tw
 17:55:12.070  pjsua_media.c  Media index 0 selected for call 0
 17:55:12.070   pjsua_core.c  TX 1038 bytes Request msg INVITE/cseq=22653 (tdta0053CF58) to UDP 202.153.199.51:5060:
INVITE sip:0921632134 <at> chiefcall.com.tw SIP/2.0

Via: SIP/2.0/UDP 210.68.184.193:5060;rport;branch=z9hG4bKPj999534a5ad9d40a7a63e575acfee67b4

Max-Forwards: 70

From: sip:07010174608 <at> chiefcall.com.tw;tag=3ff39e49434c47f99437b28e7232959e

To: sip:0921632134 <at> chiefcall.com.tw

Contact: <sip:07010174608 <at> 210.68.184.193:5060>

Call-ID: eb0d20bbf7df49959e94b51fd97e5b42

CSeq: 22653 INVITE

Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS

Supported: replaces, 100rel, norefersub

Content-Type: application/sdp

Content-Length:   465



v=0

o=- 3434291712 3434291712 IN IP4 210.68.184.193

s=pjmedia

c=IN IP4 210.68.184.193

t=0 0

a=X-nat:0

m=audio 4000 RTP/AVP 103 102 104 117 3 0 8 9 101

a=rtcp:4001 IN IP4 210.68.184.193

a=rtpmap:103 speex/16000

a=rtpmap:102 speex/8000

a=rtpmap:104 speex/32000

a=rtpmap:117 iLBC/8000

a=fmtp:117 mode=30

a=rtpmap:3 GSM/8000

a=rtpmap:0 PCMU/8000

a=rtpmap:8 PCMA/8000

a=rtpmap:9 G722/8000

a=sendrecv

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-15


--end msg--
 17:55:12.070            APP  Call 0 state=CALLING
Press 'h' to hangup all calls, 'q' to quit
 17:55:12.100   pjsua_core.c  RX 347 bytes Response msg 100/REGISTER/cseq=18217 (rdata004FD75C) from UDP 202.153.167.4:5060:
SIP/2.0 100 Trying

Via: SIP/2.0/UDP 210.68.184.193:5060;received=210.68.184.193;branch=z9hG4bKPjce4f8deba36b46b59af333a68e55cf55;rport=5060

From: <sip:07010174608 <at> chiefcall.com.tw>;tag=f2571058533a4fb39514d6d0e9eb608f

To: <sip:07010174608 <at> chiefcall.com.tw>

Call-ID: e0c9fb583b784d28aceaafc0277c456f

CSeq: 18217 REGISTER

Content-Length: 0




--end msg--
 17:55:12.100   pjsua_core.c  RX 610 bytes Response msg 407/REGISTER/cseq=18217 (rdata004FD75C) from UDP 202.153.167.4:5060:
SIP/2.0 407 Proxy Authentication Required

Via: SIP/2.0/UDP 210.68.184.193:5060;received=210.68.184.193;branch=z9hG4bKPjce4f8deba36b46b59af333a68e55cf55;rport=5060

From: <sip:07010174608 <at> chiefcall.com.tw>;tag=f2571058533a4fb39514d6d0e9eb608f

To: <sip:07010174608 <at> chiefcall.com.tw>;tag=619626302

Call-ID: e0c9fb583b784d28aceaafc0277c456f

CSeq: 18217 REGISTER

supported: com.nortelnetworks.firewall,p-3rdpartycontrol,nosec,join

proxy-authenticate: Digest realm="Realm",nonce="MTIyNTI3MzkxNzMyODYyMjRjYzBjNTNmZGQ2MmIxZTVlMGJlOTBhZGFjMzZk",stale=false,algorithm=MD5,qop="auth,auth-int"

Content-Length: 0




--end msg--
 17:55:12.100   pjsua_core.c  TX 709 bytes Request msg REGISTER/cseq=18218 (tdta00509568) to UDP 202.153.167.4:5060:
REGISTER sip:202.153.167.4;lr SIP/2.0

Via: SIP/2.0/UDP 210.68.184.193:5060;rport;branch=z9hG4bKPj775b6e3d62d64774b8987392be18a789

Max-Forwards: 70

From: <sip:07010174608 <at> chiefcall.com.tw>;tag=f2571058533a4fb39514d6d0e9eb608f

To: <sip:07010174608 <at> chiefcall.com.tw>

Call-ID: e0c9fb583b784d28aceaafc0277c456f

CSeq: 18218 REGISTER

Contact: <sip:07010174608 <at> 210.68.184.193:5060>

Expires: 300

Proxy-Authorization: Digest username="07010174608", realm="Realm",
nonce="MTIyNTI3MzkxNzMyODYyMjRjYzBjNTNmZGQ2MmIxZTVlMGJlOTBhZGFjMzZk",
uri="sip:202.153.167.4;lr", response="ed03ea882adc1b792fe0b7c642b325f9", algorithm=MD5,
cnonce="0b1d67ecef9d4248a75b379ec73dfd80", qop=auth, nc=00000001

Content-Length:  0




--end msg--
 17:55:12.160   pjsua_core.c  RX 347 bytes Response msg 100/REGISTER/cseq=18218 (rdata004FD75C) from UDP 202.153.167.4:5060:
SIP/2.0 100 Trying

Via: SIP/2.0/UDP 210.68.184.193:5060;received=210.68.184.193;branch=z9hG4bKPj775b6e3d62d64774b8987392be18a789;rport=5060

From: <sip:07010174608 <at> chiefcall.com.tw>;tag=f2571058533a4fb39514d6d0e9eb608f

To: <sip:07010174608 <at> chiefcall.com.tw>

Call-ID: e0c9fb583b784d28aceaafc0277c456f

CSeq: 18218 REGISTER

Content-Length: 0




--end msg--
 17:55:12.160   pjsua_core.c  RX 507 bytes Response msg 200/REGISTER/cseq=18218 (rdata004FD75C) from UDP 202.153.167.4:5060:
SIP/2.0 200 Registration Successful

Via: SIP/2.0/UDP 210.68.184.193:5060;received=210.68.184.193;branch=z9hG4bKPj775b6e3d62d64774b8987392be18a789;rport=5060

From: <sip:07010174608 <at> chiefcall.com.tw>;tag=f2571058533a4fb39514d6d0e9eb608f

To: <sip:07010174608 <at> chiefcall.com.tw>;tag=477497600

Call-ID: e0c9fb583b784d28aceaafc0277c456f

CSeq: 18218 REGISTER

Contact: <sip:07010174608 <at> 210.68.184.193:5060>;expires=282

supported: com.nortelnetworks.firewall,p-3rdpartycontrol,nosec,join

Content-Length: 0




--end msg--
 17:55:12.160    pjsua_acc.c  sip:07010174608 <at> chiefcall.com.tw: registration success, status=200
(Registration Successful), will re-register in 282 seconds
 17:55:12.160    pjsua_acc.c  Keep-alive timer started for acc 0, destination:202.153.167.4:5060, interval:15s
 17:55:12.571   pjsua_core.c  TX 1038 bytes Request msg INVITE/cseq=22653 (tdta0053CF58) to UDP 202.153.199.51:5060:
INVITE sip:0921632134 <at> chiefcall.com.tw SIP/2.0

Via: SIP/2.0/UDP 210.68.184.193:5060;rport;branch=z9hG4bKPj999534a5ad9d40a7a63e575acfee67b4

Max-Forwards: 70

From: sip:07010174608 <at> chiefcall.com.tw;tag=3ff39e49434c47f99437b28e7232959e

To: sip:0921632134 <at> chiefcall.com.tw

Contact: <sip:07010174608 <at> 210.68.184.193:5060>

Call-ID: eb0d20bbf7df49959e94b51fd97e5b42

CSeq: 22653 INVITE

Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS

Supported: replaces, 100rel, norefersub

Content-Type: application/sdp

Content-Length:   465



v=0

o=- 3434291712 3434291712 IN IP4 210.68.184.193

s=pjmedia

c=IN IP4 210.68.184.193

t=0 0

a=X-nat:0

m=audio 4000 RTP/AVP 103 102 104 117 3 0 8 9 101

a=rtcp:4001 IN IP4 210.68.184.193

a=rtpmap:103 speex/16000

a=rtpmap:102 speex/8000

a=rtpmap:104 speex/32000

a=rtpmap:117 iLBC/8000

a=fmtp:117 mode=30

a=rtpmap:3 GSM/8000

a=rtpmap:0 PCMU/8000

a=rtpmap:8 PCMA/8000

a=rtpmap:9 G722/8000

a=sendrecv

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-15


--end msg--
 17:55:12.871     ec004F6110  Underflow, buf_cnt=0, will generate 1 frame
 17:55:13.282     ec004F6110  Underflow, buf_cnt=0, will generate 1 frame
 17:55:13.572   pjsua_core.c  TX 1038 bytes Request msg INVITE/cseq=22653 (tdta0053CF58) to UDP 202.153.199.51:5060:
INVITE sip:0921632134 <at> chiefcall.com.tw SIP/2.0

Via: SIP/2.0/UDP 210.68.184.193:5060;rport;branch=z9hG4bKPj999534a5ad9d40a7a63e575acfee67b4

Max-Forwards: 70

From: sip:07010174608 <at> chiefcall.com.tw;tag=3ff39e49434c47f99437b28e7232959e

To: sip:0921632134 <at> chiefcall.com.tw

Contact: <sip:07010174608 <at> 210.68.184.193:5060>

Call-ID: eb0d20bbf7df49959e94b51fd97e5b42

CSeq: 22653 INVITE

Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS

Supported: replaces, 100rel, norefersub

Content-Type: application/sdp

Content-Length:   465



v=0

o=- 3434291712 3434291712 IN IP4 210.68.184.193

s=pjmedia

c=IN IP4 210.68.184.193

t=0 0

a=X-nat:0

m=audio 4000 RTP/AVP 103 102 104 117 3 0 8 9 101

a=rtcp:4001 IN IP4 210.68.184.193

a=rtpmap:103 speex/16000

a=rtpmap:102 speex/8000

a=rtpmap:104 speex/32000

a=rtpmap:117 iLBC/8000

a=fmtp:117 mode=30

a=rtpmap:3 GSM/8000

a=rtpmap:0 PCMU/8000

a=rtpmap:8 PCMA/8000

a=rtpmap:9 G722/8000

a=sendrecv

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-15


--end msg--
 17:55:14.473     ec004F6110  Underflow, buf_cnt=0, will generate 1 frame
 17:55:15.275     ec004F6110  Underflow, buf_cnt=0, will generate 1 frame
 17:55:15.575   pjsua_core.c  TX 1038 bytes Request msg INVITE/cseq=22653 (tdta0053CF58) to UDP 202.153.199.51:5060:
INVITE sip:0921632134 <at> chiefcall.com.tw SIP/2.0

Via: SIP/2.0/UDP 210.68.184.193:5060;rport;branch=z9hG4bKPj999534a5ad9d40a7a63e575acfee67b4

Max-Forwards: 70

From: sip:07010174608 <at> chiefcall.com.tw;tag=3ff39e49434c47f99437b28e7232959e

To: sip:0921632134 <at> chiefcall.com.tw

Contact: <sip:07010174608 <at> 210.68.184.193:5060>

Call-ID: eb0d20bbf7df49959e94b51fd97e5b42

CSeq: 22653 INVITE

Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS

Supported: replaces, 100rel, norefersub

Content-Type: application/sdp

Content-Length:   465



v=0

o=- 3434291712 3434291712 IN IP4 210.68.184.193

s=pjmedia

c=IN IP4 210.68.184.193

t=0 0

a=X-nat:0

m=audio 4000 RTP/AVP 103 102 104 117 3 0 8 9 101

a=rtcp:4001 IN IP4 210.68.184.193

a=rtpmap:103 speex/16000

a=rtpmap:102 speex/8000

a=rtpmap:104 speex/32000

a=rtpmap:117 iLBC/8000

a=fmtp:117 mode=30

a=rtpmap:3 GSM/8000

a=rtpmap:0 PCMU/8000

a=rtpmap:8 PCMA/8000

a=rtpmap:9 G722/8000

a=sendrecv

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-15


--end msg--
 17:55:16.076     ec004F6110  Underflow, buf_cnt=0, will generate 1 frame
 17:55:16.877     ec004F6110  Underflow, buf_cnt=0, will generate 1 frame
 17:55:17.217   sound_port.c  EC suspended because of inactivity
 17:55:19.581   pjsua_core.c  TX 1038 bytes Request msg INVITE/cseq=22653 (tdta0053CF58) to UDP 202.153.199.51:5060:
INVITE sip:0921632134 <at> chiefcall.com.tw SIP/2.0

Via: SIP/2.0/UDP 210.68.184.193:5060;rport;branch=z9hG4bKPj999534a5ad9d40a7a63e575acfee67b4

Max-Forwards: 70

From: sip:07010174608 <at> chiefcall.com.tw;tag=3ff39e49434c47f99437b28e7232959e

To: sip:0921632134 <at> chiefcall.com.tw

Contact: <sip:07010174608 <at> 210.68.184.193:5060>

Call-ID: eb0d20bbf7df49959e94b51fd97e5b42

CSeq: 22653 INVITE

Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS

Supported: replaces, 100rel, norefersub

Content-Type: application/sdp

Content-Length:   465



v=0

o=- 3434291712 3434291712 IN IP4 210.68.184.193

s=pjmedia

c=IN IP4 210.68.184.193

t=0 0

a=X-nat:0

m=audio 4000 RTP/AVP 103 102 104 117 3 0 8 9 101

a=rtcp:4001 IN IP4 210.68.184.193

a=rtpmap:103 speex/16000

a=rtpmap:102 speex/8000

a=rtpmap:104 speex/32000

a=rtpmap:117 iLBC/8000

a=fmtp:117 mode=30

a=rtpmap:3 GSM/8000

a=rtpmap:0 PCMU/8000

a=rtpmap:8 PCMA/8000

a=rtpmap:9 G722/8000

a=sendrecv

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-15


--end msg--
 17:55:27.582   pjsua_core.c  TX 1038 bytes Request msg INVITE/cseq=22653 (tdta0053CF58) to UDP 202.153.199.51:5060:
INVITE sip:0921632134 <at> chiefcall.com.tw SIP/2.0

Via: SIP/2.0/UDP 210.68.184.193:5060;rport;branch=z9hG4bKPj999534a5ad9d40a7a63e575acfee67b4

Max-Forwards: 70

From: sip:07010174608 <at> chiefcall.com.tw;tag=3ff39e49434c47f99437b28e7232959e

To: sip:0921632134 <at> chiefcall.com.tw

Contact: <sip:07010174608 <at> 210.68.184.193:5060>

Call-ID: eb0d20bbf7df49959e94b51fd97e5b42

CSeq: 22653 INVITE

Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS

Supported: replaces, 100rel, norefersub

Content-Type: application/sdp

Content-Length:   465



v=0

o=- 3434291712 3434291712 IN IP4 210.68.184.193

s=pjmedia

c=IN IP4 210.68.184.193

t=0 0

a=X-nat:0

m=audio 4000 RTP/AVP 103 102 104 117 3 0 8 9 101

a=rtcp:4001 IN IP4 210.68.184.193

a=rtpmap:103 speex/16000

a=rtpmap:102 speex/8000

a=rtpmap:104 speex/32000

a=rtpmap:117 iLBC/8000

a=fmtp:117 mode=30

a=rtpmap:3 GSM/8000

a=rtpmap:0 PCMU/8000

a=rtpmap:8 PCMA/8000

a=rtpmap:9 G722/8000

a=sendrecv

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-15


--end msg--
Nigel Hsiung | 30 Oct 03:19 2008
Picon

Re: sending own RTP packet when using PJSUA

Hi Calvin,

This is from the 0.8 days - http://osdir.com/ml/voip.pjsip/2008-06/msg00092.html
And as Nanang said, there will be waste of resource as well as having to sacrifice some of the features of PJMedia such as RTP log report, conference bridge etc. 

best,
Nigel

> Date: Wed, 29 Oct 2008 22:40:19 +0700
> From: nanang <at> pjsip.org
> To: pjsip <at> lists.pjsip.org
> Subject: Re: [pjsip] sending own RTP packet when using PJSUA
>
> Hi,
>
> AFAIK, basically there is no easy & proper way. However if you want to
> force it using pjsua, perhaps you can use transport adapter (to
> replace the packets) & disabling VAD may be necessary, there may be
> waste of resources.
>
> Regards,
& gt; nanang
>
>
> On Wed, Oct 29, 2008 at 10:09 AM, CalvIA IA <calvia08 <at> gmail.com> wrote:
> > Hi,
> >
> > Is any way to send out my own rtp packets when using pjsua?
> >
> > for eg: inserting my own packets to the media transport.
> >
> > Regards,
> > Calvin
> > _______________________________________________
> > 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

Discover the new Windows Vista Learn more!
<div>
Hi Calvin,<br><br>This is from the 0.8 days - http://osdir.com/ml/voip.pjsip/2008-06/msg00092.html<br>And as Nanang said, there will be waste of resource as well as having to sacrifice some of the features of PJMedia such as RTP log report, conference bridge etc.&nbsp; <br><br>best,<br>Nigel<br><br>&gt; Date: Wed, 29 Oct 2008 22:40:19 +0700<br>&gt; From: nanang <at> pjsip.org<br>&gt; To: pjsip <at> lists.pjsip.org<br>&gt; Subject: Re: [pjsip] sending own RTP packet when using PJSUA<br>&gt; <br>&gt; Hi,<br>&gt; <br>&gt; AFAIK, basically there is no easy &amp; proper way. However if you want to<br>&gt; force it using pjsua, perhaps you can use transport adapter (to<br>&gt; replace the packets) &amp; disabling VAD may be necessary, there may be<br>&gt; waste of resources.<br>&gt; <br>&gt; Regards,<br>&amp;
 gt; nanang<br>&gt; <br>&gt; <br>&gt; On Wed, Oct 29, 2008 at 10:09 AM, CalvIA IA &lt;calvia08 <at> gmail.com&gt; wrote:<br>&gt; &gt; Hi,<br>&gt; &gt;<br>&gt; &gt; Is any way to send out my own rtp packets when using pjsua?<br>&gt; &gt;<br>&gt; &gt; for eg: inserting my own packets to the media transport.<br>&gt; &gt;<br>&gt; &gt; Regards,<br>&gt; &gt; Calvin<br>&gt; &gt; _______________________________________________<br>&gt; &gt; Visit our blog: http://blog.pjsip.org<br>&gt; &gt;<br>&gt; &gt; pjsip mailing list<br>&gt; &gt; pjsip <at> lists.pjsip.org<br>&gt; &gt; http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org<br>&gt; &gt;<br>&gt; &gt;<br>&gt; <br>&gt; _______________________________________________<br>&gt; Visit our blog: http://blog.pjsip.org<br>&gt; <br>&gt; pjsip mailing list<br>&gt; pjsip <at> lists.pjsip.org<br>&gt; http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org<br><br>Discover the new Windows Vista <a href="http://search.msn.com/results.aspx?q=windows+vista&amp;mkt=en-US&amp;form=QBRE" target="_new">Learn more!</a>
</div>
johnson elangbam | 30 Oct 14:52 2008
Picon

Can we used Intel IPP to add video on PJSIP?

Hi all,
           Can we used Intel IPP to add video on pjsip, if possible, please tell me the steps on how to add it or please tell me the easiest alternatives on how to start.


Regards,
Elangbam Johnson

<div><p>Hi all,<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Can we used Intel IPP to add video on pjsip, if possible, please tell me the steps on how to add it or please tell me the easiest alternatives on how to start.<br><br><br>Regards,<br>Elangbam Johnson<br></p></div>
Subramanian Swaminathan | 30 Oct 17:19 2008

Media Candidate for Video

Hi there,

   Not sure if this question has been answered before but I need to do the
following. 

   I'm using pjsip-0.8.0 code base and using STUN/ICE for the media, the
current SDP header only creates ICE candidates for audio. I need to add
another Candidate for Video as well. How do we go about doing this or we can
get away with just one ICE candidate that's created?

I would appreciate any help.

Regards,
-Sub 

katjusha KATJUSHA | 30 Oct 18:21 2008
Picon

send multiple stun request

Hello people,

Could everyone tell me how to use a stun session to send multiple stun_request to different destinations?
(in order to implement an UDP hole punch)?
My problem is that I can't get the retransmission of request not completed  ... so the HolePunch fails.
I wanna send the requests so they can be processed simultaneously...

<div><p>Hello people,<br><br>Could everyone tell me how to use a stun session to send multiple stun_request to different destinations?<br>(in order to implement an UDP hole punch)?<br>My problem is that I can't get the retransmission of request not completed&nbsp; ... so the HolePunch fails.<br>
I wanna send the requests so they can be processed simultaneously...<br></p></div>

Gmane