Skip to main content

2 TENANTS 1 PBX, recordings crossed.

Posted by kornaxl on Wed, 04/15/2009

Hello Thirdlane
We have two tenants on the same PBX.
When the 1st tenant call to us (2nd tenant) and we take HOLD (MOH) the call for some seconds (or minutes) they listen yours recording (MOH of the 1st tenant) instead of the MOH of the 2nd tenant recording.

We change the audio file for the 1st tenant but the problem persist.

Regrats
Alexander Schnohr Carmona
Netline Telecommunications Chile S.A.
http://www.netline.cl
PC: 7530041, (GMT -4)
Phone: +56 2 656 0634


Submitted by eeman on Wed, 04/15/2009 Permalink

Im not sure you can fix this. When you call out your call gets routed through

[macro-tl-set-variables2]

which sets the music on hold class. This is so that when you call someone and put them on hold it plays your music class. A similar process happens on the inbound call.

when you bridge a call between two channels on the same asterisk box you have 2 legs of the call. Each leg is its own channel with its own channel information. Once the call connects both channels are bridged together. In this situation each channel has a different music class defined and when you are placed on hold its your leg of the call's value that determines the music class.

I think in order to get the behavior you are looking for, your call would have to complete like this...

M ---- tenant 1 ---> Gate

T

E <--- tenant 2 ---- Way

where the gateway is perhaps an asterisk box with a route table built out on numbers you own.

Then the other end of your call would be the trunk to the gateway box not another channel with its own set of music class declarations.

does this help explain?

Submitted by cbbs70a on Wed, 04/15/2009 Permalink

One way to "fix" this, and I'm not sure it's really worth the effort is to modify the dialplan somewhat. The first context that gets called on outbound calls is "from-inside" which really does nothing but call

macro-tl-set-variables2, which like Eric said, sets the MOH class. You can clone that macro, name it something else, and then delete the MOH statements. Then modify "from-inside" to use that macro instead. The whole thing would take a grand total of about 1 minute, but then you have to take that into account every time you upgrade the software, since its very likely that the mod would be overwritten. Also, some people don't feel comfortable making these types of edits, so that needs to be considered also.

FSD

Submitted by kornaxl on Wed, 04/15/2009 Permalink

We have an third tenant, between the second and the third the MOH works fine.

Thanks a lot.

Alexander Schnohr Carmona

Netline Telecommunications Chile S.A.