Cloudversion and IP sip provider

Discussion in '3CX Phone System - General' started by troosters, Apr 16, 2015.

Thread Status:
Not open for further replies.
  1. troosters

    Joined:
    May 8, 2014
    Messages:
    17
    Likes Received:
    2
    Hi,
    I am testing a sip provider who does not use a account/password but just the public ip of my cloud server installation.
    Now, the provider only uses port 5060, so in my tenants it can only work for the tenant is using port 5060. So for the tenants using 6060 or 7060 and so on it would not work.
    BUT I just read that with the SBC's there can be some way to redirect the calls to the correct tenant even so.

    Is that true and if it is , can anyone assist me in this ?
     
  2. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    10,842
    Likes Received:
    298
    If the VoIP provider can only send to port 5060 (PUBLICIP:5060), then the only way to differentiate calls (send calls to the correct port) would be by analyizing the number the customer dialled and using that for routing. That may be beyond the 3CX SBC capabilities, but not to say that there isn't another piece of hardware with that ability.
     
  3. eagle2

    eagle2 Well-Known Member

    Joined:
    Apr 27, 2011
    Messages:
    1,085
    Likes Received:
    11
    This is not possible with 3CX cloud server (it works only with VoIP trunks with registration), unless you agree with your provider to customize the service he provides, from port 5060 to 6060, 7060, etc.

    Other option is to use a Cisco router and configure SIP ALG service to ports 6060, 7060, ... By default SIP ALG is enabled on port 5060 and works correctly for SDP/RTP (advanced Cisco knowledge required).

    Third option is to create your own SBC using Asterisk (it's free), register all 3CX tenants SIP trunks to Asterisk and handle the SIP trunks without registration in Asterisk (advanced Linux/Asterisk knowledge required).

    In any case you will need several IP addresses:port 5060 to/from provider translated with SIP ALG capable router to one IP address:different ports for each tenant, something like:

    10.20.30.1:5060 <=> 172.20.30.1:5060
    10.20.30.2:5060 <=> 172.20.30.1:6060
    10.20.30.3:5060 <=> 172.20.30.1:7060
    ...

    where 10.20.30.x are the addresses you use to present your self to provider, 172.20.30.1 is the address of 3CX cloud server

    In scenario with Asterisk you may use only one address, e.g. 10.20.30.1 for Asterisk and implement telephone number based routing (if acceptable by provider) and register 3CX cloud server tenants SIP trunks to it (from 172.20.30.1:x060)

    Regards,
    Orlin
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
Thread Status:
Not open for further replies.