[Spce-user] SIPWISE Configuration Help
Muazu Musa Muhd
muazumusamuhd at gmail.com
Thu Feb 25 15:37:10 EST 2021
Hello, Please I really need your help setting up SIPWISE on AWS EC2 for my
small team, I tried using different versions and followed the respective
procedures stated in the Handbook all to no avail, I really ran out of
options, the problem I am facing is that everything would work but there
will be no RTP packets exchanged as it was pointed out to me in this issue,
I am new to this platform but I am trying my best to learn, I really hope
someone can point me in the right direction to set it up.
I use eu-west 1region
I used almost all images you provided on the region starting
from ami-8bef6cfc
to this ami-0a595d7ac0266d740
I set up all ports correctly
TCP port 22 (SSH)
– TCP port 443 (HTTPS/CSC)
– TCP port 1443 (Admin Panel)
– TCP port 5060 (SIP/TCP)
– UDP port 5060 (SIP/UDP)
– TCP port 5061 (SIP/TLS)
– TCP port 5222 (SIP)
– TCP port 5269 (SIP)
– UDP port 30000:44999 (RTP)
I launch my instance and SSH in to it
I advertise my public IP with
ngcp-network --set-interface=eth0 --advertised-ip=54.78.110.45
I apply the changes with
ngcpcfg apply ’add advertised-ip on interface eth0’
Then I add network configuration like
ngcp-network --set-interface=eth0 --ip=auto --netmask=auto --hwaddr=auto
ngcp-network --move-from=lo --move-to=eth0 --type=web_ext --type=sip_ext
--type=rtp_ext --type=ssh_ext --type=web_int
my network.yml is like
---
hosts:
self:
dbnode: '1'
ens5:
advertised_ip:
- 54.78.110.45
dns_nameservers:
- 10.0.0.2
gateway: 10.0.0.1
hwaddr: 02:9c:1d:a2:a2:6d
ip: 172.31.3.101
netmask: 255.255.240.0
type:
- web_ext
- sip_ext
- rtp_ext
- web_int
- ssh_ext
interfaces:
- lo
- ens5
lo:
cluster_sets:
- default
ip: 127.0.0.1
netmask: 255.255.255.0
shared_ip: []
shared_v6ip: []
type:
- sip_int
- ha_int
- aux_ext
- ssh_ext
- api_int
- rtp_int
- stor_int
v6ip: ::1
v6netmask: 128
role:
- proxy
- lb
- mgmt
- rtp
- db
- storage
status: online
swraiddevices: []
sysdescr: ''
syslocation: ''
sysname: ''
And i apply the changes with
ngcpcfg apply ’change network configuration’
So I do everything like the Handbook suggested but everything I do is
turning the same result.
I have attached my RTP log
I really wish you could help me. Thank you so much.
--
Muazu Musa Muhammad
Vannia Technologies LLC.
Twiiter: @MuazuMusaMuhd
LinkedIn: Muazu Musa Muhammad
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20210225/b01d63c0/attachment-0001.html>
-------------- next part --------------
Nov 30 12:37:38 ip-10-0-0-227 rtpengine[30268]: INFO: Generating new DTLS certificate
Nov 30 12:37:38 ip-10-0-0-227 rtpengine[30268]: INFO: Startup complete, version 9.1.1.2+0~mr9.1.1.2
Nov 30 12:37:41 ip-10-0-0-227 rtpengine[30268]: INFO: Received command 'ping' from 127.0.0.1:49411
Nov 30 12:37:41 ip-10-0-0-227 rtpengine[30268]: INFO: Replying to 'ping' from 127.0.0.1:49411 (elapsed time 0.000000 sec)
Nov 30 12:38:20 ip-10-0-0-227 rtpengine[30268]: INFO: Version 9.1.1.2+0~mr9.1.1.2 shutting down
Nov 30 12:38:21 ip-10-0-0-227 rtpengine[1957]: INFO: Generating new DTLS certificate
Nov 30 12:38:22 ip-10-0-0-227 rtpengine[1957]: INFO: Startup complete, version 9.1.1.2+0~mr9.1.1.2
Nov 30 12:38:22 ip-10-0-0-227 rtpengine[1957]: INFO: Received command 'ping' from 127.0.0.1:54131
Nov 30 12:38:22 ip-10-0-0-227 rtpengine[1957]: INFO: Replying to 'ping' from 127.0.0.1:54131 (elapsed time 0.000000 sec)
Feb 25 16:34:20 ip-172-31-3-101 rtpengine[694]: INFO: Generating new DTLS certificate
Feb 25 16:34:21 ip-172-31-3-101 rtpengine[694]: INFO: Startup complete, version 9.1.1.2+0~mr9.1.1.2
Feb 25 16:34:22 ip-172-31-3-101 rtpengine[694]: INFO: Received command 'ping' from 127.0.0.1:52244
Feb 25 16:34:22 ip-172-31-3-101 rtpengine[694]: INFO: Replying to 'ping' from 127.0.0.1:52244 (elapsed time 0.000000 sec)
Feb 25 16:35:08 ip-172-31-3-101 rtpengine[694]: INFO: Version 9.1.1.2+0~mr9.1.1.2 shutting down
Feb 25 16:35:11 ip-172-31-3-101 rtpengine[4437]: INFO: Generating new DTLS certificate
Feb 25 16:35:12 ip-172-31-3-101 rtpengine[4437]: INFO: Startup complete, version 9.1.1.2+0~mr9.1.1.2
Feb 25 16:35:13 ip-172-31-3-101 rtpengine[4437]: INFO: Received command 'ping' from 127.0.0.1:52823
Feb 25 16:35:13 ip-172-31-3-101 rtpengine[4437]: INFO: Replying to 'ping' from 127.0.0.1:52823 (elapsed time 0.000001 sec)
Feb 25 16:44:31 ip-172-31-3-101 rtpengine[4437]: INFO: Version 9.1.1.2+0~mr9.1.1.2 shutting down
Feb 25 16:44:33 ip-172-31-3-101 rtpengine[12951]: INFO: Generating new DTLS certificate
Feb 25 16:44:35 ip-172-31-3-101 rtpengine[12951]: INFO: Startup complete, version 9.1.1.2+0~mr9.1.1.2
Feb 25 16:44:40 ip-172-31-3-101 rtpengine[12951]: INFO: Received command 'ping' from 127.0.0.1:60974
Feb 25 16:44:40 ip-172-31-3-101 rtpengine[12951]: INFO: Replying to 'ping' from 127.0.0.1:60974 (elapsed time 0.000001 sec)
Feb 25 18:55:30 ip-172-31-3-101 rtpengine[12951]: INFO: [«7qBL5OxYFJ»]: Received command 'offer' from 127.0.0.1:48385
Feb 25 18:55:30 ip-172-31-3-101 rtpengine[12951]: NOTICE: [«7qBL5OxYFJ»]: Creating new call
Feb 25 18:55:30 ip-172-31-3-101 rtpengine[12951]: INFO: [«7qBL5OxYFJ»]: Replying to 'offer' from 127.0.0.1:48385 (elapsed time 0.000392 sec)
Feb 25 18:55:34 ip-172-31-3-101 rtpengine[12951]: INFO: [«7qBL5OxYFJ»]: Received command 'answer' from 127.0.0.1:48385
Feb 25 18:55:34 ip-172-31-3-101 rtpengine[12951]: INFO: [«7qBL5OxYFJ»]: Replying to 'answer' from 127.0.0.1:48385 (elapsed time 0.000186 sec)
Feb 25 18:55:35 ip-172-31-3-101 rtpengine[12951]: INFO: [«7qBL5OxYFJ»]: Received command 'answer' from 127.0.0.1:59985
Feb 25 18:55:35 ip-172-31-3-101 rtpengine[12951]: INFO: [«7qBL5OxYFJ»]: Replying to 'answer' from 127.0.0.1:59985 (elapsed time 0.000158 sec)
Feb 25 18:56:05 ip-172-31-3-101 rtpengine[12951]: INFO: [«7qBL5OxYFJ»]: Received command 'delete' from 127.0.0.1:48452
Feb 25 18:56:05 ip-172-31-3-101 rtpengine[12951]: INFO: [«7qBL5OxYFJ»]: Scheduling deletion of call branch '«moEHZeSjz»' (via-branch '«»') in 30 seconds
Feb 25 18:56:05 ip-172-31-3-101 rtpengine[12951]: INFO: [«7qBL5OxYFJ»]: Replying to 'delete' from 127.0.0.1:48452 (elapsed time 0.000106 sec)
Feb 25 18:56:06 ip-172-31-3-101 rtpengine[12951]: INFO: [«7qBL5OxYFJ»]: Received command 'delete' from 127.0.0.1:46576
Feb 25 18:56:06 ip-172-31-3-101 rtpengine[12951]: INFO: [«7qBL5OxYFJ»]: Scheduling deletion of call branch '«moEHZeSjz»' (via-branch '«»') in 30 seconds
Feb 25 18:56:06 ip-172-31-3-101 rtpengine[12951]: INFO: [«7qBL5OxYFJ»]: Replying to 'delete' from 127.0.0.1:46576 (elapsed time 0.000143 sec)
Feb 25 18:56:36 ip-172-31-3-101 rtpengine[12951]: INFO: [«7qBL5OxYFJ»]: Call branch '«moEHZeSjz»' (label 'caller', via-branch '«»') deleted, no more branches remaining
Feb 25 18:56:36 ip-172-31-3-101 rtpengine[12951]: INFO: [«7qBL5OxYFJ»]: Final packet stats:
Feb 25 18:56:36 ip-172-31-3-101 rtpengine[12951]: INFO: [«7qBL5OxYFJ»]: --- Tag '«moEHZeSjz»' (label 'caller'), created 1:06 ago for branch '«»', in dialogue with '«424D78B4-6037F2A2000A737D-61229700»'
Feb 25 18:56:36 ip-172-31-3-101 rtpengine[12951]: INFO: [«7qBL5OxYFJ»]: ------ Media #1 (audio over RTP/AVPF) using unknown codec
Feb 25 18:56:36 ip-172-31-3-101 rtpengine[12951]: INFO: [«7qBL5OxYFJ»]: --------- Port 172.31.3.101:30016 <> « 100.110.81.168:7078 », SSRC «0», 0 p, 0 b, 0 e, 66 ts
Feb 25 18:56:36 ip-172-31-3-101 rtpengine[12951]: INFO: [«7qBL5OxYFJ»]: --------- Port 172.31.3.101:30017 <> « 100.110.81.168:7079 » (RTCP), SSRC «0», 0 p, 0 b, 0 e, 66 ts
Feb 25 18:56:36 ip-172-31-3-101 rtpengine[12951]: INFO: [«7qBL5OxYFJ»]: --- Tag '«424D78B4-6037F2A2000A737D-61229700»' (label 'callee'), created 1:06 ago for branch '«z9hG4bK0226.964f340c33c986c5eabc3d9a58964518.0»', in dialogue with '«moEHZeSjz»'
Feb 25 18:56:36 ip-172-31-3-101 rtpengine[12951]: INFO: [«7qBL5OxYFJ»]: ------ Media #1 (audio over RTP/AVPF) using unknown codec
Feb 25 18:56:36 ip-172-31-3-101 rtpengine[12951]: INFO: [«7qBL5OxYFJ»]: --------- Port 172.31.3.101:30000 <> « 197.210.53.94:7078 », SSRC «0», 0 p, 0 b, 0 e, 66 ts
Feb 25 18:56:36 ip-172-31-3-101 rtpengine[12951]: INFO: [«7qBL5OxYFJ»]: --------- Port 172.31.3.101:30001 <> « 197.210.53.94:7079 » (RTCP), SSRC «0», 0 p, 0 b, 0 e, 66 ts
More information about the Spce-user
mailing list