Ring Group Issues

[simonjw]

Hi everyone.

I am trying to setup ring groups and having an issue with getting it working. I've tried using extension number 200 and 2000 with the destinations being 201 and 202 and failover being 201s voicemail. I have saved it, generated XML etc and changed my dialplans to ring to 200/2000 xml {domainName} under application transfer in the XML and I cannot get 201 and 202 to ring together. Is there anything I am missing in order to get this to work?

@Adrian Fretwell any help with this please?

Thank you

 

[Adrian Fretwell]

When you say you can't get them to ring together, what is happening? Is just one ringing? or nothing at all?

 

[simonjw]

Just the one is ringing as if it is still using the old dialplan. So I am not sure why that is the case as I would believe both should be ringing. I can call 201 and 202 from each other, however, if I make the ring group 200 or 2000 I cannot dial that, so maybe that is the issue?

 

[simonjw]

It seems I can now dial 200 and it plays my prompt businessman that I set, but I have already recreated the ring group to be 2000. So I am not sure whether it is just really delayed in clearing the cache and reloading the xml

 

[Adrian Fretwell]

It could be a caching issue, did you flush the dialplan cache? (Utilities->Clear Cache)

PS: Dialplans are cached for five minutes.

 

[whut]

Definitely flush cache. That is odd behavior. Make sure you are not using the same extension number more than one time on a domain. You cannot have phone extension 200 again for any other type of extensions

 

[simonjw]

It is really weird. I have cleared the cache like you mentioned and reloaded via the gui and the cli. I have left it for 5 minutes and clearly the inbound routes I have, are not updating as they should, even when I pull in the XML and it shows 200. So I guess I will give it another 20 minutes and see...

 

[simonjw]

@whut literally have 201 and 202 nothing else in extensions, so 200 and 2000 should be available. Evidently, 200 is available. And here I thought I was just getting the hang of Freeswitch via DjangoPBX haha

 

[simonjw]

And the odd thing now is that the say does not say businessman and the 200 still works. So that cache is cleared. So I guess the inbound XML needs to reload and cache needs to clear. And now it seems to be working, so evidently the clear cache needs to be done more than once, as well as the reloading of the xml. @Adrian Fretwell, is there any way that we can turn that caching off all together?

 

[Adrian Fretwell]

I would not recommend turning the caching off, but you can reduce it's time.
In /home/django-pbx/pbx/pbx/settings.py there is a cache section. You will see the 300, this is seconds (five min), you could maybe set this to 10.

CACHES = {
    'default': {
        'BACKEND': 'django.core.cache.backends.memcached.PyMemcacheCache',
        'LOCATION': '127.0.0.1:11211',
        'TIMEOUT': 300,
        'KEY_PREFIX': 'pbx',
        "OPTIONS": {
            "no_delay": True,
            "ignore_exc": True,
            "max_pool_size": 8,
            "use_pooling": True,
        },
    }
}

If you do make changes to settings.py, you will need to reload both instances of uWSGI, the one that provides the GUI and the one that feeds configuration to freeswitch.
As root:

uwsgi --reload /var/run/uwsgi/app/djangopbx/pid
uwsgi --reload /var/run/uwsgi/app/fs_config/pid

 

[simonjw]

@Adrian Fretwell thank you for that, I am going to test on another tenant first to see, might just be a stuck cache. I am running on the lightwight VM in this test environment. Is there anywhere that I can privately message you in order to discuss something?

 

[simonjw]

So interestingly my first lot that was sticking has now completely stopped working in terms of ringing the extensions in the list when I have been playing with the other tenant. So I am deleting the ring groups and then purging the cache as well as reload xml and going to leave it for 30 minutes and revisit. Not sure whether this is just isolated on my installation or not

 

[Adrian Fretwell]

I have never seen what you are describing. You may need to describe your setup in more detail, provide some log files and/or screenshots.

We have very complicated ring groups working with features such as delays and the confirm mechanism for mobile phone destinations.

 

[simonjw]

Its just the normal install. I got it to stick, the steps I took were as follows:

1. Change ring plan to ring group extension
2. Create ring group with destinations and save
3. Wait 5 minutes and then generate the the XML in the ring group interface
4. Flush the cache and reload XML

It works every time. However, I have come up with another issue. If I have my desk phone and my SIP Dialer on my phone registered as the same extension, 201 for example and someone calls in on say 200 or the DID, only the desk phone (201) and 202 will ring and not my SIP Dialer (201), but if you just plain dial 201 from 202 both my desk phone and SIP Dialer ring... So I am perplexed once again. Not sure whether you have seen that before or whether there is a setting to ensure both work?

 

[Adrian Fretwell]

What you are describing with your 201, sounds like "shared line appearance". This is not well supported by FreeSWITCH, see the link below:
https://developer.signalwire.com/fr...onfiguration/Shared-Line-Appearance_13174046/

As the page says, there are some settings in the SIP profile that may help you with this, but it is generally accepted that you would only register one endpoint per extension as @whut did say in his post above.

 

[simonjw]

That is odd because I have seen it work in Freeswitch before on another system a while back. Isn't it odd that both the desk phone and the app will ring internally when 201 is dialed but won't ring together when 200 or the DID is dialed? Where should I be placing the following "<param name="manage-shared-appearance" value="true"/>"? It does say the SIP profile and I am assuming that is on the extensions XML? What if my device has no settings related to SCA? Will it just work out the box?

 

[jcre]

Admin -> Sip Profiles -> Internal -> SIP PROFILE SETTINGS

It's in there, but on my install of DjangoPBX it appears to already be enabled

 

[simonjw]

Well, I can confirm that is correct. I don't have any settings on my devices that have anything around SCA, and this is a feature that a lot of my clients use, so its going to be an issue going to some level of production with this... I wonder if there is a workaround or whether I can get it working...

 

[Adrian Fretwell]

The reason your SLA behaves differently when called from a ring group is the way the bridge statement is built from the contact details.
May be you can get some packet captures...
Many ITSPs will not allow multiple registrations to a single extension because, they operate a per seat charging model - this is very common.

There are other SIP Profile options that per seat ITSP use such as setting multiple-registrations to false and setting called max-registrations-per-extension.

There may be a work-around for you, the first thing would be to set up your scenario in the lab and test it out to find out what is really happening. We would need to put some time aside to investigate, which I'm happy to do if enough people request that facility.