Topic: COS & Siblings

[SARK devs]

Lloyd Keen (thanks Lloyd) recently reported a bug with COS and Siblings.  Basically, COS breaks the sibling support.  We have created a fix for this in -619 but it isn't completely seamless.  We've had to create a new entry point in extensions.conf.  Now, this is no problem if you don't have any siblings.  Bit of a pain if you do.  Here's the deal....

You will first need to install -619 (it's available on the download site now).   Then, you can either delete and recreate all of your existing sibling trunks.. OR, ...you can change the context= entry in each existing sibling trunk definition. 

Click on the edit button for the trunk and change the context entry in the right-hand edit window.  It will look like this...

Code: [Select]

type=user
secret=whatever
context=internal

Change it to this

Code: [Select]

type=user
secret=whatever
context=priv_sibling
Now, you DONT need to do this if you aren't running or intending to run COS, OR, if you don't run Siblings.  It is only necessary if you wish to run BOTH. 

You can run pre -619 siblings without COS alongside modified -619 systems.

Sorry everyone, this is a complete PITA,  we don't usually get it this wrong.   


Kinds Regards


S

[ldkeen]

Hi Jeff,
Sorry about the delay getting back to you. Still having a few problems.
Installed -619 and changed the context from internal to priv_sibling but the call fails with:

From the calling end:

Code: [Select]

[May  2 10:10:47] WARNING[5578]: chan_iax2.c:7593 socket_process: Call rejected by 60.240.xxx.xxx: No such context/extension
    -- Hungup 'IAX2/gurusme-16384'

And from the receiving end:

Code: [Select]

[May  2 10:06:58] NOTICE[6520]: chan_iax2.c:7773 socket_process: Rejected connect attempt from 203.206.xxx.xxx, request '3000@priv_sibling' does not exist
Looking at the dial plan I can't see any context for priv_sibling.

We tried deleting the trunk and re-creating it, but it didn't automatically add the context (priv_sibling). It still remains as context=internal.

I also have another problem, whilst testing I created an unpriviledged trunk which I now can't delete via either the server-manager or by db commands (db selintra delete sme>>guru).
Many thanks,
Lloyd

[SARK devs]

Aaaaaaaaaaaaaaaaaaaaaaaaaaaaaargh!

Big greenie!

Try -620

Sorry mate

re >> sibling - just vim the file and dd the row.  That'll get the blighter.

I'll post a bug to investigate priv deletes properly

Best


J

[ldkeen]

Hi Jeff,
Haven't had much a chance to give it a good workout, but -620 seems to have done the trick.
Many Thanks,
Lloyd