
Scalability&Reliability
Bydefault,theConnectionServerwillload‐balanceamongsttheconfiguredPortServers.PortServerscanalsobe
broughton‐lineanddynamicallyaddedtoroutinggroupsincaseoffailure.
BothConnectionServersandPortServerscanbedisabledformaintenancewithoutdisruptingconnectedclientsor
theirfaxes.Whiledisabled,
thatparticularserverwillrefuseanynewfaxes,andanyloggedinclientswillbe
migratedtoanotherConnectionServer.Anyfaxesinprogresswhentheserverisdisabledwillfinishwithout
interruption,butnewfaxeswillberoutedtoalternateservers,ifavailable.
InfrastructureRequirements
IIS/SQLServer
AnyversionofIISthatsupportsASP.NET2.0issufficienttoruntheHTTPSProxy.
AMicrosoftSQLServerversion2000oraboveisrequiredforthePortServerandBillingdatabases.Forsmaller
installations,MSDEorSQLServerExpressversionsaresufficient.
SIP+T.38media gateway
ThePortServermustbeconnectedtomediagatewaysthatsupportSIPandT.38.Foroutboundfaxes,themedia
gatewaymustre‐INVITEforT.38ifafaxisdetected.Forinboundfaxes,thePortServerwillimmediatelyre‐INVITE
forT.38.
EachPortServercanbeconfiguredtousea
SIPproxyinsteadusingaper‐PortServerusernameandpassword.
EachPortServercanbeconfiguredtosendREGISTERrequeststoaSIPregistrar.
Mediagatewaysthatareknowntoworkinclude(butarenotlimitedto):
• AudioCodesTrunkPackandMediantseries
• MostCiscorouters
T.38
trafficisexpectedtoconsumeapproximately60kbpsperactivefaxport.
UpstreamSIP TrunkingProvider
APortServercanbeconfiguredtouseanupstreamSIPtrunkingproviderinsteadofamediagateway.Insurethat
theupstreamprovidersupportsend‐to‐endT.38forreliablefaxing.Itisalsoimportanttohavealow‐latencylink
(lessthan50msround‐trip)totheprovider.
LAN/WANtopology
Atthistime,onlyIPv4networksaresupported.
HTTPStrafficisexpectedconsumeapproximately15kbpsperactivefaxport.
Komentáře k této Příručce