locked
SIP trunk configuration for Skype For Business Cloud Connector RRS feed

  • Question

  • Hi guys,

    We implement Skype for Business Cloud Connector on-premise  VMs on Hyper-V. (Building 1)
    Also take a SIP Trunk from our ITSP in Building 2. There is some questions as below:
    1-      Is it possible to forwarding SIP port from IP static in building 1 to IP static in Building2?
    2-      How should I edit configuration.ini file? Specific in voice gateway section… put IP static that related to building 2 or what?
    3-      Where should I use my SBC IP & IP address which I take with SIP Trunk modem
    PS: Network structure and Configuration file is attached. Please help us in this regards ….
    Thank you

    ; Build number 6.0.9319.419 - Keep this comment for diagnostic purpose 
    ;;;;;;;;;;;;;; Common (topology-wide) parameters. ;;;;;;;;;;;;;
    [Common]
    
    ;Domain(s) of SIP URIs used by company users.
    ;Domain(s) registered on O365.
    ;Support multiple domains separated by space. First domain is the default used.
    ;for phone URI.
    SIPDomains=mydomain.com
    
    ;Domain DNS suffix for the Skype for Business Cloud Connector Edition itself.
    ;Virtual machines CMS, Mediation server join this domain.
    ;Can be local (e.g. does not need to be in public DNS)
    ;MUST be different with domain(s) registered on O365
    VirtualMachineDomain=mydomain.local
    
    ;AD Server Name
    ;Server name which will be used to generate Server fqdn. It can NOT contain .<VirtualMachineDomain>. 15 Character LIMIT.
    ServerName=AD
    
    ;AD Server IP address
    IP=10.0.0.26
    
    ;O365 Online service FQDNs
    ;No need to change for world-wide O365 instance. For other instances, go to domain settings page in O365 portal to get the right Fqdns.  
    OnlineSipFederationFqdn=sipfed.online.lync.com
    
    ;Must update SiteName before deployment. Register-CcAppliance cmdlet uses SiteName to register current appliance to an existing or new site.
    ;If you want to register the appliance to an new site, SiteName must be unique and different from any other existing site in your Office 365 tenant configuration.
    ;If you want to register the appliance to an existing site, SiteName must match the site name defined in your Office 365 tenant configuration.
    ;If you are copying configuration file from one site to another, make sure you update the SiteName for each site correctly.
    SiteName=IranZamin
    
    ;Optional site parameters
    CountryCode=US
    City=Teh
    State=Teh
    
    ;The IP address of the VM that prepares base VM image
    ;This setting is only necessary for Convert-CcIsoToVhdx
    ;Leave this blank if DHCP is supported
    BaseVMIP=10.0.0.22
    
    ;The address of Windows Server Update Service - an intranet server to host updates from Microsoft Update
    ;Leave them blank if WSUS is not needed and we'll update from Windows Update site on the Internet instead
    WSUSServer=
    WSUSStatusServer=
    
    ;Type of hardware. The default value is Normal.
    ;You can also set to Minimum for smaller deployments that can support up to 50 simultaneous calls.
    HardwareType=Minimum
    
    ;If need to install OMS agent or not. Will automatic install OMS agent during deployment only if OMSEnabled=true.
    ;You can call Install-CcOMSAgent anytime to install the OMS agent manually into the running instance.
    OMSEnabled=false
    
    ;;;;;;;;;;;;;;;;;;;; Parameters for a pool of VM network. ;;;;;;;;;;;;;;;;;;;;
    [Network]
    
    ; For corpnet IPs
    CorpnetIPPrefixLength=16
    
    ; For Edge external IPs
    InternetIPPrefixLength=16
    
    ; The hyper-V switch names for corpnet and internet connectivity. 
    CorpnetSwitchName=SfB CCE Corpnet Switch
    InternetSwitchName=SfB CCE Internet Switch
    
    ;Default gateway in Corpnet
    ;Corpnet default gateway enables automatic updating the servers from the Corpnet
    ;It must be configured for Convert-CcIsoToVhdx to convert windows ISO file to VHDX file
    ;Corpnet default gateway will allow BaseVM to connect to internet and install window update packs
    CorpnetDefaultGateway=10.0.0.1
    
    ;Internet default gateway to enable edge server to connect O365 servers
    ;Remove or leave it as blank if don't want to configure default gateway
    InternetDefaultGateway=10.0.0.1
    
    ;DNS IP addresses for corpnet. Use space as separator if there are multiple addresses
    ;This setting is necessary for OS update when WSUS servers are not configured, or they are specified using domain names
    ;This DNS IP address will be added as a forwarder on the AD server
    ;During Convert-CcIsoToVhdx, this DNS IP address will be assigned to corpnet connection network adapter
    CorpnetDNSIPAddress=8.8.8.8
    
    ;Internet DNS IP address for resolving _sipfederationtls._tcp.<domain> and _sip._tls.<domain>
    ;This DNS IP address will be assigned to internet connection network adapter on Edge server
    ;The Edge server must be able to resolve public DNS records for the O365 Sip Domain
    ;If Gateway FQDN uses O365 Sip Domain in name for TLS purposes, be sure to set this IP Address to allow Edge to resolve these records
    InternetDNSIPAddress=8.8.8.8
    
    ; The management switch to provide network connectivity of host and VMs.
    ; ManagementIPPrefix in MUST be configured as different subnet from other internal IPs. 
    ; Just as the default value shown, ManagementIPPrefix is 192.168.213.0, while AD IPAddress is 192.168.0.238 
    ; The ManagementIPPrefixLength should be a value in range [8, 29]. 
    ManagementSwitchName=SfB CCE Management Switch
    ManagementIPPrefix=192.168.213.0
    ManagementIPPrefixLength=24
    
    ;;;;;;;;;;;;; Parameters for Primary Central Management Service. ;;;;;;;;;;;;;
    [PrimaryCMS]
    
    ;Server name which will be used to generate Server fqdn. It can NOT contain .<VirtualMachineDomain>. 15 Character LIMIT.
    ;Pool name will be the same as server name. 
    ServerName=CMSServer
    
    ;Server IP address
    IP=10.0.0.23
    
    ;File share name for Primary CMS File Store Service.
    ;Must be created on the Primary CMS server (used for replication of CMS data 
    ;to other servers and backup CMS)
    ShareName=CmsFileStore
    
    ;;;;;;;;;;;;;;;;;;;; Parameters for a pool of Mediation Servers. ;;;;;;;;;;;;;;;;;;;;
    [MediationServer]
    
    ;Server name which will be used to generate Server fqdn. It can NOT contain .<VirtualMachineDomain>. 15 Character LIMIT.
    ServerName=MedServer
    
    ;Pool name which will be used to generate pool fqdn. It can NOT contain .<DomainName>
    PoolName=mspool
    
    ;Server IP address
    IP=10.0.0.28
    
    ;;;;;;;;;;;;;;;;;;;; Parameters for a pool of Edge Servers. ;;;;;;;;;;;;;;;;;;;;
    [EdgeServer]
    
    ;Server name which will be used to generate Server fqdn. It can NOT contain .<VirtualMachineDomain>. 15 Character LIMIT.
    InternalServerName=EdgeServer
    
    ;Pool name which will be used to generate pool fqdn. It can NOT contain .<DomainName>
    ;FQDN of the Edge Pool internal interface must resolve to IP addresses on 
    ;internal interfaces of all edge servers (one A record per server)
    InternalPoolName=edgepool
    
    ;Internal IP addresses of servers in Edge Server Pool.
    ;Currently there is only one edge server in Edge Server Pool. We don't support multiple IP addresses.
    InternalServerIPs=10.0.0.25
    
    ;Pool name which will be used to generate pool fqdn. It can NOT contain .<DomainName>
    ;FQDN of the Edge Pool external interface for SIP traffic must resolve to 
    ;IP addresses on external interfaces of all edge servers (one 
    ;A record per server) or to the VIP of HLB (if HLB is used for SIP traffic).
    ;The suffix of this FQDN should be the default (first) internal domain.
    ;The "sip" prefix is not allowed. 
    ExternalSIPPoolName=ap
    
    ;External IP addresses of servers in Edge Server Pool for SIP traffic. 
    ;Public IP addresses if there is no NAT (firewall or HLB), 
    ;NAT-ed addresses otherwise.
    ;Currently there is only one edge server in Edge Server Pool. We don't support multiple IP addresses.
    ExternalSIPIPs=10.0.0.21
    
    ;Pool name which will be used to generate pool fqdn. It can NOT contain .<DomainName>
    ;FQDN of the Edge Pool external interface for media traffic must resolve to 
    ;IP addresses on external interfaces of all edge servers (one 
    ;A record per server) or to the VIP of HLB (if HLB is used for media traffic).
    ;Can be the same FQDN as External SIP FQDN (since there is no client 
    ;SIP traffic in this topology there is no conflict for port 443).
    ExternalMRFQDNPoolName=mr
    
    ;External IP addresses of servers in Edge Server Pool for Media traffic. 
    ;Public IP addresses if there is no NAT or firewall or HLB, 
    ;NAT-ed addresses otherwise.
    ;Can be the same IPs as External SIP IPs (since there is no client SIP traffic 
    ;in this topology there is no conflict for port 443).
    ;Currently there is only one edge server in Edge Server Pool. We don't support multiple IP addresses.
    ExternalMRIPs=10.0.0.21
    
    ;Public External IP addresses of servers in Edge Server Pool for Media 
    ;traffic. Should only be specified if NAT (firewall or HLB) is used.
    ;If NAT is not used, keep this element here and leave the value as blank.
    ;Currently there is only one edge server in Edge Server Pool. We don't support multiple IP addresses.
    ExternalMRPublicIPs=Building1 Static IP
    
    ;Public External port range for Media Relay (AV Edge role)
    ;MR port start from 50000, the range should be even number from 100 to 10000
    ;For both TCP and UDP
    ;Each concurrent call need 2 ports
    ;So the concurrent call capability in MR should be range / 2
    ;Note: concurrent call number also depends on the capability of PSTN Gateway
    ExternalMRPortRange=10000
    
    ;Parameters for gateway
    ;If only one Gateway is needed, remove entire [GateWay2] section. Don't keep it but leave values empty.
    ;If Gateway FQDN uses O365 Sip Domain in name for TLS purposes, be sure to set InternetDNSIPAddress to allow Edge to resolve these records
    [Gateway1]
    
    ; Gateway FQDN
    FQDN=Building 2 Static IP
    
    ;Gateway IP address
    IP=Building 2 Static IP
    
    ;Gateway Port
    Port=5060
    
    ;Protocol for SIP traffic (TCP or TLS)
    Protocol=TCP
    
    ;List of voice routes used by this gateway. 
    ;Routes are defined in the next section.
    VoiceRoutes=LocalRoute
    
    ;;;;;;;;;;;;;;;;;;;; Parameters for hybrid voice routing ;;;;;;;;;;;;;;;;;;;;
    [HybridVoiceRoutes]
    ;Named voice route to be used by one or more gateways
    LocalRoute=.*
    
    ;;;;;;;;;;;;;;;;;;;; Parameters for TrunkConfiguration ;;;;;;;;;;;;;;;;;;;;
    [TrunkConfiguration]
    ;Whether Gateways support Refer. It is used for Call Transfer scenario.
    ;The value can be "true" or "false". Default value is "true".
    ;EnableReferSupport set to "true" means the Gateway(s) support Refer which can handle all the call transfer stuffs.
    ;EnableReferSupport set to "false" means the Gateway(s) don't support Refer. Then Mediation Server will handle all the call transfer stuffs.
    EnableReferSupport=true
    
    ;Indicates whether outbound calls that are not answered by the gateway within 10 seconds will be routed to the next available trunk.
    ;If there are no additional trunks then the call will automatically be dropped.
    ;The value can be "true" or "false". Default value is "true".
    EnableFastFailoverTimer=true
    
    ;Indicates whether call history information will be forwarded through the trunk.
    ;The value can be "true" or "false". Default value is "false".
    ForwardCallHistory=false
    
    ;Indicates whether the P-Asserted-Identity (PAI) header will be forwarded along with the call.
    ;The value can be "true" or "false". Default value is "false".
    ForwardPAI=false

    Structure Schema : https:// i.stack.imgur.com/wCvQ5.jpg


    Monday, May 14, 2018 10:08 AM

