NO JOY ClearlyIP Incoming Calls Fail

[redstonemason]

I was able to get into the portal to generate an invoice so that I could submit a port request of many numbers to ClearlyIP as of today. I will update here if the porting gets processed or refused.

As for iPBX2021 on Debian 10 VULTR... ClearlyIP Trunks did not come up and work without placing a ticket and having them do a SIP trace and make a change on their side. Curious.

 

[wardmundy]

I was able to get into the portal to generate an invoice so that I could submit a port request of many numbers to ClearlyIP as of today. I will update here if the porting gets processed or refused.

As for iPBX2021 on Debian 10 VULTR... ClearlyIP Trunks did not come up and work without placing a ticket and having them do a SIP trace and make a change on their side. Curious.

Need a better hint? What did they do on their side? If you don't know, perhaps you could ask them. Thanks.

 

[redstonemason]

Need a better hint? What did they do on their side? If you don't know, perhaps you could ask them. Thanks.

I will ask them. The issue was that I could could place outgoing calls but incoming calls were not being completed.
They even used desktop sharing to explore my iPBX Web Gui and at the root prompt of a bash shell they did:

apt-get install sngrep
sngrep -rc

Nice tool that I have never used

 

[tbrummell]

I will ask them. The issue was that I could could place outgoing calls but incoming calls were not being completed.
They even used desktop sharing to explore my iPBX Web Gui and at the root prompt of a bash shell they did:

apt-get install sngrep
sngrep -rc

Nice tool that I have never used

It's been mentioned here before, and yes, an invaluable tool to have in your back pocket.

 

[wardmundy]

According to Clearly IP:

The change in your case was to set your media to connect directly. Our default setup is the media (RTP) is proxied through the trunking servers briefly and then re-invited to the media servers; this is to help with firewall issues on most routers as it allows the router to open the pin holes for the RTP on a case-by-case basis since the media servers are constantly changing. In your case that re-invite wasn't getting through, and switching you to direct media resolved it.

 

[redstonemason]

According to Clearly IP:

Is this media RTP setting on the ClearlyIp system or a setting on my iPBX?

Also, I see this morning that the process and it's child threads

node /var/www/html/admin/modules/clearlytrunking/node/build/bundle.js

have my CPU pinned at 100% (VULTR iPBX2021 Debian 10)

I am commited to getting this fixed and this PBX is not really in production yet but I am thinking that this thread needs to be marked as NO JOY.

 

[redstonemason]

Here is a screen shot of

root ~/: top

 

[wardmundy]

I'd recommend you run it by the ClearlyIP folks again.

 

[redstonemason]

Will do. Thank you.

 

[redstonemason]

While the following does not explain the flaming Clearly Trunking daemon nor the media RTP problem with some Vultr co-locations (I am using VULTR Toronto for my initial move from VOIP.MS to ClearlyIP), I do have a more stable system I think...

Together with Clearly IP tech support, we uninstalled the Clearly Trunking Daemon and manually configured the ClearlyIP Trunks with the credentials instead of using the ClearlyIP KeyCode.

The downside for some using this workaround is that you will lose SMS and WebRTC if you choose this solution.

We also remove modules - ClearlDevices, ClearlyLicensing (for ClearlyAnywhere) and PM2 and UCP.

Yes - I killed a Mosquitto with a Sledgehammer and was quite happy to do it for my use case to get this migration on the road!

 

[kenn10]

We also remove modules - ClearlDevices, ClearlyLicensing (for ClearlyAnywhere) and PM2 and UCP.

I think you may need PM2 for the FreePBX backup and a few other FreePBX modules. I guess you'll find out as you use it.

 

[redstonemason]

I think you may need PM2 for the FreePBX backup and a few other FreePBX modules. I guess you'll find out as you use it.

I had stripped an instance down earlier but that was a long time ago under CentOS.