Setting up FreePBX to send a X-Tenant SIP header for Skyetel Tenant tracking
-
This is fully working now. I tested calls and saw all of the correct X-Tenant headers in the outbound
INVITEmessages
Outbound routing changed as of now, to give a short time of low call volume as a pseudo test.
-
Not trying to threadjack.
Just an fyi, in FusionPBX, this is included by default. -
@JaredBusch nice! What tool are you using in that screenshot to look at call flow?
-
@fuznutz04 said in Setting up FreePBX to send a X-Tenant SIP header for Skyetel Tenant tracking:
@JaredBusch nice! What tool are you using in that screenshot to look at call flow?
-
@FATeknollogee Thanks!
-
@FATeknollogee said in Setting up FreePBX to send a X-Tenant SIP header for Skyetel Tenant tracking:
Not trying to threadjack.
Just an fyi, in FusionPBX, this is included by default.That has nothing to do with anything as the thread was specifically about setting up FreePBX.
FusionPBX is not ever Asterisk based so nothing especially matters about what works in that.
-
@fuznutz04 said in Setting up FreePBX to send a X-Tenant SIP header for Skyetel Tenant tracking:
@FATeknollogee Thanks!
Sangoma has included it by default since FreePBX 14. It was available via yum in FreePBX 13.
-
All outbound calls were routed out to @Skyetel for the entire day.
Users were completely unaware of any changes. This is how things are supposed to work.
535 minutes used.
Only 5 simultaneous channels.
-
@JaredBusch we did a port over to Skyetel for a busy utility today, too.
-
This is great. Thanks.
What is this significance to the numbers within the "{OUTBOUND_ROUTE_NAME:0:4}" preceding the route name?
-
@cdbrush said in Setting up FreePBX to send a X-Tenant SIP header for Skyetel Tenant tracking:
This is great. Thanks.
What is this significance to the numbers within the "{OUTBOUND_ROUTE_NAME:0:4}" preceding the route name?
That’s a substring. Look at the route name, starting at character zero and going for 4 characters.