All replies

  • Hi Omid,

     

     Is it possible to forwarding SIP port from IP static in building 1 to IP static in Building2?

    I did not see these configuration,but if you have deploy 2 CCE instances, then just use a different cloudconnector.ini file for each instance

     

    You’re connecting a SIP trunk from an ITSP, which should be Lync/Skype certified. To get a SIP trunk, you get two endpoints;

     

    IP A, Port 5060: ITSP (Internet Telephony Service Provider) – sided

    IP B, Port 5068: Cloud Connector ended, public IP Address and default TCP Port

    IP and Port A are included in the CloudConnector.ini, IP and Port B are non-existent during the initial deployment.


    Best Regards,
    Leon Lu


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    Tuesday, May 15, 2018 7:54 AM
  • Hi,

     

    Are there any update for this issue, if the reply is helpful to you, please try to mark it as an answer, it will help others who has similar issue.


    Best Regards,
    Leon Lu


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    Thursday, May 17, 2018 8:39 AM
  • Hi ,

     

    Do you have some updates? If the reply help to you ,please mark the reply as answer.


    Best Regards,
    Leon Lu


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    Wednesday, May 23, 2018 2:22 AM
  • Hi,

    sorry for long delay...

    Actually we don't want to deploy tow instance . We are looking for a solution that connect our SIP Trunk modem in Building 2 to our Cloud Connector servers in Building 1.

    Does Some thing like VPN or anything like that help ?

    Thursday, June 28, 2018 11:15 AM