Toggle sidebar Toggle sidebar

Some minor issues

Status
Not open for further replies.

CdnNick

Joined
Aug 21, 2018
Messages
17
Reaction score
3
Hi,

I'm currently having some minor issues:

1) some times when we place a call into shared parking we are unable to pick up the call, it gives a "call not found" error, the call itself sits in the system for a few minutes then eventually disconnects. I've had this problem on multiple phones no matter which phone parked the call. If I use the webclient I am able to unpark the call through the "switchboard" so that's a work around but not a great solution.

2) we are using Yealink T23G and T46S phones that all have the latest firmware, if I make a change to the phones (like edit a BLF button) the phone will not updated, I've waited days, tried forcing a re-provision, the only way it updates is if I do a factory reset and configure the phone again. I am using direct SIP to configure the phones.

I have a total of 8 phones in the office, 1 remote W60B unit and the PBX is hosted on Amazon lightsail, the updating worked before so I am not sure why it just stopped.

On a side note would it be worth setting up an SBC and would I need 1 in each of my 2 locations?
 
Do all users have the right to park calls (Ext -> Rights -> Can park calls)?
 
  • Like
Reactions: craigreilly
CdnNick said:
On a side note would it be worth setting up an SBC and would I need 1 in each of my 2 locations?
Click to expand...

One SBC per Location - as easy as a Raspberry Pi.
 
  • Like
Reactions: JCLloyd
Last edited:
I would for sure use SBC at the site with 8 phones vs. STUN. Also make sure to test with the 3CX template to see if the issues go away.

If you are using an older phone template it could cause this issue. Also we have seen this happen if you are using your own SSL certificate instead of the 3CX FQDN one (depending on certificate source and versions of firmware, etc).
 
I verified each extension has the rights to park a call.

At my remote location with the 1 phone can the SBC be a mix of windows and raspberry Pi? I have a windows 10 PC that is on 24/7, it would be easy to use that for 1 phone.

So the phones all have the same SIP and RTP ports. I'm guessing it might be better to spend my time setting up the SBC instead of changing all the ports and port forwarding?
 
I was just looking at the instructions for setting up the SBC, but under SIP trunks I don't see the "Add SBC" button. What am I missing?
 
I ordered a raspberry Pi, it will arrive on Monday. Can I setup the SBC on a live system or do I need to take the system down to setup them up? Once the SBC is up I assume I need to reprovision the phones with the new settings?
 
If the phones are on STUN you can simply install/configure the new SBC on the PI and then move one phone at a time over. So the only downtime would be when you move the phones over.
 
  • Like
Reactions: CentrexJ
CentrexJ said:
If the phones are on STUN you can simply install/configure the new SBC on the PI and then move one phone at a time over. So the only downtime would be when you move the phones over.
Click to expand...

Ok, that's what I was thinking but it doesn't really mention anything in the instructions.
 
@CdnNick :
  • Set up the SBC and it connect to the 3CX.
  • Then, go to the provisioning tab of the extension you want to move.
  • Make sure the phone is selected.
  • Choose 3CX SBC (remote) for the Provisioning Method.
  • With only one SBC, the interface and SBC IP will populate for you.
  • I almost forgot... move the phone at this time.
I was expecting more pixie dust and witches brew when I did it, but it kind of just happens for you :)>)
 
Thanks, guess I'll see how it goes next week when I get started.
 
So I setup the SBC last night and moved all the phones this morning. Half of the phones I had to factory reset to get them to reprovision to the SBC. The weird thing was after the reset in the 3cx management console it changed the IP of the SBC to a 169.x.x.x address and I had to change it back every time.

Phones are up and seem to be working, hopefully this fixes my shared parking issue.
 
@CdnNick … Wow... I did NOT have that issue, and am sorry that you have.

I hard-coded the SBC, the same as I would a server. That keeps it on the correct IP. There was a February Windows update that screwed with NIC settings, but I did the Linux ISO install for both the 3CX & SBC.

The Yealink T48G phones we use only needed to be set to DHCP, and then changed to SBC (remote) in the 3CX console. Bringing them back from SBC to local has the caveat that there is a proxy IP that gets set to the SBC that needs to be deleted before taking them off the SBC and moving them back.
. I am wondering if your phones just needed the Proxy IP set to the SBC, instead of starting over.

[Update] - Let us know how the Shared Parking works... or doesn't. I set some up on our 3CX, and no one wants to use them! They really don't use much of the 3CX features... basically voicemail and forward calls.
 
Hard coded the SBC where? I set it up with a static IP address on the local router, is that what you mean? It was weird, I had a mixture of the 2 phone models we use not update, while others changed in a matter of seconds. But now that they are connected to the SBC changes to the phone config update almost instantly when I hit the reprovision button so that's an improvement.

I only use the shared parking feature because we upgraded from an ancient phone system and the office staff was used to putting calls on hold on the individual analog lines. Some of the people don't deal with change so well so this was the closest thing I could think of to replicate the old system. They are still getting use to having extensions and voicemail lol.
 
When installing the SBC, leaving the network cable unplugged causes the SBC installer (at least on Linux) to ask for static IP settings. With the cable plugged in, the installer just pulls a DHCP address from the source and you need to do IP reservations at the DHCP source. This is only done during install. Luckily, it only take a bout 10 minutes, plus/minus.

If your phones were defaulting to 169.254.x.y using DHCP, I am wondering if they will revert back to 169.254.x.y if the DHCP server is off line for any length of time. Would that mean having to reboot those phones after the DHCP server recovers? If you get a chance to test this, it would be worth knowing what to expect if that happens. Just a thought.
 
I think I need to clarify myself a bit, the IP address switching to 169.x.x.x was under the Phone Provisioning tab and the "3CX Session Border Controller" field was being switched from the local address to 169.x.x.x.

The "3CX Session Border Controller" field is blank when I select the 3CX SBC option, is that normal or maybe I do have an issue with my config? When I setup the SBC it was connected to the network/internet at the time.
 
Status
Not open for further replies.

Latest Posts

Forum statistics

Threads
112,089
Messages
590,696
Members
165,053
Latest member
jmc-tim
3CX Logo Footer Copyright © Sitemap Privacy
Top Bottom