3CX - PBX Connector

[siibi]

Dear Kazoo-lovers,

I am trying to integrate a 3CX system with Kazoo throught the PBX connector app.

Registration = OK

Call setup = OK

Oubound call : one-way voice.

The issue is because our upstream provider doesn't allow the IP address of the 3CX system for RTP.

How can I force that the media is originating from our Kazoo system ?

Thanks for your support !

Sibi

[fred]

It sounds like you want to set bypass_media : false.

http://blog.2600hz.com/bypass-media-mode

You didn't say what version you are running.  I think bypass_media is only on v4.

[James Aimonetti]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

I think you want to set the "media_handling" flag to "process".

https://docs.2600hz.com/dev/applications/crossbar/doc/connectivity/

- --
James Aimonetti

Lead Systems Architect
"If Dialyzer don't care, I don't care"
2600HzPDX | http://2600hz.com
sip:ja...@2600hz.com
tel:415.886.7905
irc:mc_ @ freenode
-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEvSh+xZ5hP1H8lVIU1Mpr4k9cJWAFAlk+tGkACgkQ1Mpr4k9c
JWDsTwgAhlzkGhUOtDWyRIUTosup2dRLzSVYCI3tmISHJ96Pa/WlP1cAzozEZpn3
BXilTl19V+X2+Sxz2p1X6hMOx3lky/jih+v0yyd4AZaeYp56HsskzkFnfT18kKPy
C1OLbmhSW/lOtK7CpeUe+Lnwna8HP9l3ORgyLrNUiTZeiPZz8a0rBTzp21t77coI
rLKYn6UlAwtqfrb4wmZ2x1M835iNtqUIPx3XOTis0aziRZZSe+BFGFyjRe6ZrtaC
6qRfV0BuLlphajCsEZj2gn11GwEzLuPJ1IOii/RImUUodNU3puqhDx1FAPRaIU9B
huDX7w6emwCrrPr+BEctIO8IinYqgA==
=c7Fx
-----END PGP SIGNATURE-----

[fred]

Is this technically the same as bypass_media other than being configured on a per PBX basis rather than per Carrier basis?

On Monday, June 12, 2017 at 8:34:09 AM UTC-7, James Aimonetti wrote:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

I think you want to set the "media_handling" flag to "process".

https://docs.2600hz.com/dev/applications/crossbar/doc/connectivity/

siibi writes:

> Dear Kazoo-lovers,
>
> I am trying to integrate a 3CX system with Kazoo throught the PBX connector
> app.
>
> Registration = OK
> Call setup = OK
>
> Oubound call : one-way voice.
> The issue is because our upstream provider doesn't allow the IP address of
> the 3CX system for RTP.
> How can I force that the media is originating from our Kazoo system ?
>
> Thanks for your support !
>
> Sibi


- --
James Aimonetti

Lead Systems Architect
"If Dialyzer don't care, I don't care"
2600HzPDX | http://2600hz.com

sip:...@2600hz.com

[James Aimonetti]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

I believe this ends up setting the flag in a similar fashion, yes.

>> sip:...@2600hz.com <javascript:>

>> tel:415.886.7905
>> irc:mc_ @ freenode
>> -----BEGIN PGP SIGNATURE-----
>>
>> iQEzBAEBCAAdFiEEvSh+xZ5hP1H8lVIU1Mpr4k9cJWAFAlk+tGkACgkQ1Mpr4k9c
>> JWDsTwgAhlzkGhUOtDWyRIUTosup2dRLzSVYCI3tmISHJ96Pa/WlP1cAzozEZpn3
>> BXilTl19V+X2+Sxz2p1X6hMOx3lky/jih+v0yyd4AZaeYp56HsskzkFnfT18kKPy
>> C1OLbmhSW/lOtK7CpeUe+Lnwna8HP9l3ORgyLrNUiTZeiPZz8a0rBTzp21t77coI
>> rLKYn6UlAwtqfrb4wmZ2x1M835iNtqUIPx3XOTis0aziRZZSe+BFGFyjRe6ZrtaC
>> 6qRfV0BuLlphajCsEZj2gn11GwEzLuPJ1IOii/RImUUodNU3puqhDx1FAPRaIU9B
>> huDX7w6emwCrrPr+BEctIO8IinYqgA==
>> =c7Fx
>> -----END PGP SIGNATURE-----
>>

- --
James Aimonetti

Lead Systems Architect
"If Dialyzer don't care, I don't care"
2600HzPDX | http://2600hz.com

sip:ja...@2600hz.com

