search

dOpensource / dsiprouter

UI Interface for implementing Kamailio to provide PBX Hosting and SIP Trunking Services
https://dsiprouter.org
Apache License 2.0
196 stars 105 forks source link

vmware support #363

Open arenrover0 opened 3 years ago

arenrover0 commented 3 years ago

hello i know it's kind of a noob problem but i couldn't find any thing online so i really appreciate it if you take some time to help me out I just installed dsiprouter on a centos vmware and i am using 2 freepbx (one as carrier(...176) and one as a local pbx(...177)) when i try to call from career to the local I get the following error in dsiprouter.log

ERR: [556270ba16f86adf714330192f289bc8@192.168.1.176:5060]: Failed to get 2 consecutive ports on interface 5.201.135.138 for media relay (last error: Cannot assign requested address) Apr 18 20:08:58 rtpengine[2874]: ERR: [556270ba16f86adf714330192f289bc8@192.168.1.176:5060]: Failed to get 2 consecutive ports on all locals of logical 'default' pr 18 20:08:58 rtpengine[2874]: [1618760338.985104] ERR: [556270ba16f86adf714330192f289bc8@192.168.1.176:5060]: Failed to get 2 consecutive ports on interface 5.201.135.138 for media relay (last error: Cannot assign requested address) pr 18 20:08:58 rtpengine[2874]: [1618760338.989972] ERR: [556270ba16f86adf714330192f289bc8@192.168.1.176:5060]: Failed to get 2 consecutive ports on all locals of logical 'default' pr 18 20:08:58 rtpengine[2874]: [1618760338.990006] ERR: [556270ba16f86adf714330192f289bc8@192.168.1.176:5060]: Error allocating media ports pr 18 20:08:58 rtpengine[2874]: [1618760338.990034] ERR: [556270ba16f86adf714330192f289bc8@192.168.1.176:5060]: Destroying call pr 18 20:08:58 rtpengine[2874]: [1618760338.990146] ERR: [556270ba16f86adf714330192f289bc8@192.168.1.176:5060]: Call start seems to exceed call stop pr 18 20:08:58 rtpengine[2874]: [1618760338.990369] WARNING: [556270ba16f86adf714330192f289bc8@192.168.1.176:5060]: Protocol error in packet from 127.0.0.1:57714: Ran out of ports [d8:supportsl10:load limite3:sdp262:v=0 pr 18 20:08:58 rtpengine[2874]: o=root 62959694 62959694 IN IP4 192.168.1.176 pr 18 20:08:59 rtpengine[2874]: s=Asterisk PBX 13.19.1 pr 18 20:08:59 rtpengine[2874]: c=IN IP4 192.168.1.176 pr 18 20:08:59 rtpengine[2874]: t=0 0 pr 18 20:08:59 rtpengine[2874]: m=audio 15152 RTP/AVP 0 8 101 pr 18 20:08:59 rtpengine[2874]: a=rtpmap:0 PCMU/8000 pr 18 20:08:59 rtpengine[2874]: a=rtpmap:8 PCMA/8000 pr 18 20:08:59 rtpengine[2874]: a=rtpmap:101 telephone-event/8000 pr 18 20:08:59 rtpengine[2874]: a=fmtp:101 0-16 pr 18 20:08:59 rtpengine[2874]: a=maxptime:150 pr 18 20:08:59 rtpengine[2874]: a=sendrecv pr 18 20:08:59 rtpengine[2874]: 3:ICE6:remove13:media-address13:192.168.1.1275:flagsl13:trust-addresse7:replacel6:origin18:session-connectione18:transport-protocol7:RTP/A ... pr 18 20:08:59 rtpengine[2874]: [1618760338.990405] WARNING: [556270ba16f86adf714330192f289bc8@192.168.1.176:5060]: ... VP8:rtcp-muxl5:demuxe7:call-id51:556270ba16f86adf714330192f289bc8@192.168.1.176:506013:received-froml3:IP413:192.168.1.176e8:from-tag10:as331fd6f77:command5:offere] Apr 18 20:08:58 rtpengine[2874]: ERR: [556270ba16f86adf714330192f289bc8@192.168.1.176:5060]: Error allocating media ports Apr 18 20:08:58 rtpengine[2874]: ERR: [556270ba16f86adf714330192f289bc8@192.168.1.176:5060]: Destroying call Apr 18 20:08:58 rtpengine[2874]: INFO: [556270ba16f86adf714330192f289bc8@192.168.1.176:5060]: Final packet stats: Apr 18 20:08:58 rtpengine[2874]: INFO: [556270ba16f86adf714330192f289bc8@192.168.1.176:5060]: --- Tag 'as331fd6f7', created 0:00 ago for branch '', in dialogue with '' Apr 18 20:08:58 rtpengine[2874]: INFO: [556270ba16f86adf714330192f289bc8@192.168.1.176:5060]: ------ Media #1 (audio over RTP/AVP) using unknown codec Apr 18 20:08:58 rtpengine[2874]: INFO: [556270ba16f86adf714330192f289bc8@192.168.1.176:5060]: --- Tag '', created 0:00 ago for branch '', in dialogue with 'as331fd6f7' Apr 18 20:08:58 rtpengine[2874]: INFO: [556270ba16f86adf714330192f289bc8@192.168.1.176:5060]: ------ Media #1 (audio over RTP/AVP) using unknown codec Apr 18 20:08:58 rtpengine[2874]: ERR: [556270ba16f86adf714330192f289bc8@192.168.1.176:5060]: Call start seems to exceed call stop Apr 18 20:08:58 rtpengine[2874]: ci=556270ba16f86adf714330192f289bc8@192.168.1.176:5060, created_from=127.0.0.1:57714, last_signal=1618760337, tos=0, ml0_start_time=1618760338.990017, ml0_end_time=1618760338.990271, ml0_duration=0.000254, ml0_termination=UNKNOWN, ml0_local_tag=as331fd6f7, ml0_local_tag_type=FROM_TAG, ml0_remote_tag=(null), payload_type=unknown, ml1_start_time=1618760337.557768, ml1_end_time=1618760338.990282, ml1_duration=1.432514, ml1_termination=UNKNOWN, ml1_local_tag=(null), ml1_local_tag_type=UNKNOWN, ml1_remote_tag=as331fd6f7, payload_type=unknown, Apr 18 20:08:58 rtpengine[2874]: WARNING: [556270ba16f86adf714330192f289bc8@192.168.1.176:5060]: Protocol error in packet from 127.0.0.1:57714: Ran out of ports [d8:supportsl10:load limite3:sdp262:v=0 o=root 62959694 62959694 IN IP4 192.168.1.176 s=Asterisk PBX 13.19.1 c=IN IP4 192.168.1.176 t=0 0 m=audio 15152 RTP/AVP 0 8 101 a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=maxptime:150 a=sendrecv 3:ICE6:remove13:media-address13:192.168.1.1275:flagsl13:trust-addresse7:replacel6:origin18:session-connectione18:transport-protocol7:RTP/A ... Apr 18 20:08:58 rtpengine[2874]: WARNING: [556270ba16f86adf714330192f289bc8@192.168.1.176:5060]: ... VP8:rtcp-muxl5:demuxe7:call-id51:556270ba16f86adf714330192f289bc8@192.168.1.176:506013:received-froml3:IP413:192.168.1.176e8:from-tag10:as331fd6f77:command5:offere] Apr 18 20:08:58 rtpengine[2874]: DEBUG: [556270ba16f86adf714330192f289bc8@192.168.1.176:5060]: freeing main call struct Apr 18 20:08:58 /usr/sbin/kamailio[2907]: ERROR: rtpengine [rtpengine.c:2588]: rtpp_function_call(): proxy replied with error: Ran out of ports Apr 18 20:08:58 rtpengine[2874]: INFO: Detected command from 127.0.0.1:57714 as a duplicate Apr 18 20:08:59 rtpengine[2874]: DEBUG: timer run time = 0.000068 sec Apr 18 20:09:01 rtpengine[2874]: DEBUG: timer run time = 0.000063 sec pr 18 20:09:02 systemd[1]: Started Session 88 of user root. pr 18 20:09:02 CROND[10691]: (root) CMD (/opt/dsiprouter/gui/dsiprouter_cron.py fusionpbx sync) Apr 18 20:09:02 rtpengine[2874]: DEBUG: timer run time = 0.000080 sec Apr 18 20:09:03 rtpengine[2874]: DEBUG: timer run time = 0.000051 sec pr 18 20:09:04 postfix/pickup[8573]: A488434040: uid=0 from=<root> pr 18 20:09:04 postfix/cleanup[3139]: A488434040: message-id=<20210418153904.A488434040@local.cluster> pr 18 20:09:04 postfix/qmgr[1933]: A488434040: from=<root@local.cluster>, size=4475, nrcpt=1 (queue active) pr 18 20:09:04 postfix/local[3142]: A488434040: to=<root@local.cluster>, orig_to=<root>, relay=local, delay=0.37, delays=0.37/0/0/0, dsn=2.0.0, status=sent (delivered to mailbox) pr 18 20:09:04 postfix/qmgr[1933]: A488434040: removed

devopsec commented 3 years ago

@arenrover0 it sounds like your PBX's are installed on the same box as dsiprouter?
if so, this is not the typical way to install and they would be better suited on a separate box unless you know how to avoid these issues.
other than that it could be a VLAN issue, VLAN support is currently a manual process but there is an issue open on making VLAN support easier out of the box.
see https://github.com/dOpensource/dsiprouter/issues/366 for more info

mackhendricks commented 2 years ago

This error is received typically when the rtpengine config is using the NAT'd public address versus the internal ip. The RTPEngine can't bind to a NAT'd ip. We will be fixing this, but our test case currently consists of Cloud platforms, but it should work for VMWARE

devopsec commented 2 years ago

Looking back at this issue, we don't support centos installations anymore, and have moved to Amazon Linux (as stable) / alpha support for the more stable centos alternatives (rocky, alma, rhel).
We also have not tested on vmware so that is also an unsupported configuration.
I would assume there are some networking workarounds needed to get dsiprouter to play nice with vmware.
Changing name and pulling off v0.70 release.

devopsec commented 9 months ago

Update, centos 7/8/9 support has been updated in the recent releases.
That being said vmware is still not high priority looking at where most people are deploying their builds.
I'll leave this issue open and up to the community to support.