Ooh323<->pjsip I forget my configure

Asterisk Asterisk Support
1

I got few succeed ooh323<->pjsip calls in both directions today. but I change the configure file, then I lost it , I forgot what I did with it. now calls have one way sound. I remember when calls succeed the rtp channel should behind the ringing. here is the one way sound call log.

*CLI> – Executing [1001@from-gnugk:1] Dial(“OOH323/Win10-2021KVQWA-0”, “PJSIP/1001”) in new stack
– Called PJSIP/1001
– PJSIP/1001-00000000 is ringing
> 0x7fc6c000b970 – Strict RTP learning after remote address set to: 172.16.0.4:1026
> 0x7fc6c000b970 – Strict RTP switching to RTP target address 172.16.0.4:1026 as source
> 0x7fc6c000b970 – Strict RTP learning complete - Locking on source address 172.16.0.4:1026
> 0x7fc6a8007a20 – Strict RTP learning after remote address set to: 103.57.12.21:4000
– PJSIP/1001-00000000 answered OOH323/Win10-2021KVQWA-0
– Channel PJSIP/1001-00000000 joined ‘simple_bridge’ basic-bridge <4d1d06ff-5f0c-42b5-8889-78b898e743cb>
– Channel OOH323/Win10-2021KVQWA-0 joined ‘simple_bridge’ basic-bridge <4d1d06ff-5f0c-42b5-8889-78b898e743cb>
> 0x7fc6a8007a20 – Strict RTP qualifying stream type: audio
> 0x7fc6a8007a20 – Strict RTP switching source address to 103.57.12.21:28881
> 0x7fc6a8007a20 – Strict RTP learning complete - Locking on source address 103.57.12.21:28881

=

I remember these
> 0x7fc6c000b970 – Strict RTP learning after remote address set to: 172.16.0.4:1026
> 0x7fc6c000b970 – Strict RTP switching to RTP target address 172.16.0.4:1026 as source
> 0x7fc6c000b970 – Strict RTP learning complete - Locking on source address 172.16.0.4:1026
> 0x7fc6a8007a20 – Strict RTP learning after remote address set to: 103.57.12.21:4000
should be behind
– PJSIP/1001-00000000 answered OOH323/Win10-2021KVQWA-0
then the call succeed.

[general]
port=1730
bindaddr=0.0.0.0
gateway=yes
faststart=no
h245tunneling=yes
mediawaitforconnect=yes

h323id=ObjSysAsterisk
e164=8000
callerid=asterisk
gatekeeper = 172.16.0.4
AllowGKRouted = yes
logfile=/var/log/asterisk/h323_log
tracelevel=5
context=default
disallow=all
allow=ulaw

[Win10-2021KVQWA] ;polycom
type=user
context=from-gnugk
disallow=all
allow=ulaw

[h323peer] ;h323 outgoing
IP=172.16.0.4
port=1720
type=peer
h323id=gnugk
disallow=all
allow=ulaw

2

now the h323->sip call have one way rtp connection. and auto hang up in 60 seconds.

3

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.