tel:415.886.7905
irc:mc_ @ freenode
-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEvSh+xZ5hP1H8lVIU1Mpr4k9cJWAFAlk+vaQACgkQ1Mpr4k9c
JWDPAQgAspTT05l0x8NZRSFOYEb0AUqx1Njk7mvYpVzmKPmnxVGqX1J25f74vz0f
cnsORFx23u2ytnYb+219vjmfKS47gV2/kVsF36l/9+U1u/GpHZBP7NxZPAsy9eIA
fIf0Nu7Sxlw+yJQsk/K+J7peKvKrnuqm+k2gt28nek1DHhuQ8PCfRuuFdNz6J2uL
QZWWVlms6FUKgdMNsWHPBXYdEuk9Xeput51wmK5QPGLuF3kejLHrk87Cy6e8mLEI
wSH8w7yC7MFF63FhGSbXNMdNiTnK7Gz7e+hJeviIxyDoiRlISkT0mZhVv+wcFFX1
fpDw+FH+w1WLgS87TLYeR8r7G53ztA==
=Owdr
-----END PGP SIGNATURE-----

[siibi]

Thank all for the suggestions !

I did set already the parameter "media_handling" to process in the trunkstore of the account. After that, I run the command

"sup trunkstore_maintenance flush 394f063b9408e610b0ba7b09147xxxx01" but no change.

bypass_media is only set on the resource - upstream provider ? This will impact all devices & trunks so this is not acceptable.

Is there another way to originate the rtp traffic from Kazoo to the upstream provider in stead of 3CX to upstream provider ?

 

Op maandag 12 juni 2017 16:44:39 UTC+2 schreef siibi:

[Eamon]

Setup a device in smart pbx and set the invite format to be e164  "invite_format": "e164",

try that instead of the pbx connector 

[siibi]

Thanks again for the suggestion.

I have setup the 3CX as a device in smartpbx and removed the one in PBX connector. 

Still the RTP traffic is sourcing from the 3CX server.

After this, I have added & changed the following parameters in the device (database)

media.bypass_media to true and false

peer_to_peer to true and false

No change when I set these parameters. Are these directly active when I change them in the database or do I need to launch a sup commando ?

Any other ideas ?

Thanks a lot

Sibi

Op dinsdag 13 juni 2017 21:54:30 UTC+2 schreef Eamon:

[fred]

Are you sure the DB changes are taking effect?  If there is any doubt, reboot server(s).  I'm sure there are SUP commands but not 100% sure what they are.

[siibi]

For the trunkstore, I know the sup commando but not for the device document. 

Not 100% sure it takes effect when changing something in the device document.

Rebooting the server each time we add a device like this, is not an option. Anybody knows if we need to launch a sup commando for the device configuration if somehting is changed in the database ?

The parameter "peer_to_peer" is not documented in the https://github.com/2600hz/kazoo/blob/master/applications/crossbar/doc/devices.md

Is it a valid parameter ? It was by default there in Kazoo v4.

Op woensdag 14 juni 2017 16:57:02 UTC+2 schreef fred:

[fred]

Rebooting the server each time we add a device like this, is not an option.

That is what development servers are for.  Even just an all-in-one development server can test a lot of these things.  

I know there are SUP commands for this so you do not have to reboot in production once you test out what the commands are.

[James Aimonetti]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

You should not edit database documents unless absolutely necessary!

If you are editing a property of a device, a simple PATCH to
/devices/{DEVICE_ID} will suffice - the doc will be updated in the
database and the appropriate caches will be flushed of the device's old
config.

So please use the API; if you find yourself going to the database often,
let us know as an equivalent API should exist (and if not, we should
build one).

- --
James Aimonetti

Lead Systems Architect
"If Dialyzer don't care, I don't care"
2600HzPDX | http://2600hz.com
sip:ja...@2600hz.com
tel:415.886.7905
irc:mc_ @ freenode
-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEvSh+xZ5hP1H8lVIU1Mpr4k9cJWAFAllBXGwACgkQ1Mpr4k9c
JWDE5Qf8DfCpAP7C7hbSkya022AF87xnqjUn9n0akXMzJFycnCN24JSu/kX2ap67
lxL4Jjlh74V0iVNloMjKsZsvYB7cDTlI0WAQ31JilqgQIThDkWeXvhD1oM3RdaQI
tTmi4jPQDfWlszqdSuIjy+XYJb+SE3h9G0qjSRELVPi/U0Akgr5BSbYD+QoZhOip
kdfgU0d7vq8I3kzw1a9RAuZxmG06e7MBoeMAw0U7oteo4FHzFoMpJajPtBzHY7SQ
O8aLcs/1uUL0BaqJIvpZzmi1tXWTo6n5qJgAja+dIocmJFpIJW+Jgdu04H+0OOAV
gHf4XSvKuqXXJJUUJfijfIwJ3xOABw==
=a0kz
-----END PGP SIGNATURE-----