Caddadkan waxaan ku tusi doonaa oo ku sharixi doonaa qaar ka mid ah qallafsanaanta dejinta server-ka CMS ee qaabka kutlada fashilantay.
AragtidaGuud ahaan, waxaa jira saddex nooc oo ah dejinta server-ka CMS:
- Keli ah oo la isku daray(hal la isku daray), i.e. Kani waa hal server oo ay ku shaqeeyaan dhammaan adeegyada lagama maarmaanka ah. Inta badan, hawlgelinta noocan ahi waxay ku habboon tahay oo keliya gelitaanka macmiilka gudaha iyo deegaanno yar yar oo xaddidan iyo xaddidid la'aanta hal server aysan ahayn arrin muhiim ah, ama xaaladaha CMS ay qabato oo keliya hawlo gaar ah, sida ad hoc shirarka Cisco UCM.
Qiyaasta nidaamka shaqada:
- Kala qaybsanaan kali ah(Single Split) waxay fidisaa noocii hore ee geynta iyadoo ku daraysa server u gaar ah gelitaanka dibadda. Soo-dejinta dhaxalka ah, tani waxay la macno tahay in la geeyo server-ka CMS ee qaybta shabakadda ee militariga ka go'an (DMZ) halkaasoo macaamiisha dibadda ay ka heli karaan, iyo hal server CMS oo ku jira xudunta shabakadda halkaasoo macaamiisha gudaha ay ka heli karaan CMS. Habkan geynta gaarka ah ayaa hadda lagu beddelay waxa loogu yeero nooca Cidhifka Keliya, kaas oo ka kooban server Cisco Expressway, kaas oo leh ama yeelan doona qaar badan oo isku mid ah awooda Firewall bypass si macaamiishu aysan ugu baahnayn inay ku daraan server CMS gees ah.
Qiyaasta nidaamka shaqada:
- La qiyaasi karo oo adkeysi leh(Scalable and Fault Tolerant) Noocaan waxaa ka mid ah dib-u-celinta qayb kasta, taasoo u oggolaanaysa nidaamku inuu ku koraan baahiyahaaga ilaa awooddiisa ugu badan iyadoo la siinayo dib-u-celin haddii ay dhacdo guuldarro. Waxa kale oo ay isticmaashaa fikradda Single Edge si ay u bixiso marin dibadeed oo sugan. Tani waa nooca aan ku eegi doono qaybtan. Haddii aan fahamno sida loo geeyo kooxdan noocaan ah, kaliya ma fahmi doonno noocyada kale ee hawlgelinta, laakiin sidoo kale waxaan awood u yeelan doonnaa inaan fahamno sida loo abuuro kooxo adeegayaal CMS ah si loo daboolo kobaca suurtagalka ah ee baahida.
Kahor intaadan u dhaqaaqin dirista, waxaad u baahan tahay inaad fahanto qaar ka mid ah waxyaabaha aasaasiga ah, kuwaas oo ah
Qaybaha software CMS ee ugu muhiimsan:
- databaseWaxay kuu ogolaanaysaa inaad isku xidho qaar ka mid ah habaynta, sida qorshaha garaacida, meelaha isticmaalaha, iyo isticmaalayaasha laftooda. Waxay taageertaa ururinta helitaan sare (hal sayid) oo keliya.
- Wac Buundada: adeeg loogu talagalay shirarka maqalka iyo muuqaalka ah kaas oo si buuxda u xakameynaya maaraynta iyo habaynta wicitaanada iyo hababka warbaahinta badan. Waxay taageertaa ururinta helitaanka sare iyo miisaanka.
- XMPP serverMas'uul ka ah diiwaangelinta iyo xaqiijinta macaamiisha isticmaalaya Codsiga Kulanka Cisco iyo/ama WebRTC(isgaarsiinta waqtiga-dhabta ah, ama si fudud browserka), iyo sidoo kale calaamadaynta qaybaha. Waxa lagu ururin karaa helitaan sare oo keliya.
- Buundada ShabakaddaWaxay siisaa macmiilka gelitaanka WebRTC.
- Isku-dheelitiriyaha: Waxay siisaa hal dhibic isku xidhka Cisco Meeting Apps oo ah hal nooc oo kala qaybsan. Waxay dhegaysataa is-dhexgalka dibadda iyo dekedda ee xidhiidhada soo socda. Si la mid ah, dheelitiriyaha culeyska ayaa aqbala isku xirka TLS ee ka imaanaya server-ka XMPP, kaas oo ay uga beddeli karto isku xirka TCP macaamiisha dibadda.
Xaaladeena looma baahnaan doono. - U rog server: Waxay bixisaa tignoolajiyada ka gudubta Firewall ee u oggolaanaysa
Dhig CMS-ga gadaasha Firewall ama NAT si loogu xidho macaamiisha dibadda adoo isticmaalaya Cisco Meeting App ama qalabka SIP. Xaaladeena looma baahnaan doono. - Maamulka ShabakaddaIsku xirka maamulka iyo gelitaanka API, oo ay ku jiraan shirarka CM Midaysan ee gaarka ah.
Hababka Habaynta
Si ka duwan badeecooyinka kale ee Cisco, Cisco Meeting Server waxa ay taageertaa saddex hab oo qaabaynta si loo dejiyo nooc kasta oo hawlgelin ah.
- Khadka taliska (CLI): interface line Command oo loo yaqaan MMP qaabeynta bilowga ah iyo hawlaha shahaado.
- Maamulaha Mareegta: Ugu horrayn isku xidhka CallBridge ee la xidhiidha, gaar ahaan marka la samaynayo hal serfer oo aan kooxaysan.
- nasasho APIWaxaa loo istcimaalaa hawlaha qaabaynta ee ugu adag iyo hawlaha la xidhiidha xog urursan.
Marka lagu daro kuwa kore, borotokoolka ayaa la isticmaalaa SFTP si aad ugu wareejiso faylalka-badanaa shatiyada, shahaadooyinka, ama diiwaanka-looga wareejinta iyo ka wareejinta serverka CMS.
Marka la eego hagaha dejinta ee Cisco waxay ku qoran tahay caddaan iyo Ingiriisi in kooxdu ay u baahan tahay in la geeyo ugu yaraan saddex server (nodes) ee macnaha guud ee xogta. Sababtoo ah Kaliya tiro aan caadi ahayn oo nood ah ayaa habka lagu dooranayo Database Master-ka cusub shaqayn doona, iyo guud ahaan Database Master-ku waxa uu xidhiidh la leeyahay inta badan xogta server-ka CMS.
Iyo sida dhaqanku muujinayo, laba server (nodes) runtii kuma filna. Habka xulashada wuxuu shaqeeyaa marka Master-ka dib loo bilaabo, Server-ka addoonku wuxuu noqdaa Master kaliya ka dib markii server-ka dib loo soo celiyay. Si kastaba ha noqotee, haddii koox ka kooban laba server uu Master-ka si lama filaan ah u baxo, markaas Server-ku ma noqon doono Master, haddii addoonkuna baxo, markaa Master-ka soo haray ayaa noqon doona addoon.
Laakiin marka la eego macnaha XMPP, runtii waa lagama maarmaan in la ururiyo koox ka kooban saddex server, sababtoo ah Haddii, tusaale ahaan, aad curyaamiso adeegga XMPP mid ka mid ah server-yada uu XMMP ku jiro heerka Hoggaaminta, markaa server-ka soo haray ee XMPP wuxuu ku sii jirayaa heerka Follower iyo xiriirinta CallBridge ee XMPP way dhici doontaa, sababtoo ah CallBridge waxay si gaar ah ugu xidhaa XMPP oo leh heerka hogaamiyaha. Tanina waa muhiim, sababtoo ah... hal wicitaan ma mari doono.
Sidoo kale isla meelaynta ayaa haga koox leh hal server XMPP ayaa la muujiyay.
Iyadoo la tixgelinayo kuwa kor ku xusan, waxay caddaynaysaa sababta: waxay u shaqeysaa sababtoo ah waxay ku jirtaa habka guul-darrada.
Xaaladeena, server-ka XMPP wuxuu ku jiri doonaa dhammaan saddexda nood.
Waxaa loo malaynayaa in dhammaan saddexda server-keennu ay kor u kacday.
Diiwaanada DNS
Kahor intaadan bilaabin dejinta server-yada, waxaad u baahan tahay inaad abuurto diiwaannada DNS А и SRV noocyada:
Fadlan la soco in diiwaannadayada DNS ay ku jiraan laba domains example.com iyo KOOCI.tusaale.com. Example.com waa goob ay dhammaan macaamiisha Isgaadhsiinta ee Cisco midaysan u isticmaali karaan URI-yadooda, taas oo ay u badan tahay inay ka dhex jiraan kaabayaashaaga ama ay u badan tahay inay joogaan. Ama example.com waxay la mid tahay isla bogga ay isticmaalayaashu u isticmaalaan ciwaanadooda iimaylka. Ama macmiilka Jabber ee laptop-kaaga ayaa laga yaabaa inuu haysto URI [emailka waa la ilaaliyay]. Domain KOOCI.example.com waa goobta loo habayn doono isticmaalayaasha Server Meeting Server. Goobta Server Meeting Server-ku waxa ay noqon doontaa KOOCI.example.com, marka isla isticmaale Jabber, user@ URI waxa uu u baahan doonaa in loo isticmaalo si loo galo Server Meeting ServerKOOCI.tusaale.com.
Qaabeynta aasaasiga ah
Dhammaan goobaha hoos lagu sharraxay waxaa lagu muujiyey hal server, laakiin waxay u baahan yihiin in lagu sameeyo server kasta oo kutlada ku jira.
QoS
Maadaama CMS ay abuurto waqtiga dhabta ah taraafikada u nugul daahitaanka iyo luminta xirmooyinka, inta badan waxaa lagu talinayaa in la habeeyo tayada adeegga (QoS). Si taas loo gaaro, CMS-du waxay taageertaa baakadaha sumadaynta ee Xeerarka Adeegyada Kala Duwan (DSCPs) ee ay soo saarto. In kasta oo mudnaanta taraafikada ku salaysan ee DSCP ay ku xidhan tahay sida taraafikada loogu habeeyo qaybaha shabakadda ee kaabayaashaaga, xaaladdeenna waxaan ku habeyn doonnaa CMS-yada mudnaanta DSCP ee caadiga ah iyadoo lagu saleynayo dhaqamada ugu wanaagsan ee QoS.
Server kasta waxaan geli doonaa amarradan
dscp 4 multimedia 0x22
dscp 4 multimedia-streaming 0x22
dscp 4 voice 0x2E
dscp 4 signaling 0x1A
dscp 4 low-latency 0x1AHaddaba, dhammaan taraafikada fiidyaha waxaa lagu calaamadeeyay AF41 (DSCP 0x22), dhammaan taraafikada codka waxaa lagu calaamadeeyay EF (DSCP 0x2E), noocyada kale ee taraafikada daahitaanka hooseeya sida SIP iyo XMPP waxay isticmaalaan AF31 (DSCP 0x1A).
Hubinta:
NTP
Nidaamka Waqtiga Shabakadda (NTP) muhiim uma aha oo kaliya bixinta waqtiyada saxda ah ee wicitaanada iyo shirarka, laakiin sidoo kale xaqiijinta shahaadooyinka.
Ku dar server-yada NTP kaabayaashaaga amar sida
ntp server add <server>
Xaaladeena, waxaa jira laba server oo noocaas ah, markaa waxaa jiri doona laba kooxood.
Hubinta:
Oo u deji aagga wakhtiga server-kayaga
DNS
Waxaan ku darnaa server-yada DNS CMS oo leh amar sida:
dns add forwardzone <domain-name> <server ip>
Xaaladeena, waxaa jira laba server oo noocaas ah, markaa waxaa jiri doona laba kooxood.
Hubinta:
Isku xidhka Interface Configuration
Waxaan ku habeyneynaa interface-ka amar sida:
ipv4 <interface> add <address>/<prefix length> <gateway>
Hubinta:
Magaca adeegaha (magaca martida)
Waxaan dejinay magaca serverka oo wata amar sida:
hostname <name>
Oo waanu dib u bilownay.
Tani waxay dhamaystiraysaa qaabeynta aasaasiga ah.
Shahaadooyinka
AragtidaServer Meeting Server wuxuu u baahan yahay isgaarsiin qarsoodi ah oo ka dhexeeya qaybo kala duwan, natiijaduna, shahaadooyinka X.509 ayaa looga baahan yahay dhammaan hawlgelinta CMS. Waxay gacan ka geystaan hubinta in adeegyada/serverka ay ku kalsoon yihiin adeegayaasha/adeegyada kale.
Adeeg kastaa wuxuu u baahan yahay shahaado, laakiin abuurista shahaado gaar ah adeeg kasta waxay u horseedi kartaa jahawareer iyo kakanaanta aan loo baahnayn. Nasiib wanaag, waxaan soo saari karnaa shahaado lammaanaha muhiimka ah ee dadweynaha iyo gaarka ah ka dibna dib ayaan uga isticmaali karnaa adeegyo badan. Xaaladeena, shahaado isku mid ah ayaa loo isticmaali doonaa Wicitaanka Wicitaanka, XMPP Server, Buundada Shabakadda iyo Maamulka Shabakadda. Haddaba, waxaad u baahan tahay inaad abuurto labo fure shahaado dadweyne iyo mid gaar ah seerfar kasta oo ka tirsan kooxda.
Isku dhafka xogta, si kastaba ha ahaatee, waxay leedahay shuruudo shahaado gaar ah, sidaas darteedna waxay u baahan tahay shahaado u gaar ah oo ka duwan kuwa adeegyada kale. CMS waxay isticmaashaa shahaadada server-ka, taas oo la mid ah shahaadooyinka ay isticmaalaan server-yada kale, laakiin sidoo kale waxaa jirta shahaadada macmiilka ee loo isticmaalo isku xirka xogta. Shahaadooyinka database-ka waxaa loo isticmaalaa xaqiijinta iyo sirta labadaba. Halkii laga siin lahaa isticmaale-magaca iyo erayga sirta ah ee macmiilka si uu ugu xidho kaydka xogta, waxa ay soo bandhigaysaa shahaado macmiilka oo uu ku kalsoon yahay server-ku. Serfer kasta oo ku jira kutlada kaydka xogta ayaa isticmaali doona lamaane furaha dadweynaha iyo kuwa gaarka ah. Tani waxay u oggolaanaysaa dhammaan server-yada kooxda in ay sir xogta si ay u furto oo kaliya server-yada kale ee sidoo kale wadaaga isla lamaanaha muhiimka ah.
Si shaqo-ka-dhisista loogu shaqeeyo, kooxuhu waa inay ka kooban yihiin ugu yaraan 3 adeegayaal, laakiin aan ka badnayn 5, oo leh ugu badnaan wakhtiga safarka wareega ee 200 ms inta u dhaxaysa xubnaha koox kasta. Xadkaani wuu ka xaddidan yahay marka loo eego isku dhafka Call Bridge, sidaas darteed inta badan waa qodobka xaddidaya diritaannada juqraafi ahaan loo qaybiyay.
Doorka kaydka xogta ee CMS waxa ay leedahay tiro shuruudo gaar ah. Si ka duwan doorarka kale, waxay u baahan tahay macmiilka iyo shahaadada server-ka, halkaas oo shahaadada macmiilku ay leedahay goob gaar ah oo CN ah oo loo soo bandhigay server-ka.
CMS waxay isticmaashaa xogta boostada oo leh hal sayid iyo dhowr nuqul oo gebi ahaanba isku mid ah. Waxa jira hal mar oo keliya xogta aasaasiga ah ("serverka database"). Xubnaha soo hadhay ee kooxdu waa nuqul ama "macaamiisha xogta database".
Kutlada keydka macluumaadka waxay u baahan tahay shahaado server oo gaar ah iyo shahaado macmiil. Waa inay saxeexaan shahaadooyin, badanaaba hay'ad shahaado gaar ah oo gudaha ah. Sababtoo ah xubin kasta oo ka mid ah kutlada xogta waxay noqon kartaa sayid, kaydka xogta iyo lammaanaha shahaadaynta macmiilka (oo ay ku jiraan furayaasha dadweynaha iyo kuwa gaarka ah) waa in lagu koobiyeeyo dhammaan server-yada si ay u qaataan aqoonsiga macmiilka ama kaydka xogta. Intaa waxaa dheer, shahaadada xididka CA waa in la raro si loo hubiyo in macmiilka iyo shahaadooyinka server-ka la xaqiijin karo.
Markaa, waxaanu abuurnay codsi shahaado ah oo ay isticmaali doonaan dhammaan adeegyada server-ka marka laga reebo kaydka xogta (waxaa jiri doona codsi gooni ah tan) oo leh amar sida:
pki csr hostname CN:cms.example.com subjectAltName:hostname.example.com,example.com,conf.example.com,join.example.com
Gudaha CN waxaan ku qornaa magaca guud ee adeegayaashayada. Tusaale ahaan, haddii magacyada martida loo yahay ee server-yadayada server01, server02, server03, ka dibna CN wuxuu noqon doonaa server.example.com
Waxaan ku sameynaa si la mid ah labada server ee soo haray iyadoo ay ku kala duwan yihiin amarrada ay ka koobnaan doonaan "hostnames" u dhigma
Waxaan abuurnaa laba codsi oo shahaadooyin ah oo ay isticmaali doonaan adeegga keydka macluumaadka oo wata amarro sida:
pki csr dbclusterserver CN:hostname1.example.com subjectAltName:hostname2.example.com,hostname3.example.com
pki csr dbclusterclient CN:postgreshalkaas oo dbclusterserver и macmiilka dbcluster Magacyada codsiyadayada iyo shahaadooyinka mustaqbalka, magaca martida1 (2) (3) Magacyada server-yada u dhigma.
Nidaamkan waxaan ku sameynaa kaliya hal server (!), Oo waxaan ku dhejin doonaa shahaadooyinka iyo faylasha muhiimka ah ee u dhigma server-yada kale.
Daar qaabka shahaadada macmiilka ee AD CS
Waxaad sidoo kale u baahan tahay inaad ku biirto shahaadooyinka server kasta hal fayl.On *NIX:
cat server01.cer server02.cer server03.cer > server.cerDaaqadaha/DOS:
copy server01.cer + server02.cer + server03.cer server.cer
Oo u soo rar server kasta:
1. Shahaadada serverka "Shakhsi".
2. Shahaadada xididka (oo ay la socdaan kuwa dhexdhexaadka ah, haddii ay jiraan).
3. Shahaadooyinka kaydka xogta ("server" iyo "macmiilka") iyo faylalka wata kordhinta furaha, kuwaas oo la sameeyay markii la abuurayo codsiga shahaadooyinka "server" iyo "macmiilka". Faylashani waa inay isku mid noqdaan dhammaan server-yada.
4. Faylka dhammaan saddexda shahaado "shakhsi".
Natiijo ahaan, waa inaad ka heshaa wax la mid ah sawirka faylkan ee server kasta.
Kooxda Xogta
Hadda oo aad haysato dhammaan shahaadooyinka lagu shubay server-yada CMS, waxaad habayn kartaa oo aad awood u yeelan kartaa ururinta xogta inta u dhaxaysa saddexda nood. Talaabada ugu horeysa waa in la doorto hal server oo ah noodhka sare ee kutlada xogta oo si buuxda loo habeeyo.
Xogta Masterka
Talaabada ugu horeysa ee samaynta ku celcelinta xogta macluumaadka waa in la caddeeyo shahaadooyinka loo isticmaali doono database-ka. Tan waxaa lagu sameeyaa iyadoo la adeegsanayo amar sida:
database cluster certs <server_key> <server_crt> <client_key> <client_crt> <ca_crt>Hadda aan u sheegno CMS interface ka loo isticmaalo ururinta xogta ee amarka:
database cluster localnode aKadibna waxaan ku bilownay xogta kutlada ee server-ka ugu weyn ee leh amarka:
database cluster initialize
Nodes Database Macmiil
Waxaan samaynaa hab isku mid ah, kaliya halkii amarka kutlada database bilowga geli amarka sida:
database cluster join <ip address existing master>halkaas oo ciwaanka IP-ga jira ee ciwaanka ip-ga ah ee server-ka CMS kaas oo kooxda lagu bilaabay, si fudud Master.
Waxaan hubinaa sida ay kooxdayada xog ururinta uga shaqeyso dhammaan server-yada leh amarka:
database cluster status
Waxaan sidaas oo kale ku sameynaa server-ka saddexaad ee soo haray.
Natiijo ahaan, waxaa soo baxday in server-keena ugu horreeya uu yahay Master, inta kale waa addoomo.
Adeegga Maamulka Shabakadda
Daar adeega maamulka shabakada:
webadmin listen a 445Dekedda 445 ayaa la doortay sababtoo ah dekedda 443 waxaa loo isticmaalaa marin u helka macmiilka shabakadda
Waxa aanu ku habeynay adeega maamulka shabakada faylal shahaado ah oo wata amar sida:
webadmin certs <keyfile> <certificatefile> <ca bundle>Oo awood u yeelo Web Admin amarka:
webadmin enable
Haddii wax walba hagaagaan, waxaan heli doonaa khadadka GUUSHA ee tilmaamaya in Admin Web si sax ah loogu habeeyey shabakada iyo shahaadada. Waxaan eegnaa shaqada adeegga anagoo adeegsanayna biraawsarkaaga, waxaanan galnaa cinwaanka maamulaha shabakadda, tusaale ahaan: : 445
Wac Kooxda Buundada
Wicitaanada Wicitaanku waa adeega kaliya ee ka jira diritaan kasta oo CMS ah. Wicitaanada Wicitaanku waa habka shirarka ee ugu muhiimsan. Waxa kale oo ay bixisaa is-dhexgalka SIP si wicitaannada loo mariyo ama looga soo diro, tusaale ahaan, Cisco Unified CM.
Awaamiirta hoos lagu sharraxay waa in lagu fuliyaa server kasta oo wata shahaadooyin ku habboon.
Sidaas awgeed:
Waxa aanu ku xidhxidhay shahaadooyinka adeega Wicitaanka Biriijka amar sida:
callbridge certs <keyfile> <certificatefile>[<cert-bundle>]Waxaan ku xireynaa adeegyada CallBridge interface-ka aan uga baahanahay amarka:
callbridge listen aOo dib ugu bilow adeegga amarka:
callbridge restart
Hadda oo aan haysanno Wicitaanada Wicitaanka, waxaan habayn karnaa isku dhafka Call Bridge. Kutlada Wicitaanku way ka duwan yihiin xogta xogta ama ururinta XMPP. Kooxda Wicitaanka Bridge waxay taageeri kartaa min 2 ilaa 8 nood iyada oo aan wax xannibaad ah lahayn. Waxay bixisaa ma aha oo kaliya dib-u-celinta, laakiin sidoo kale culeyska culeyska si shirarka si firfircoon loogu qaybiyo server-yada Call Bridge iyadoo la adeegsanayo qaybinta wacitaanka caqli-gal ah. CMS waxay leedahay astaamo dheeri ah, Kooxaha Wicitaanka Buundada iyo astaamo la xidhiidha oo loo isticmaali karo maarayn dheeraad ah.
Isku dhafka buundada wacitaanka waxaa lagu habeeyey ugu horeyn iyada oo loo marayo interface adminka webka
Habka hoos lagu sharaxay waa in lagu fuliyaa server kasta oo kutlada ah.
Sidaas
1. U gudub shabakada si aad u hesho Habayn > Kooxda.
2. In Wac aqoonsiga Bridge Sida magac gaar ah, geli callbridge[01,02,03] oo u dhiganta magaca serverka. Magacyadani waa qaylo-dhaan, laakiin waa inay gaar u ahaadaan kooxdan. Waxay yihiin kuwo sifeynaya dabeecadda sababtoo ah waxay muujinayaan inay yihiin aqoonsiga server-ka [01,02,03].
3.B Buundooyinka Wicitaanka Kooxaysan geli URL-yada maamulaha shabakada ee adeegayaashayada kutlada, [01,02,03].tusaale.com:445, ee goobta ciwaanka. Hubi inaad qeexdo dekedda. Waxaad ka tagi kartaa isku xirka Peer SIP domain madhan.
4. Ku dar shahaado kalsoonida CallBridge ee server kasta, faylka uu ka kooban yahay dhammaan shahaadooyinka server-kayaga, kaas oo aan ku milnay faylkan bilowgii hore, iyada oo amar ah:
callbridge trust cluster <trusted cluster certificate bundle>Oo dib ugu bilow adeegga amarka:
callbridge restart
Natiijo ahaan, server kasta waa inaad ka heshaa sawirkan:
Kooxda XMPP
Adeegga XMPP ee ku jira CMS waxa loo isticmaalaa in lagu maamulo dhammaan diiwaangelinta iyo xaqiijinta Cisco Meeting Apps (CMA), oo ay ku jirto macmiilka shabakadda CMA WebRTC. Buundada Wicitaanka lafteedu waxay sidoo kale u shaqeysaa sidii macmiil XMPP ujeeddooyin xaqiijineed sidaa darteed waa in loo habeeyaa sida macaamiisha kale. Dulqaadashada qaladka XMPP waa sifo lagu taageeray jawiga wax soo saarka ilaa nooca 2.1
Awaamiirta hoos lagu sharraxay waa in lagu fuliyaa server kasta oo wata shahaadooyin ku habboon.
Sidaas awgeed:
Waxaan ku xidhxidhay shahaadooyinka adeega XMPP amar sida:
xmpp certs <keyfile> <certificatefile>[<cert-bundle>]Kadibna ku qeex interface-ka dhageysiga amarka:
xmpp listen aAdeegga XMPP wuxuu u baahan yahay goob gaar ah. Kani waa galitaanka isticmaalayaasha Si kale haddii loo dhigo, marka adeegsaduhu isku dayo inuu galo isagoo isticmaalaya abka CMA (ama macmiilka WebRTC), waxay galaan userID@logindomain. Xaaladeena waxay noqon doontaa userid@KOOCI.tusaale.com. Waa maxay sababta aysan tusaale ahaan.com u ahayn? Hawlgelintayada gaarka ah, waxaanu ku dooranay boggayaga Midaysan ee CM kaas oo isticmaalayaasha Jabber ay ku isticmaali doonaan CM Midaysan tusaale ahaan.com, marka waxaan u baahnay qayb ka duwan isticmaalayaasha CMS si ay ugu soo wacaan ugana soo celiyaan CMS-ga iyada oo loo sii marayo boggaga SIP.
Samee domain XMPP adoo isticmaalaya amar sida:
xmpp domain <domain>Oo awood adeega XMPP amarka:
xmpp enableAdeegga XMPP, waa in aad u samaysaa aqoonsi buundada Wicitaan kasta oo la isticmaali doono marka la iska diiwaan gelinayo adeegga XMPP. Magacyadani waa qaylo-dhaan (kumana xidhna magacyada gaarka ah ee aad u habaysay isu-ururinta buundada wacitaanka). Waa inaad ku darto saddex buundooyinka wacitaanka hal server oo XMPP ah ka dibna geli shahaadooyinkaas server-yada kale ee XMPP ee kutlada sababtoo ah qaabeyntani kuma habboona kaydinta xogta. Ka dib waxaan u habeyn doonaa buundada Wicitaan kasta si uu u isticmaalo magacan iyo sirtan si aan isaga diiwaan geliyo adeegga XMPP.
Hadda waxaan u baahanahay inaan ku habeyno adeegga XMPP seerfarka ugu horreeya oo leh saddex Call Bridges callbridge01, callbridge02 iyo callbridge03. Akoon kasta waxa lagu meelayn doonaa furaha sirta ah ee aan tooska ahayn. Mar dambe ayaa lagu geli doonaa adeegayaasha kale ee Wicitaanka Buundada si ay u galaan server-kan XMPP. Geli amarradan soo socda:
xmpp callbridge add callbridge01
xmpp callbridge add callbridge02
xmpp callbridge add callbridge03Natiijo ahaan, waxaan ku hubineynaa waxa ku dhacay amarka:
xmpp callbridge list
Isla sawir la mid ah waa inuu ka soo muuqdaa server-yada haray ka dib tillaabooyinka hoos lagu sharraxay.
Marka xigta, waxaan ku darnaa isla jaangooyooyin isku mid ah labada server ee soo haray, kaliya oo leh amarrada
xmpp callbridge add-secret callbridge01
xmpp callbridge add-secret callbridge02
xmpp callbridge add-secret callbridge03Waxaan si taxadar leh ugu darnaa sirta si, tusaale ahaan, aysan u jirin meelo dheeraad ah.
Natiijo ahaan, server kastaa waa inuu lahaadaa sawir isku mid ah:
Marka xigta, dhammaan server-yada kooxda, waxaan ku cadeyneynaa kalsoonida faylka ka kooban dhammaan seddexda shahaado, oo horey loo abuuray amar sidan oo kale ah:
xmpp cluster trust <trust bundle>Waxaan awood u siineynaa qaabka xmpp kutlada dhammaan server-yada kutlada leh amarka:
xmpp cluster enableSeerfarka ugu horreeya ee kooxda, waxaanu ku bilaabaynaa abuurista koox xmpp ah oo leh amarka:
xmpp cluster initializeSerfarada kale, kudar kutlada xmpp oo wata amar sida:
xmpp cluster join <ip address head xmpp server>Waxaan hubineynaa server kasta guusha abuurista kooxda XMPP ee server kasta oo leh amarrada:
xmpp status
xmpp cluster statusAdeegga koowaad:
Seerfar labaad:
Seerfar saddexaad:
Ku xidhida Buundada Wicitaanka ee XMPP
Hadda oo kooxda XMPP ay shaqaynayso, waxaad u baahan tahay inaad habayso adeegyada Wicitaanka Buundada si aad ugu xidho kooxda XMPP. Qaabayntan waxa lagu sameeyaa maamulka shabakada
Seerfar kasta, u gudub qaabaynta> Guud iyo gudaha goobta Magaca Biriijka Wicitaan ee Gaarka ah qor magacyo gaar ah oo u dhigma serverka Wicitaanka Bridge callbridge[01,02,03]... Garoonka dhexdiisa Domain conf.tusaale.ru iyo furaha sirta ah ee u dhigma, waad basaasiin kartaa iyaga
server kasta oo kutlada leh amarka:
xmpp callbridge list
Ka tag goobta "Serverka" oo faaruq ah Callbridge wuxuu samayn doonaa raadinta DNS SRV _xmpp-qayb._tcp.conf.example.comsi loo helo server XMPP ah oo la heli karo. Cinwaanka IP-ga ee isku xirka callbridges ee XMPP way ku kala duwanaan karaan server kasta, waxay kuxirantahay waxa qiyamka lagu celiyo codsiga diiwaanka _xmpp-qayb._tcp.conf.example.com callbridge, taas oo iyana ku xiran goobaha mudnaanta ee diiwaanka DNS ee la bixiyay.
Marka xigta, aad Xaaladda> Guud si aad u xaqiijiso in adeegga Wicitaanka aroosadda uu si guul leh ugu xiran yahay adeegga XMPP.
Buundada Shabakadda
Seerfar kasta oo ka tirsan kooxda, awood u geli adeegga Buundada Shabakadda ee leh amarka:
webbridge listen a:443Waxaan ku habeyneynaa adeegga Buundada Shabakadda faylal shahaado ah oo wata amar sida:
webbridge certs <keyfile> <certificatefile> <ca bundle>Web Bridge waxay taageertaa HTTPS. Waxay HTTP u wareejin doontaa HTTPS haddii loo habeeyo inay isticmaasho "http-redirect".
Si aad awood u siiso dib u jiheynta HTTP, adeegso amarka soo socda:
webbridge http-redirect enableSi aad u ogeysiiso Wicitaanka Buundada in Buundada Shabakadda ay aamini karto isku xirka Wicitaanka, adeegso amarka:
webbridge trust <certfile>halkaas oo uu kani yahay fayl ka kooban dhammaan saddexda shahaado ee server kasta oo kutlada.
Sawirkaani waa inuu ku yaal server kasta oo kutlada.
Hadda waxaan u baahanahay inaan abuurno isticmaale leh doorka "appadmin", waxaan u baahanahay si aan u habayn karno kooxdayada (!), Oo ma aha server kasta oo ku jira kooxda si gaar ah, habkan ayaa goobaha si siman loogu dabaqi doonaa server kasta inkastoo xaqiiqda ah in la samayn doono hal mar.
Habayn dheeraad ah ayaanu isticmaali doonaa .
Oggolaanshaha, dooro aasaaska qaybta oggolaanshaha
Si aad si sax ah ugu dirto amarada server-ka CMS, waxaad u baahan tahay inaad dejiso codaynta loo baahan yahay
Waxaan ku qeexnay Webbridge oo leh amarka POST oo leh halbeeg url iyo macnaha
Buundada lafteeda, waxaan ku tusinaa xuduudaha loo baahan yahay: gelitaanka martida, gelitaanka la ilaaliyo, iwm.
Wac kooxaha Bridge
Sida caadiga ah, CMS had iyo jeer ma samayso isticmaalka ugu hufan ee agabka shirarka ee uu heli karo.
Tusaale ahaan, kulanka saddex ka-qaybgale, ka qaybgale kasta waxa laga yaabaa inuu ku dhammaado saddex buundooyin wac oo kala duwan. Si saddexdan ka qaybgalayaashu ay midba midka kale ugu wada xidhiidhaan, Wicitaanka Buundooyinka waxay si toos ah u samayn doonaan isku xidhka dhammaan server-yada iyo macaamiishooda isla Booska, si ay dhammaan u ekaato in dhammaan macaamiishu ay ku jiraan isku server. Nasiib darro, dhinaca hoose ee tani waa in hal shir oo 3 qof ah uu hadda cuni doono 9 dekedood oo warbaahin ah. Tani waxay caddahay inay tahay isticmaalka kheyraadka oo aan waxtar lahayn. Intaa waxaa dheer, marka buundada Wicitaanka si dhab ah loo raro, habka caadiga ah waa in la sii wado aqbalka wicitaanada oo la siiyo adeeg tayo leh oo la dhimay dhammaan macaamiisha Buundada Wicitaanka.
Dhibaatooyinkan waxaa lagu xalliyaa iyada oo la adeegsanayo muuqaalka Kooxda Wicitaanka Bridge. Sifadan waxaa lagu soo bandhigay nooca 2.1 ee software-ka Server-ka kulanka waxaana la kordhiyey si ay u taageerto isu dheelitirka culeyska ee wicitaanada gudaha iyo dibadda ee Cisco Meeting App (CMA), oo ay ku jiraan kaqeybgalayaasha WebRTC.
Si loo xalliyo dhibaatada dib-u-xidhka, saddex xaddidaad oo la hagaajin karo ayaa loo soo bandhigay Buundada Wicitaan kasta:
Xaddidaad — kani waa tirada ugu badan ee buundada Wicista ee gaarka ah. Goob kastaa waxay leedahay xaddid lagu taliyey, sida 96000 ee CMS1000 iyo 1.25 GHz vCPU ee mashiinka farsamada. Wicitaanada kala duwani waxay isticmalaan qadar go'an oo agab ah taas oo ku xidhan xalinta iyo heerka jir ee ka qaybqaataha.
NewConferenceLoadLimitBasisPoints (default 50% loadLimit) - dejiyaa xadka culeyska server-ka, ka dib shirarka cusub waa la diidaa.
Conference LoadLimitBasisPoints (default 80% of loadLimit) - qiimaha rarka serverka ka dib ka qaybgalayaasha ku biiraya shir jira waa la diidi doonaa.
Iyadoo sifadan loogu talagalay qaybinta wicitaanka iyo isu dheelitirka culeyska, kooxaha kale sida TURN Servers, Web Bridge Servers iyo Recorders ayaa sidoo kale lagu meelayn karaa kooxaha Wicitaanka Buundada si ay sidoo kale si habboon loogu kooxeeyo isticmaalka ugu habboon. Haddii mid ka mid ah walxahan aan lagu meelayn kooxda wacitaanka, waxaa loo maleynayaa inay diyaar u yihiin dhammaan server-yada iyada oo aan lahayn mudnaan gaar ah.
Halbeegyadan waxaa lagu habeeyey halkan: :445/api/v1/system/configuration/cluster
Marka xigta, waxaanu tusinaynaa callbridge kasta kooxda callbridge ay ka tirsan tahay:
Marka hore wacbridge
Buundada labaad
Third callbridge
Sidaa darteed, waxaan u habeynay kooxda Wicitaanka Brdige si ay si hufan u isticmaalaan agabka kutlada Server Meeting Server.
Ka soo dejinta isticmaalayaasha Hagaha Active
Adeegga Maamulka Shabakadda waxa uu leeyahay qaybta qaabaynta LDAP, laakiin ma bixiyo doorashooyin isku dhafan oo isku dhafan, macluumaadkana laguma kaydiyo xogta kutlada, markaa qaabaynta waa in lagu sameeyaa, iyada oo gacanta lagu hayo server kasta iyada oo loo sii marayo Interface-ka Shabkada, ama iyada oo loo marayo API, iyo si aan "saddex jeer" "Ha kicin" waxaan weli dejin doonaa xogta iyada oo loo marayo API.
Isticmaalka URL si loo galo :445/api/v1/ldapServers waxay abuuraan shay Server LDAP, iyaga oo tilmaamaya cabbirro sida:
- Adeegaha IP
- lambarka dekedda
- Magaca isticmaalaha
- furahaaga
- aamin
Secure - door run ama been ku xiran dekedda, 389 - ma ammaan, 636 - ilaaliyo.
Khariidaynta xuduudaha isha LDAP ee sifooyinka ku jira Server Meeting Server.
Khariidaynta LDAP waxay u dejisaa sifooyinka ku jira tusaha LDAP sifooyinka CMS. Sifooyinka dhabta ah:
- jidMapping
- Khariidaynta magaca
- CoSpaceNameMapping
- coSpaceUriMapping
- coSpaceSecondaryUriMapping
Sharaxaada sifooyinkaJID waxay ka dhigan tahay aqoonsiga galitaanka isticmaalaha ee CMS. Maadaama uu kani yahay adeegaha Microsoft Active Directory LDAP, khariidadaha CMS JID ee sAMAccountName ee LDAP, kaas oo asal ahaan ah aqoonsiga gelitaanka Hagaha Active ee isticmaalaha. Sidoo kale ogow in aad qaadato sAMAccountName oo aad kudarto domainka conf.pod6.cms.lab dhamaadkiisa sababtoo ah tani waa galitaanka isticmaalayaashaadu u isticmaali doonaan si ay u galaan CMS.
Khariidaynta magaca ku dhigma waxa ku jira goobta bandhiga Hagaha firfircoon ee magaca isticmaalaha goobta magaca CMS.
CoSpaceNameMapping abuuraa magac meel bannaan oo CMS ah oo ku salaysan goobta bandhigaName. Sifadan, oo ay weheliso sifada coSpaceUriMapping, waa waxa loo baahan yahay si loogu sameeyo meel bannaan isticmaale kasta.
coSpaceUriMapping qeexayaa qaybta adeegsadaha ee URI ee la xidhiidha booska gaarka ah ee isticmaalaha. Domainyada qaarkood waxaa loo habayn karaa in lagu wacdiyo meel bannaan. Haddii qaybta adeegsaduhu ay ku habboonaato goobtan mid ka mid ah xayndaabyadan, wicitaanku wuxuu ku jihaysan doonaa booska isticmaalaha.
coSpaceSecondaryUriMapping qeexaya URI labaad si loo gaaro meel bannaan. Tan waxa loo istcimaali karaa in lagu daro naanaysta nambarada loogu talagalay soo-gudbinta wicitaanada goobta isticmaalaha la soo dhoofiyo si ay beddel ugu noqoto URI-ga alfanumeric ee lagu qeexay cabbirka coSpaceUriMapping.
Serfarka LDAP iyo khariidaynta LDAP waa la habeeyey. Hadda waxaad u baahan tahay inaad isku xirto iyaga oo abuuraya isha LDAP.
Isticmaalka URL si loo galo :445/api/v1/ldapSource waxay abuurtaa shay Isha LDAP, oo qeexaya cabirrada sida:
- server
- khariidaynta
- baseDn
- filter
Hadda oo qaabaynta LDAP dhammaatay, waxaad samayn kartaa hawlgalka isku xidhka gacanta.
Tani waxaynu ku samaynaa mid ka mid ah interface-ka Webka ee server kasta adigoo gujinaya Sync hada qaybta Tusaha Hawl-galka
ama adoo adeegsanaya API-ga amarka POST adigoo isticmaalaya URL si loo galo :445/api/v1/ldapSyncs
Shirarka Ad-Hoc
Waa maxay tani?Fikradda dhaqameed, shirku waa marka ay laba kaqeybgalayaashu wada hadlaan, mid ka mid ah ka qaybgalayaasha (adoo isticmaalaya qalab ka diiwaan gashan Unified CM) ayaa riixaya badhanka "Conference", oo wacaya qofka kale, ka dib markii uu la hadlo qolo saddexaad. , taabo badhanka "Shirka" mar labaad si aad ugu biirto dhammaan ka qaybgalayaasha shirka saddex geesoodka ah.
Waxa ka sooca shirka Ad-Hoc iyo shir la qorsheeyay ee CMS waa in shirka Ad-Hoc aanu ahayn kaliya wicitaan SIP ah ee CMS. Marka hindisaha shirku uu mar labaad riixo badhanka shirka si uu qof walba ugu yeedho isla kulanka, Midaysan CM waa in uu API ugu yeedhaa CMS si uu u sameeyo shir-ku- duulaya kaas oo dhamaan wicitaanada lagu wareejiyo. Waxaas oo dhami waxay dhacaan iyagoon ka qaybgalayaashu ogaan.
Tani waxay ka dhigan tahay in Midaysan CM waa inuu habeeyaa aqoonsiga API iyo cinwaanka WebAdmin / dekedda adeegga iyo sidoo kale SIP Trunk si toos ah serverka CMS si uu u sii wado wicitaanka.
Haddii loo baahdo, CUCM waxay si firfircooni ah u abuuri kartaa meel bannaan oo CMS ah si wicitaan kastaa u gaaro CMS oo uu u dhigmo xeerka wicitaanka ee loogu talagalay meelaha bannaan.
Is dhexgalka CUCM loo habeeyey si la mid ah sida lagu qeexay maqaalka Marka laga reebo in Cisco UCM waxaad u baahan tahay inaad u abuurto saddex jir CMS ah, saddex buundooyinka Shirarka, gudaha SIP Profile Security ku qeex saddex Magac Mawduuc ah, Kooxaha Jidka, Liisaska Jidadka, Kooxda Waxtarka Warbaahinta iyo Liisaska Kooxda Warbaahineed, oo ku dar dhowr xeerar marin ah. ku socota Server-ka Kulanka.
Xogta Amniga SIP:
Jirrid:
Jirrid kastaa waxay u egtahay isku mid:
Buundada Shirka
Buundada Shirku waxay u egtahay isku mid:
Kooxda Jidka
Liiska Jidadka
Kooxda Ilaha Warbaahinta
Liiska Kooxda Ilaha Warbaahinta
Xeerarka wac
Si ka duwan hababka maaraynta wicitaanka ee horumarsan sida Midaysan CM ama Waddada Wayn, CMS kaliya waxay ka eegtaa bogga SIP Request-URI ee wicitaannada cusub. Markaa haddii SIP Casuumaad loogu talagalay kabo: [emailka waa la ilaaliyay]CMS-du waxay danaysaa kaliya domain.com. CMS waxay raacdaa xeerarkan si ay u go'aamiso meesha lagala xiriiro wicitaanka:
1. CMS waxa ay marka hore isku daydaa in ay ku haboonaato xayndaabka SIP iyo xayndaabyada lagu habeeyey xeerarka wicitaanka ee soo socda. Wicitaannadan ayaa markaa loo wareejin karaa ("la beegsaday") meelo bannaan ama isticmaaleyaal gaar ah, IVR-yada gudaha, ama meelaha Microsoft Lync/Skype ee Ganacsiga (S4B) si toos ah isugu dhafan.
2. Haddii aysan jirin wax u dhigma sharciyada wicitaanka soo socda, CMS waxay isku dayi doontaa inay la mid noqoto domainka lagu habeeyay miiska gudbinta wicitaanka. Haddii kulan la sameeyo, sharcigu si cad ayuu u diidi karaa wicitaanka ama u gudbin karaa wicitaanka. Wakhtigan, CMS waxa laga yaabaa inay dib u qorto domainka, kaas oo mararka qaarkood faa'iido u leh wacitaanka xayndaabka Lync. Waxa kale oo aad dooran kartaa inaad ku gudubto tuurista, taas oo macnaheedu yahay in aan midkoodna wax laga beddeli doonin, ama isticmaal qorshe gudaha ah ee CMS. Haddii aysan jirin wax u dhigma sharciyada gudbinta wacitaanka, qaladku waa in la diido wicitaanka. Maskaxda ku hay in gudaha CMS, inkasta oo wicitaanku "soo gudbinayo", warbaahintu waxay wali ku xidhan tahay CMS, taas oo macnaheedu yahay inay ku jiri doonto calaamadaynta iyo jidka taraafikada warbaahinta.
Kadib wicitaanada la soo gudbiyo oo kaliya ayaa ku xiran sharciyada wicitaanka. Goobahani waxay go'aamiyaan meelaha wicitaanada loo diro, nooca jirridda (haddii ay tahay wicitaan cusub oo Lync ama wicitaan SIP ah), iyo beddelaad kasta oo la samayn karo haddii wareejinta aan lagu dooran sharciga gudbinta wacitaanka.
Halkan waxaa ah diiwaanka dhabta ah ee waxa dhacaya inta lagu jiro shirka Ad-Hoc
Sawirku wuxuu muujinayaa si liidata (ma garanayo sida loo wanaajiyo), markaa waxaan u qori doonaa log sidatan:
Info 127.0.0.1:35870: API user "api" created new space 7986bb6c-af4e-488d-9190-a75f16844e44 (001036270012)
Info call create failed to find coSpace -- attempting to retrieve from database
Info API "001036270012" Space GUID: 7986bb6c-af4e-488d-9190-a75f16844e44 <--> Call GUID: 93bfb890-646c-4364-8795-9587bfdc55ba <--> Call Correlator GUID: 844a3c9c-8a1e-4568-bbc3-8a0cab5aed66 <--> Internal G
Info 127.0.0.1:35872: API user "api" created new call 93bfb890-646c-4364-8795-9587bfdc55ba
Info call 7: incoming SIP call from "sip:[email protected]" to local URI "sip:[email protected]:5060" / "sip:[email protected]"
Info API call leg bc0be45e-ce8f-411c-be04-594e0220c38e in call 434f88d0-8441-41e1-b6ee-6d1c63b5b098 (API call 93bfb890-646c-4364-8795-9587bfdc55ba)
Info conference 434f88d0-8441-41e1-b6ee-6d1c63b5b098 has control/media GUID: fb587c12-23d2-4351-af61-d6365cbd648d
Info conference 434f88d0-8441-41e1-b6ee-6d1c63b5b098 named "001036270012"
Info call 7: configured - API call leg bc0be45e-ce8f-411c-be04-594e0220c38e with SIP call ID "[email protected]"
Info call 7: setting up UDT RTP session for DTLS (combined media and control)
Info conference "001036270012": unencrypted call legs now present
Info participant "[email protected]" joined space 7986bb6c-af4e-488d-9190-a75f16844e44 (001036270012)
Info participant "[email protected]" (e8371f75-fb9e-4019-91ab-77665f6d8cc3) joined conference 434f88d0-8441-41e1-b6ee-6d1c63b5b098 via SIP
Info call 8: incoming SIP call from "sip:[email protected]" to local URI "sip:[email protected]:5060" / "sip:[email protected]"
Info API call leg db61b242-1c6f-49bd-8339-091f62f5777a in call 434f88d0-8441-41e1-b6ee-6d1c63b5b098 (API call 93bfb890-646c-4364-8795-9587bfdc55ba)
Info call 8: configured - API call leg db61b242-1c6f-49bd-8339-091f62f5777a with SIP call ID "[email protected]"
Info call 8: setting up UDT RTP session for DTLS (combined media and control)
Info call 9: incoming SIP call from "sip:[email protected]" to local URI "sip:[email protected]:5060" / "sip:[email protected]"
Info API call leg 37a6e86d-d457-47cf-be24-1dbe20ccf98a in call 434f88d0-8441-41e1-b6ee-6d1c63b5b098 (API call 93bfb890-646c-4364-8795-9587bfdc55ba)
Info call 9: configured - API call leg 37a6e86d-d457-47cf-be24-1dbe20ccf98a with SIP call ID "[email protected]"
Info call 9: setting up UDT RTP session for DTLS (combined media and control)
Info call 8: compensating for far end not matching payload types
Info participant "[email protected]" joined space 7986bb6c-af4e-488d-9190-a75f16844e44 (001036270012)
Info participant "[email protected]" (289e823d-6da8-486c-a7df-fe177f05e010) joined conference 434f88d0-8441-41e1-b6ee-6d1c63b5b098 via SIP
Info call 7: compensating for far end not matching payload types
Info call 8: non matching payload types mode 1/0
Info call 8: answering offer in non matching payload types mode
Info call 8: follow-up single codec offer received
Info call 8: non matching payload types mode 1/0
Info call 8: answering offer in non matching payload types mode
Info call 8: sending response to single-codec additional offer
Info call 9: compensating for far end not matching payload types
Info participant "[email protected]" joined space 7986bb6c-af4e-488d-9190-a75f16844e44 (001036270012)
Info participant "[email protected]" (d27e9a53-2c8a-4e9c-9363-0415cd812767) joined conference 434f88d0-8441-41e1-b6ee-6d1c63b5b098 via SIP
Info call 9: BFCP (client role) now active
Info call 9: sending BFCP hello as client following receipt of hello when BFCP not active
Info call 9: BFCP (client role) now active
Info call 7: ending; remote SIP teardown - connected for 0:13
Info call 7: destroying API call leg bc0be45e-ce8f-411c-be04-594e0220c38e
Info participant "[email protected]" left space 7986bb6c-af4e-488d-9190-a75f16844e44 (001036270012)
Info call 9: on hold
Info call 9: non matching payload types mode 1/0
Info call 9: answering offer in non matching payload types mode
Info call 8: on hold
Info call 8: follow-up single codec offer received
Info call 8: non matching payload types mode 1/0
Info call 8: answering offer in non matching payload types mode
Info call 8: sending response to single-codec additional offer
Info call 9: ending; remote SIP teardown - connected for 0:12Shirka Ad-Hoc laftiisa:
Xeerarka wicitaanka ee soo gala
Habaynta cabirrada wicitaanada soo gala waa lagama maarmaan si ay awood ugu yeelato wacitaanka CMS. Sidaad ku aragtay habaynta LDAP, dhammaan isticmaalayaasha waxa lala soo dejiyay barta conf.pod6.cms.lab. Markaa ugu yaraan, waxaad doonaysaa in la soo waco boggan si loo beegsado meelaha bannaan. Waxa kale oo aad u baahan doontaa inaad dejiso shuruuc wax kasta oo loogu talagalay magaca domain oo dhammaystiran (iyo laga yaabee xitaa cinwaanka IP) mid kasta oo ka mid ah adeegayaasha CMS. Xakamaynta wicitaankayaga dibadeed, Midaysan CM, waxay habayn doontaa jirridyada SIP ee loogu talagalay mid kasta oo ka mid ah adeegayaasha CMS si gaar ah. Iyada oo ku xidhan in meesha loo socdo jirridda SIP-ga ay tahay ciwaanka IP-ga ama server-ka FQDN ayaa go'aamin doona in CMS u baahan yahay in la habeeyo si uu u aqbalo wicitaannada lagu hagayo ciwaanka IP-ga ama FQDN.
Goobta leh mudnaanta ugu sareysa ee qaanuunka soo galootiga waxaa loo istcimaalaa barta isticmaale kasta. Marka isticmaalayaashu ay isku xiraan LDAP, CMS waxay si toos ah u abuurtaa meelo bannaan, laakiin kaliya qaybta isticmaale ee URI (coSpaceUriMapping), tusaale ahaan, user.space. Qayb URI buuxa ayaa la soo saaray iyadoo lagu salaynayo sharcigan. Dhab ahaantii, haddii aad geli lahayd Buundada Shabakadda wakhtigan, waxaad arki lahayd in Space URI aanay lahayn domain. Markaad u dejiso qaanuunkan sida mudnaanta ugu sareysa, waxaad dejineysaa bogga meelaha bannaan ee la soo saaray inay noqdaan conf.tusaale.com.
Xeerarka Wicitaanka ee bixida
Si loogu oggolaado isticmaaleyaasha inay sameeyaan wicitaanno dibadda ah kooxda Midaysan ee CM, waa inaad dejisaa sharciyada dibadda. Qaybta dhammaadka dhibcaha ka diiwaan gashan Midaysan CM, sida Jabber, waa tusaale.com. Wicitaanada goobtan waa in loo rogo sida wicitaanada SIP ee caadiga ah ee noodhka habaynta CM midaysan. Adeegga ugu weyn waa cucm-01.example.com, iyo serferka dheeraadka ah waa cucm-02.example.com.
Xeerka kowaad wuxuu qeexayaa habka ugu fudud ee wicitaanada u dhexeeya server-yada kooxda.
field Maxalli ka yimid domain ayaa mas'uul ka ah waxa lagu soo bandhigi doono qofka soo wacaya SIP-URI qofka loogu yeero calaamadda "@". Haddii aan ka tagno madhan, ka dib calaamadda "@" waxaa jiri doona ciwaanka IP-ga ee CUCM kaas oo wacitaankani marayo. Haddii aan cayimno domain, ka dib calaamadda "@" waxaa jiri doona domain. Tani waa lagama maarmaan si loo awoodo in dib loo soo waco, haddii kale suurtagal ma noqon doonto in lagu soo celiyo SIP-URI name@ip-address.
Wac marka lagu tilmaamo Maxalli ka yimid domain
Wac marka MAYA tilmaamay Maxalli ka yimid domain
Hubi inaad si cad u qeexdo sir ama Aan qarsoodi ahayn wicitaanada baxaya, sababtoo ah ma jiraan wax la shaqeeya parameterka Auto.
Rikoodh
Shirarka fiidyaha waxaa duubaya serverka Diiwaanka Rikooriyuhu waxa uu la mid yahay Server Meeting Server. Diiwaaniyuhu uma baahna rakibaadda shati kasta. Shatiyada duubista ayaa looga baahan yahay adeegayaasha maamula adeegyada CallBridge, i.e. shatiga duubista ayaa loo baahan yahay waana in lagu dabaqaa qaybta CallBridge, ee maaha in server-ka ku shaqeeya Rikoodhka. Diiwaaniyuhu waxa uu u dhaqmaa sidii macmiilka fariimaha la fidi karo iyo borotokoolka joogitaanka (XMPP), markaa seerfarka XMPP waa in lagu socodsiiyaa serferka martigelinaya CallBridge.
Sababtoo ah Waxaan leenahay koox, shatigana wuxuu u baahan yahay in lagu "fidiyo" dhammaan saddexda adeeg ee kooxda. Kadibna si fudud ugu geli akoonkaaga gaarka ah shatiyada aanu ku xidhno (ku dar) ciwaanada MAC ee a-interface-yada dhammaan adeegayaasha CMS ee ku jira kooxda.
Oo kani waa sawirka waa inuu ku jiraa server kasta oo kutlada
Guud ahaan, waxaa jira dhowr xaaladood oo lagu dhejinayo Rikoorka, laakiin waxaan ku adkeysan doonnaa tan:
Kahor intaadan dejin wax duubista, waxaad u baahan tahay inaad diyaariso meel shirarka fiidiyowga si dhab ah loogu duubi doono. Dhab ahaantii halkan , sida loo sameeyo dhammaan Duubista. Waxaan diiradda saarayaa qodobbada iyo faahfaahinta muhiimka ah:
1. Way fiican tahay inaad ka siibto shahaadada server-ka ugu horreeya ee kutlada.
2. Khaladka "Diiwaangelinta lama heli karo" waxaa laga yaabaa inuu dhaco sababtoo ah shahaado khaldan ayaa lagu qeexay Truster Trust.
3. Qoritaanku ma shaqayn karo haddii tusaha NFS ee loo cayimay duubista aanu ahayn hagaha xididka.
Mararka qaarkood waxaa jirta baahi loo qabo in si toos ah loo duubo shir hal isticmaale ama meel gaar ah.
Taas awgeed, laba CallProfiles ayaa la sameeyay:
Iyadoo duubiddu ay naafo tahay
Iyo shaqada duubista tooska ah
Marka xigta, waxaanu "ku lifaaqnaa" CallProfile oo leh hawl duubitaan otomaatig ah booska la rabo.
Gudaha CMS waxaa si aad ah loo aasaasay in haddii CallProfile si cad loogu xidhay meel kasta ama meel kasta, markaa CallProfilekan wuxuu u shaqeeyaa oo keliya marka la eego meelahan gaarka ah. Oo haddii CallProfile aanu ku xidhnayn meel kasta, ka dib default waxaa lagu dabaqaa kuwa meelaha bannaan oo aan CallProfile si cad ugu xidhnayn.
Marka xigta waxaan isku dayi doonaa inaan sharaxo sida CMS looga galo meel ka baxsan shabakada gudaha ee ururka.
Ilaha:
Source: www.habr.com