A cikin wannan fitowar zan nuna da kuma bayyana wasu ƙulla-ƙulla na kafa uwar garken CMS a cikin yanayin cluster mai kasawa.
Ka'idarGabaɗaya, akwai nau'ikan tura uwar garken CMS guda uku:
- Haɗe Guda Daya(Hade guda ɗaya), watau. wannan uwar garken guda ɗaya ce wacce duk sabis ɗin da ake buƙata ke gudana akansa. A mafi yawan lokuta, wannan nau'in turawa ya dace kawai don samun damar abokin ciniki na ciki kuma a cikin ƙananan wurare inda ƙayyadaddun ƙididdiga da ƙuntatawa na uwar garken guda ɗaya ba abu ne mai mahimmanci ba, ko kuma a cikin yanayi inda CMS kawai ke yin wasu ayyuka, kamar ad hoc. taro akan Cisco UCM.
Matsakaicin tsarin aiki:
- Rarraba Single(Raba Guda ɗaya) yana ƙara nau'in turawa ta baya ta ƙara uwar garken daban don samun waje. A cikin turawa na gado, wannan yana nufin ƙaddamar da uwar garken CMS a cikin ɓangaren cibiyar sadarwar da ba ta da iyaka (DMZ) inda abokan ciniki na waje za su iya samun dama ga shi, da uwar garken CMS ɗaya a cikin cibiyar sadarwar inda abokan ciniki na ciki zasu iya samun damar CMS. Wannan samfurin turawa na musamman yanzu ana maye gurbinsa da abin da ake kira nau'in Gaba ɗaya, wanda ya ƙunshi sabobin Cisco Expressway, wanda ko dai yana da ko zai sami yawancin damar wucewar Wutar Wuta iri ɗaya don haka abokan ciniki basa buƙatar ƙara sabar CMS mai kwazo.
Matsakaicin tsarin aiki:
- Sikeli da juriya(Scalable and Fault Tolerant) Wannan nau'in ya haɗa da sakewa ga kowane bangare, ƙyale tsarin yayi girma tare da buƙatun ku zuwa iyakar ƙarfinsa yayin samar da sakewa idan an gaza. Hakanan yana amfani da ra'ayi Single Edge don samar da amintaccen shiga waje. Wannan shi ne nau'in da za mu duba a cikin wannan shirin. Idan muka fahimci yadda ake tura wannan nau'in tari, ba za mu fahimci sauran nau'ikan turawa kawai ba, amma kuma za mu iya fahimtar yadda ake ƙirƙirar gungun sabar CMS don ɗaukar yuwuwar haɓakar buƙatu.
Kafin ci gaba zuwa turawa, kuna buƙatar fahimtar wasu abubuwa na asali, wato
Babban abubuwan software na CMS:
- database: Yana ba ku damar haɗa wasu saitunan, kamar tsarin bugun kira, wuraren mai amfani, da masu amfani da kansu. Yana goyan bayan tari don samun dama mai yawa (maigida ɗaya) kawai.
- Kira gada: sabis don taron sauti da bidiyo wanda ke ba da cikakken iko akan gudanarwa da sarrafa kira da hanyoyin multimedia. Yana goyan bayan tari don samuwa mai yawa da ƙima.
- uwar garken XMPP: alhakin rajista da kuma tabbatar da abokan ciniki ta amfani da Cisco Meeting Application da/ko WebRTC(sadarwar lokaci-lokaci, ko kuma kawai a cikin burauzar yanar gizo), da kuma sigina na tsaka-tsaki. Za a iya tari don samun dama mai yawa kawai.
- Gadar Yanar Gizo: Yana ba da damar abokin ciniki zuwa WebRTC.
- Load balancer: Yana ba da wurin haɗin kai guda ɗaya don Ayyukan Taro na Cisco a cikin Yanayin Rarraba Guda. Yana sauraron abin dubawa na waje da tashar jiragen ruwa don haɗin haɗin gwiwa. Hakanan, ma'aunin nauyi yana karɓar haɗin TLS masu shigowa daga uwar garken XMPP, ta inda zai iya canza haɗin TCP daga abokan ciniki na waje.
A cikin yanayin mu ba za a buƙaci ba. - JUYA uwar garken: Yana ba da fasahar kewayawa ta Firewall da ke ba da izini
sanya CMS ɗin mu a bayan Firewall ko NAT don haɗa abokan ciniki na waje ta amfani da Cisco Meeting App ko na'urorin SIP. A cikin yanayin mu ba za a buƙaci ba. - Yanar Gizo Admin: Ƙwararren Gudanarwa da samun damar API, gami da taron CM na Haɗin Kai na musamman.
Yanayin Kanfigareshan
Ba kamar yawancin samfuran Cisco ba, Cisco Meeting Server yana goyan bayan hanyoyin daidaitawa guda uku don ɗaukar kowane nau'in turawa.
- Layin umarni (CLI): Tsarin layin umarni wanda aka sani da MMP don daidaitawar farko da ayyukan takaddun shaida.
- Mai Gudanar da Yanar Gizo: Da farko don daidaitawa masu alaƙa da CallBridge, musamman lokacin kafa sabar mara-clustered guda ɗaya.
- REST API: Ana amfani da shi don mafi rikitattun ayyuka na daidaitawa da ayyuka masu alaƙa da tarin bayanai.
Baya ga abin da ke sama, ana amfani da ka'idar SFTP don canja wurin fayiloli-yawanci lasisi, takaddun shaida, ko rajistan ayyukan-zuwa kuma daga uwar garken CMS.
A cikin jagororin turawa daga Cisco an rubuta shi da fari da Ingilishi cewa gungun yana buƙatar turawa akalla uku sabobin (nodes) a cikin mahallin bayanan bayanai. Domin Sai kawai tare da ƙarancin adadin nodes ɗin tsarin zaɓin sabon Babban Database Master zai yi aiki, kuma gabaɗaya Jagorar Database yana da alaƙa da galibin bayanan uwar garken CMS.
Kuma kamar yadda aikin ya nuna, sabobin biyu (nodes) ba su isa sosai ba. Tsarin zaɓi yana aiki lokacin da aka sake kunna Jagora, uwar garken Bawan ya zama Jagora kawai bayan an sake kunna sabar. Sai dai idan a cluster na sabobin biyu Master uwar garken ya fita kwatsam, to, uwar garken ba za ta zama Jagora ba, idan kuma Bawan ya fita, to sauran uwar garken zai zama Bawan.
Amma a cikin mahallin XMPP, da gaske ya zama dole a haɗa gungun sabar guda uku, saboda. idan, alal misali, kun kashe sabis ɗin XMPP akan ɗaya daga cikin sabar da XMMP yake a cikin Matsayin Jagora, to akan ragowar uwar garken XMPP zai kasance a cikin Matsayin Follower kuma haɗin CallBridge zuwa XMPP zai faɗi, saboda CallBridge yana haɗi na musamman zuwa XMPP tare da matsayin Jagora. Kuma wannan yana da mahimmanci, saboda ... kira daya ba zai shiga ba.
Hakanan a cikin turawa iri ɗaya ana nuna gungu mai sabar XMPP ɗaya.
Kuma la'akari da abin da ke sama, ya bayyana dalilin da ya sa: yana aiki saboda yana cikin yanayin rashin nasara.
A cikin yanayinmu, uwar garken XMPP za ta kasance a kan dukkan nodes uku.
Ana tsammanin cewa duk sabobin mu guda uku sun tashi.
Bayanan DNS
Kafin ka fara kafa sabobin, kana buƙatar ƙirƙirar bayanan DNS А и SRV iri:
Lura cewa a cikin bayananmu na DNS akwai yanki guda biyu example.com da conf.misali.com. Example.com yanki ne wanda duk masu biyan kuɗi na Cisco Unified Communication Manager zasu iya amfani da su don URIs, wanda ya fi dacewa a cikin kayan aikin ku ko kuma yana iya kasancewa. Ko example.com yayi daidai da yanki ɗaya da masu amfani ke amfani da su don adiresoshin imel ɗin su. Ko abokin ciniki na Jabber akan kwamfutar tafi-da-gidanka na iya samun URI [email kariya]. Yankin conf.example.com shine yankin da za a saita don masu amfani da Sabar Taro ta Cisco. Yankin Cisco Meeting Server zai kasance conf.example.com, don haka ga mai amfani da Jabber iri ɗaya, mai amfani @ URI zai buƙaci a yi amfani da shi don shiga Cisco Meeting Server.conf.misali.com.
Tsarin asali
Ana nuna duk saitunan da aka bayyana a ƙasa akan sabar guda ɗaya, amma suna buƙatar yin su akan kowace uwar garken a cikin tari.
QoS
Tun da CMS ke haifarwa real-lokaci zirga-zirga mai kula da jinkiri da asarar fakiti, a mafi yawan lokuta ana ba da shawarar saita ingancin sabis (QoS). Don cimma wannan, CMS tana goyan bayan fakitin yiwa alama alama tare da Lambobin Sabis daban-daban (DSCPs) da yake haifarwa. Ko da yake DSCP tushen fifikon zirga-zirgar ababen hawa ya dogara da yadda hanyoyin sadarwa ke sarrafa zirga-zirgar ababen more rayuwa na cibiyar sadarwar ku, a cikin yanayin mu za mu tsara CMS ɗin mu tare da fifikon DSCP na yau da kullun dangane da mafi kyawun ayyuka na QoS.
A kowane uwar garken za mu shigar da waɗannan umarni
dscp 4 multimedia 0x22
dscp 4 multimedia-streaming 0x22
dscp 4 voice 0x2E
dscp 4 signaling 0x1A
dscp 4 low-latency 0x1ADon haka, duk zirga-zirgar bidiyo an yiwa alama AF41 (DSCP 0x22), duk zirga-zirgar murya an yiwa alama EF (DSCP 0x2E), sauran nau'ikan ƙananan zirga-zirgar latency kamar SIP da XMPP suna amfani da AF31 (DSCP 0x1A).
Binciken:
NTP
Ka'idar Time Protocol (NTP) tana da mahimmanci ba kawai don samar da ingantattun tamburan kira da taro ba, har ma don tabbatar da takaddun shaida.
Ƙara sabar NTP zuwa kayan aikin ku tare da umarni kamar
ntp server add <server>
A cikin yanayinmu, akwai irin waɗannan sabar guda biyu, don haka za a sami ƙungiyoyi biyu.
Binciken:
Kuma saita yankin lokaci don uwar garken mu
DNS
Muna ƙara sabar DNS zuwa CMS tare da umarni kamar:
dns add forwardzone <domain-name> <server ip>
A cikin yanayinmu, akwai irin waɗannan sabar guda biyu, don haka za a sami ƙungiyoyi biyu.
Binciken:
Kanfigareshan Sadarwar Sadarwar Sadarwa
Muna saita hanyar sadarwa tare da umarni kamar:
ipv4 <interface> add <address>/<prefix length> <gateway>
Binciken:
Sunan uwar garken (sunan mai watsa shiri)
Mun saita sunan uwar garken tare da umarni kamar:
hostname <name>
Kuma mun sake yi.
Wannan yana kammala ainihin tsari.
.Ертификаты
Ka'idarCisco Meeting Server yana buƙatar rufaffiyar sadarwa tsakanin sassa daban-daban, kuma a sakamakon haka, ana buƙatar takaddun shaida X.509 don duk ayyukan CMS. Suna taimakawa tabbatar da cewa wasu sabar/sabis sun amince da sabis/uwar garken.
Kowane sabis yana buƙatar takaddun shaida, amma ƙirƙirar takaddun takaddun shaida na kowane sabis na iya haifar da rudani da rikitarwa mara amfani. Sa'ar al'amarin shine, za mu iya samar da takardar shedar maɓalli na jama'a-masu zaman kansu sannan mu sake amfani da su a cikin ayyuka da yawa. A cikin yanayinmu, za a yi amfani da wannan takardar shaidar don Call Bridge, XMPP Server, Web Bridge da Admin Web. Don haka, kuna buƙatar ƙirƙirar maɓallan takaddun shaida na jama'a da masu zaman kansu ga kowane sabar a cikin tari.
Tarin bayanai, duk da haka, yana da wasu buƙatun takaddun shaida na musamman don haka yana buƙatar takaddun shaida na kansa waɗanda suka bambanta da na sauran ayyukan. CMS yana amfani da takardar shaidar uwar garken, wanda yayi kama da takaddun shaida da wasu sabar ke amfani da su, amma kuma akwai takardar shaidar abokin ciniki da ake amfani da ita don haɗin bayanai. Ana amfani da takaddun shaida don duka tabbaci da ɓoyewa. Maimakon samar da sunan mai amfani da kalmar sirri don abokin ciniki don haɗi zuwa bayanan bayanai, yana gabatar da takardar shaidar abokin ciniki wanda uwar garken ta amince da shi. Kowace uwar garken da ke cikin gungun bayanai za ta yi amfani da maɓalli iri ɗaya na jama'a da masu zaman kansu. Wannan yana ba duk sabar da ke cikin gungu damar rufaffen bayanai ta yadda wasu sabar za su iya ɓoye su kawai waɗanda su ma ke raba maɓalli iri ɗaya.
Don sake yin aiki, rukunin bayanai dole ne su ƙunshi mafi ƙarancin sabar 3, amma ba fiye da 5 ba, tare da matsakaicin lokacin zagaye na 200 ms tsakanin kowane membobi. Wannan iyaka ya fi takura fiye da tarukan gadar Kira, don haka sau da yawa shi ne ke da iyakacin abubuwan da ake rarrabawa a yanayi.
Matsayin bayanan bayanai na CMS yana da buƙatu na musamman da dama. Ba kamar sauran ayyuka ba, yana buƙatar abokin ciniki da takardar shaidar uwar garke, inda takardar shaidar abokin ciniki tana da takamaiman filin CN wanda aka gabatar ga uwar garken.
CMS tana amfani da bayanan postgres tare da maigida ɗaya da kwafi iri ɗaya iri ɗaya. Babban tushen bayanai guda ɗaya ne kawai a lokaci guda (“uwar garken bayanai”). Ragowar mambobi na tarin su ne kwafi ko "abokan ciniki na bayanai".
Tarin bayanai yana buƙatar keɓaɓɓen takardar shaidar uwar garken da takardar shaidar abokin ciniki. Dole ne a sanya hannu ta hanyar takaddun shaida, yawanci hukumar takardar shedar sirri ta ciki. Domin duk wani memba na tarin tarin bayanai zai iya zama maigidan, uwar garken bayanai da nau'i-nau'i na satifiket ɗin abokin ciniki (wanda ke ɗauke da maɓallan jama'a da na sirri) dole ne a kwafi su zuwa duk sabar domin su ɗauki ainihin abokin ciniki ko uwar garken bayanai. Bugu da ƙari, dole ne a ɗora nauyin takardar shaidar tushen CA don tabbatar da cewa abokin ciniki da takaddun shaida na uwar garke za a iya tabbatar da su.
Don haka, mun ƙirƙiri buƙatun takardar shaidar da duk sabis ɗin uwar garken za su yi amfani da shi sai ma'aunin bayanai (za a sami buƙatu daban don wannan) tare da umarni kamar:
pki csr hostname CN:cms.example.com subjectAltName:hostname.example.com,example.com,conf.example.com,join.example.com
A cikin CN muna rubuta sunan sabobin mu. Misali, idan sunayen uwar garken mu uwar garken01, uwar garken02, uwar garken03, to CN zai kasance uwar garken.example.com
Muna yin haka akan sauran sabar guda biyu tare da bambancin cewa umarnin zai ƙunshi "sunayen mai masauki" daidai.
Muna samar da buƙatu guda biyu don takaddun shaida waɗanda sabis ɗin bayanai za su yi amfani da su tare da umarni kamar:
pki csr dbclusterserver CN:hostname1.example.com subjectAltName:hostname2.example.com,hostname3.example.com
pki csr dbclusterclient CN:postgresinda dbclusterserver и dbclusterclient sunayen buƙatun mu da takaddun shaida na gaba, sunan mai masauki1(2)(3) sunayen sabobin da suka dace.
Muna yin wannan hanya akan sabar guda ɗaya (!), kuma za mu loda takaddun shaida da fayilolin maɓalli .masu dacewa zuwa wasu sabar.
Kunna yanayin takardar shaidar abokin ciniki a AD CS
Hakanan kuna buƙatar haɗa takaddun shaida na kowane uwar garken cikin fayil ɗaya.Na *NIX:
cat server01.cer server02.cer server03.cer > server.cerA kan Windows/DOS:
copy server01.cer + server02.cer + server03.cer server.cer
Kuma loda zuwa kowane uwar garken:
1. "Mutum" uwar garken takardar shaidar.
2. Tushen takardar shaidar (tare da masu matsakaici, idan akwai).
3. Takaddun shaida don bayanan bayanai ("uwar garken" da "abokin ciniki") da fayiloli tare da tsawo na .key, waɗanda aka haifar lokacin ƙirƙirar buƙatun takaddun shaida na "uwar garken" da "abokin ciniki". Dole ne waɗannan fayilolin su zama iri ɗaya akan duk sabobin.
4. Fayil na duk takaddun shaida na "mutum" guda uku.
A sakamakon haka, ya kamata ku sami wani abu kamar wannan hoton fayil akan kowane uwar garken.
Rukunin Database
Yanzu da kuna da duk takaddun takaddun da aka ɗora zuwa sabobin CMS, zaku iya daidaitawa da ba da damar tattara bayanai tsakanin nodes uku. Mataki na farko shine zaɓin uwar garken guda ɗaya a matsayin babban kumburin tarin bayanai da kuma daidaita shi gabaɗaya.
Babban Database
Mataki na farko na kafa kwafin bayanai shine tantance takaddun takaddun da za a yi amfani da su don adana bayanai. Ana yin wannan ta amfani da umarni kamar:
database cluster certs <server_key> <server_crt> <client_key> <client_crt> <ca_crt>Yanzu bari mu gaya wa CMS wacce ke dubawa don amfani da ita don tattara bayanai tare da umarni:
database cluster localnode aSa'an nan kuma mu fara da cluster database a kan babban uwar garken tare da umurnin:
database cluster initialize
Nodes Database Abokin ciniki
Muna yin wannan hanya, kawai maimakon umarni tarin bayanai farawa shigar da umarni kamar:
database cluster join <ip address existing master>inda ip address data kasance babban adireshin ip na uwar garken CMS wanda aka fara gungu a kansa, Jagora kawai.
Muna duba yadda tarin bayanan mu ke aiki akan duk sabobin tare da umarni:
database cluster status
Haka muke yi akan sauran uwar garken na uku.
A sakamakon haka, ya zama cewa uwar garken mu na farko shine Jagora, saura kuma bayi.
Sabis Mai Gudanar da Yanar Gizo
Kunna sabis ɗin mai gudanar da gidan yanar gizo:
webadmin listen a 445An zaɓi Port 445 saboda ana amfani da tashar jiragen ruwa 443 don samun damar mai amfani ga abokin ciniki na yanar gizo
Muna saita sabis ɗin Admin Web tare da fayilolin takaddun shaida tare da umarni kamar:
webadmin certs <keyfile> <certificatefile> <ca bundle>Kuma kunna Admin Web tare da umarnin:
webadmin enable
Idan komai ya yi kyau, za mu sami layukan SUCCESS da ke nuna cewa an tsara Admin Web daidai don hanyar sadarwa da takaddun shaida. Muna duba ayyukan sabis ɗin ta amfani da mai binciken gidan yanar gizo kuma mu shigar da adireshin mai gudanar da gidan yanar gizon, misali: : 445
Kira gada Cluster
Gadar Kira ita ce kawai sabis ɗin da ke akwai a cikin kowane aikin CMS. Gadar kira ita ce babbar hanyar yin taro. Hakanan yana ba da hanyar haɗin SIP ta yadda za a iya tura kira zuwa ko daga gare ta, misali, Cisco Unified CM.
Dole ne a aiwatar da umarnin da aka bayyana a ƙasa akan kowace uwar garken tare da takaddun shaida masu dacewa.
Saboda haka:
Muna danganta takaddun shaida tare da sabis na gadar Kira tare da umarni kamar:
callbridge certs <keyfile> <certificatefile>[<cert-bundle>]Muna ɗaure sabis na CallBridge zuwa keɓantawar da muke buƙata tare da umarni:
callbridge listen aKuma zata sake farawa sabis tare da umarni:
callbridge restart
Yanzu da mun daidaita gadar kiran mu, za mu iya saita tarin gadar Kira. Tarin gadar kira ya sha bamban da tarin bayanai ko tarin XMPP. Call Bridge Cluster na iya tallafawa daga nodes 2 zuwa 8 ba tare da wani hani ba. Yana bayar da ba kawai redundancy, amma kuma load daidaitawa domin taro za a iya rayayye rarraba a fadin Call Bridge sabobin ta amfani da fasaha rarraba kira. CMS yana da ƙarin fasaloli, Ƙungiyoyin Gadar Kira da abubuwan da ke da alaƙa waɗanda za a iya amfani da su don ƙarin gudanarwa.
An saita gunkin gadar kira da farko ta hanyar haɗin yanar gizo mai gudanarwa
Dole ne a aiwatar da tsarin da aka bayyana a ƙasa akan kowace uwar garken a cikin tari.
Sabili da haka,
1. Tafi cikin yanar gizo zuwa Kanfigareshan> Tari.
2. A Kira Gaji ainihi A matsayin suna na musamman, shigar da callbridge[01,02,03] daidai da sunan uwar garken. Waɗannan sunaye na sabani ne, amma dole ne su kasance na musamman ga wannan tari. Suna da siffata a yanayi saboda suna nuna cewa su ne masu gano uwar garken [01,02,03].
3.V Gadar Kira Mai Tari shigar da URLs mai kula da gidan yanar gizo na sabar mu a cikin gungu, [01,02,03].misali.com:445, a cikin filin adireshi. Tabbatar da saka tashar jiragen ruwa. Kuna iya barin yankin SIP mahaɗin Peer fanko.
4. Ƙara takardar shaida zuwa ga CallBridge Trust na kowane uwar garken, wanda fayil ɗin ya ƙunshi duk takaddun shaida na uwar garken mu, wanda muka haɗa cikin wannan fayil tun farkon, tare da umarni kamar:
callbridge trust cluster <trusted cluster certificate bundle>Kuma zata sake farawa sabis tare da umarni:
callbridge restart
Sakamakon haka, akan kowace uwar garken yakamata ku sami wannan hoton:
Rukunin XMPP
Ana amfani da sabis na XMPP a cikin CMS don kula da duk rajista da tabbatarwa don Cisco Meeting Apps (CMA), gami da abokin ciniki na gidan yanar gizo na CMA WebRTC. Gadar Kira ita ma tana aiki azaman abokin ciniki na XMPP don dalilai na tantancewa don haka dole ne a daidaita su kamar sauran abokan ciniki. Haƙuri na kuskuren XMPP siffa ce wacce aka sami goyan baya a cikin yanayin samarwa tun sigar 2.1
Dole ne a aiwatar da umarnin da aka bayyana a ƙasa akan kowace uwar garken tare da takaddun shaida masu dacewa.
Saboda haka:
Muna haɗa takaddun shaida tare da sabis na XMPP tare da umarni kamar:
xmpp certs <keyfile> <certificatefile>[<cert-bundle>]Sannan ayyana mahallin saurare tare da umarni:
xmpp listen aSabis na XMPP yana buƙatar yanki na musamman. Wannan shine shiga ga masu amfani. A wasu kalmomi, lokacin da mai amfani yayi ƙoƙarin shiga ta amfani da app na CMA (ko ta hanyar abokin ciniki na WebRTC), suna shigar da userID@logindomain. A yanayin mu zai zama userid@conf.misali.com. Me yasa ba shine kawai misali.com ba? A cikin turawa ta musamman, mun zaɓi yankinmu na Unified CM wanda masu amfani da Jabber za su yi amfani da su a cikin Unified CM azaman misali.com, don haka muna buƙatar wani yanki na daban don masu amfani da CMS don tura kira zuwa kuma daga CMS ta wuraren SIP.
Saita yankin XMPP ta amfani da umarni kamar:
xmpp domain <domain>Kuma kunna sabis na XMPP tare da umarnin:
xmpp enableA cikin sabis na XMPP, dole ne ka ƙirƙiri takaddun shaida ga kowane Gadar Kira da za a yi amfani da ita lokacin yin rijista tare da sabis na XMPP. Waɗannan sunaye ne na sabani (kuma ba su da alaƙa da keɓaɓɓen sunaye da kuka tsara don tarin gadar kira). Dole ne ku ƙara gadoji kira guda uku akan uwar garken XMPP ɗaya sannan ku shigar da waɗannan takaddun shaida akan wasu sabar XMPP a cikin gungu saboda wannan tsarin bai dace da ma'aunin bayanai ba. Daga baya za mu saita kowace Gadar Kira don amfani da wannan suna da sirri don yin rajista tare da sabis na XMPP.
Yanzu muna buƙatar saita sabis na XMPP akan sabar farko tare da Kira Bridges Callbridge01, callbridge02 da callbridge03. Kowane asusu za a sanya kalmomin shiga bazuwar. Daga baya za a shigar da su a kan wasu sabar gadar Kira don shiga cikin wannan uwar garken XMPP. Shigar da umarni masu zuwa:
xmpp callbridge add callbridge01
xmpp callbridge add callbridge02
xmpp callbridge add callbridge03Sakamakon haka, muna duba abin da ya faru da umarnin:
xmpp callbridge list
Daidai wannan hoton ya kamata ya bayyana akan ragowar sabobin bayan matakan da aka bayyana a ƙasa.
Na gaba, muna ƙara daidai saituna iri ɗaya akan ragowar sabobin biyu, kawai tare da umarni
xmpp callbridge add-secret callbridge01
xmpp callbridge add-secret callbridge02
xmpp callbridge add-secret callbridge03Muna ƙara Sirrin a hankali ta yadda, alal misali, babu ƙarin sarari a ciki.
Sakamakon haka, kowane uwar garken ya kamata ya kasance yana da hoto iri ɗaya:
Na gaba, akan duk sabar da ke cikin tarin, mun ƙididdige amincin fayil ɗin da ke ɗauke da duk takaddun shaida guda uku, waɗanda aka ƙirƙira a baya tare da umarni kamar haka:
xmpp cluster trust <trust bundle>Muna kunna yanayin gungu na xmpp akan duk sabar tari tare da umarni:
xmpp cluster enableA kan uwar garken farko na gungu, mun fara ƙirƙirar gungu na xmpp tare da umarni:
xmpp cluster initializeA kan wasu sabobin, ƙara gungu zuwa xmpp tare da umarni kamar:
xmpp cluster join <ip address head xmpp server>Muna duba kowane sabar nasarar ƙirƙirar gungu na XMPP akan kowace uwar garken tare da umarni:
xmpp status
xmpp cluster statusSabar ta farko:
Sabar ta biyu:
Sabar ta uku:
Haɗa Gadar Kira zuwa XMPP
Yanzu da gungu na XMPP yana gudana, kuna buƙatar saita sabis na gadar Kira don haɗawa zuwa gungu na XMPP. Ana yin wannan tsari ta hanyar mai sarrafa gidan yanar gizo.
A kowane uwar garken, je zuwa Kanfigareshan> Gaba ɗaya kuma a cikin filin Sunan Gadar Kira na Musamman rubuta musamman sunaye daidai da gadar Kira ta uwar garken gada[01,02,03]. Л л domain conf.misali.ru da kalmomin sirri masu dacewa, zaku iya leken asiri akan su
akan kowace uwar garken da ke cikin gungu tare da umarni:
xmpp callbridge list
Bar filin “Server” fanko Callbridge zai yi bincike na SRV na DNS _xmpp-bangaren._tcp.conf.example.comdon nemo sabar XMPP da ke akwai. Adireshin IP don haɗa layin kira zuwa XMPP na iya bambanta akan kowane uwar garken, ya dogara da abin da aka mayar da ƙimar zuwa buƙatun rikodin. _xmpp-bangaren._tcp.conf.example.com callbridge, wanda kuma ya dogara da saitunan fifiko don rikodin DNS da aka ba.
Na gaba, je zuwa Matsayi> Gabaɗaya don tabbatar ko an sami nasarar haɗa sabis ɗin Bride na Kira zuwa sabis na XMPP.
Gadar Yanar Gizo
A kan kowane uwar garken da ke cikin gungu, kunna sabis na gadar Yanar Gizo tare da umarni:
webbridge listen a:443Muna saita sabis ɗin gadar Yanar gizo tare da fayilolin takaddun shaida tare da umarni kamar:
webbridge certs <keyfile> <certificatefile> <ca bundle>Gadar Yanar Gizo tana goyan bayan HTTPS. Zai tura HTTP zuwa HTTPS idan an saita shi don amfani da "http-redirect".
Don kunna juyawa HTTP, yi amfani da umarni mai zuwa:
webbridge http-redirect enableDon sanar da Gadar Kira ta san cewa gadar Yanar Gizo na iya amincewa da haɗin kai daga Gadar Kira, yi amfani da umarnin:
webbridge trust <certfile>inda wannan fayil ne mai ɗauke da duk takaddun shaida guda uku daga kowace uwar garken a cikin gungu.
Wannan hoton ya kamata ya kasance akan kowane uwar garken da ke cikin gungu.
Yanzu muna buƙatar ƙirƙirar mai amfani tare da rawar "appadmin", muna buƙatar shi don mu iya saita gungu (!), Kuma ba kowane sabar a cikin gungu daban ba, ta wannan hanyar za a yi amfani da saitunan daidai ga kowane uwar garken duk da gaskiyar cewa za a yi su sau ɗaya.
Don ƙarin saitin za mu yi amfani da shi .
Don izini, zaɓi Na asali a cikin sashin izini
Don aika umarni daidai zuwa uwar garken CMS, kuna buƙatar saita rikodin da ake buƙata
Mun saka Webbridge tare da umarni POST tare da siga url da ma'ana
A cikin gadar yanar gizon kanta, muna nuna sigogin da ake buƙata: damar baƙo, samun kariya, da sauransu.
Kira Ƙungiyoyin Gada
Ta hanyar tsoho, CMS ba koyaushe yana yin ingantaccen amfani da albarkatun taron da ake da su ba.
Misali, don taro tare da mahalarta uku, kowane ɗan takara na iya ƙarewa akan gadar Kira daban-daban guda uku. Domin waɗannan mahalarta uku su yi hulɗa da juna, Call Bridges za su kafa haɗin kai ta atomatik tsakanin duk sabar da abokan ciniki a cikin sarari guda, ta yadda duk ya zama kamar duk abokan ciniki suna kan sabar iri ɗaya. Abin baƙin ciki shine, ƙasan wannan shine taron mutum 3 guda ɗaya yanzu zai cinye tashoshin watsa labarai na 9. Wannan tabbas rashin ingantaccen amfani da albarkatun ne. Bugu da ƙari, lokacin da gadar Kira ta yi lodi da gaske, tsarin da aka saba shine a ci gaba da karɓar kira da samar da ingantaccen sabis ga duk masu biyan kuɗi na waccan gadar Kira.
Ana magance waɗannan matsalolin ta amfani da fasalin Ƙungiyar Ƙarfafa Kira. An gabatar da wannan fasalin a cikin sigar 2.1 na software na Cisco Meeting Server kuma an tsawaita don tallafawa daidaita nauyin duka biyun mai shigowa da waje da kiran Cisco Meeting App (CMA), gami da mahalarta WebRTC.
Don warware matsalar sake haɗawa, an gabatar da iyakoki masu daidaitawa guda uku don kowane Gadar Kira:
Ƙimar Load - wannan shine matsakaicin nauyin lambobi don takamaiman gadar Kira. Kowane dandali yana da ƙayyadaddun ƙayyadaddun kaya, kamar 96000 don CMS1000 da 1.25 GHz kowane vCPU don injin kama-da-wane. Kira daban-daban suna cinye takamaiman adadin albarkatu dangane da ƙuduri da ƙimar ɗan takara.
NewConferenceLoadLimitBasisPoints (tsohuwar 50% loadLimit) - saita iyakar nauyin uwar garken, bayan haka an ƙi sabon taro.
Ƙaddamar da Taro na ZamaniLoadLimitBasisPoints (Tsoffin 80% na LoadLimit) - ƙimar lodin uwar garken bayan haka za a ƙi masu shiga taron da ake da su.
Yayin da aka ƙera wannan fasalin don rarraba kira da daidaita kaya, sauran ƙungiyoyi irin su TURN Servers, Web Bridge Servers da Recorders kuma ana iya sanya su zuwa Ƙungiyoyin Gadar Kira ta yadda za a iya haɗa su da kyau don amfani mai kyau. Idan ɗayan waɗannan abubuwan ba a sanya su zuwa ƙungiyar kira ba, ana ɗaukan suna samuwa ga duk sabar ba tare da wani fifiko na musamman ba.
An saita waɗannan sigogi anan: :445/api/v1/system/configuration/cluster
Bayan haka, muna nuna wa kowane gadar kiran waya wacce rukunin kiran gadar ta ke:
Na farko callbridge
Gada ta biyu
Gada ta uku
Don haka, mun saita ƙungiyar Kira Brdige don yin amfani da albarkatu na gungu na Sabar Meeting Server.
Ana shigo da masu amfani daga Active Directory
Sabis na Admin na Yanar Gizo yana da sashin daidaitawa na LDAP, amma baya samar da zaɓuɓɓuka masu rikitarwa, kuma ba a adana bayanan a cikin ma'ajin bayanai na cluster, don haka sai a yi sanyi, ko dai da hannu akan kowace sabar ta hanyar Intanet, ko ta hanyar Intanet. API ɗin, kuma domin mu "sau uku"Kada ku tashi" har yanzu za mu saita bayanan ta API.
Amfani da URL don samun dama :445/api/v1/ldapServers suna ƙirƙirar abu na LDAP Server, suna ƙayyadaddun sigogi kamar:
- Sabar IP
- lambar tashar jiragen ruwa
- Sunan mai amfani
- kalmar sirri
- m
Amintacce - zaɓi gaskiya ko ƙarya dangane da tashar jiragen ruwa, 389 - ba amintacce ba, 636 - kariya.
Taswirar tushen LDAP zuwa sifofi a cikin Sabar Taro ta Cisco.
Taswirar LDAP taswirar halaye a cikin kundin adireshin LDAP zuwa halayen da ke cikin CMS. Haƙiƙanin halayen:
- jiMapping
- Taswirar suna
- CoSpaceNameMapping
- coSpaceUriMapping
- coSpaceSecondaryUriMapping
Bayanin halayeJID yana wakiltar ID ɗin shiga mai amfani a cikin CMS. Tun da wannan sabar LDAP ce ta Microsoft Active Directory, taswirar CMS JID zuwa sunan sunan sAMAccount a cikin LDAP, wanda shine ainihin ID ɗin shiga Active Directory na mai amfani. Hakanan lura cewa kun ɗauki sAMAccountName kuma ƙara yankin conf.pod6.cms.lab zuwa ƙarshensa saboda wannan shine shiga masu amfani da ku don shiga cikin CMS.
Taswirar suna yayi daidai da abin da ke cikin filin nunin Active Directory Suna zuwa filin sunan CMS na mai amfani.
CoSpaceNameMapping yana ƙirƙirar sunan sarari na CMS bisa filin nunin Suna. Wannan sifa, tare da sifa ta coSpaceUriMapping, shine abin da ake buƙata don ƙirƙirar sarari ga kowane mai amfani.
coSpaceUriMapping yana bayyana ɓangaren mai amfani na URI mai alaƙa da keɓaɓɓen sarari na mai amfani. Ana iya saita wasu yankuna don a buga su cikin sarari. Idan ɓangaren mai amfani ya dace da wannan filin don ɗayan waɗannan wuraren, za a tura kiran zuwa sararin samaniyar mai amfani.
coSpaceSecondaryUriMapping yana bayyana URI na biyu don isa sararin samaniya. Ana iya amfani da wannan don ƙara laƙabi na lamba don tura kira zuwa sararin mai amfani da aka shigo da shi azaman madadin URI haruffan da aka ayyana a cikin ma'aunin coSpaceUriMapping.
An saita uwar garken LDAP da taswirar LDAP. Yanzu kuna buƙatar haɗa su tare ta ƙirƙirar tushen LDAP.
Amfani da URL don samun dama :445/api/v1/ldapSource ƙirƙira wani abu Source LDAP, ƙayyadaddun sigogi kamar:
- uwar garken
- Taswirar
- tusheDn
- tace
Yanzu da saitin LDAP ya cika, zaku iya aiwatar da aikin aiki tare.
Muna yin wannan ko dai a cikin Intanet na kowace uwar garken ta dannawa Aiki tare yanzu sashe Active Directory
ko ta hanyar API tare da umarnin POST amfani da URL don samun dama :445/api/v1/ldapSyncs
Taro na Ad-Hoc
Menene wannan?A cikin al'adar al'ada, taro shine lokacin da mahalarta biyu ke magana da juna, kuma ɗaya daga cikin mahalarta (ta amfani da na'urar da aka yi rajista da Unified CM) ya danna maɓallin "Conference", ya kira wani, bayan ya yi magana da wannan ɓangare na uku. , sake danna maɓallin "Conference" don haɗawa da duk mahalarta taron uku.
Abin da ke bambanta taron Ad-Hoc daga taron da aka tsara a cikin CMS shine cewa taron Ad-Hoc ba kawai kiran SIP ba ne ga CMS. Lokacin da mai ƙaddamar da taron ya danna maɓallin Taro a karo na biyu don gayyatar kowa da kowa zuwa taro iri ɗaya, Unified CM dole ne ya yi kiran API zuwa CMS don ƙirƙirar taron kan-tashi wanda sannan ana canja wurin duk kira. Duk wannan yana faruwa ba tare da mahalarta sun lura ba.
Wannan yana nufin cewa Unified CM dole ne ya saita bayanan shaidar API da adireshin WebAdmin/tashar sabis da kuma SIP Trunk kai tsaye zuwa uwar garken CMS don ci gaba da kira.
Idan ya cancanta, CUCM na iya ƙirƙira sarari a hankali a cikin CMS ta yadda kowane kira zai iya isa CMS kuma ya dace da ka'idar kira mai shigowa wanda aka yi niyya don sarari.
Haɗin kai tare da CUCM an daidaita su kamar yadda aka bayyana a cikin labarin sai dai a kan Cisco UCM kuna buƙatar ƙirƙirar kututtuka guda uku don CMS, gadajen taro guda uku, a cikin Bayanan Tsaro na SIP Ƙayyade Sunayen Jigo guda uku, Ƙungiyoyin Hanya, Lissafin Hanyoyi, Rukunin Resourse na Media da Lissafin Rukunin Resourse na Media, kuma ƙara ƴan ƙa'idodin kewayawa. zuwa Cisco Meeting Server.
Bayanan Tsaro na SIP:
Ganyayyaki:
Kowane akwati yayi kama da haka:
Gadar Taro
Kowane gadar taro yayi kama da haka:
Rukunin Hanya
Jerin hanyoyin hanya
Rukunin Albarkatun Watsa Labarai
Jerin Rukunin Albarkatun Watsa Labarai
Dokokin Kira
Ba kamar ƙarin tsarin sarrafa kira na ci-gaba kamar Unified CM ko Expressway, CMS kawai yana duba yankin a cikin filin SIP Request-URI don sababbin kira. Don haka idan SIP INVITE don sip ne: [email kariya]CMS kawai yana kula da domain.com. CMS yana bin waɗannan ƙa'idodi don ƙayyade inda za'a tura kira:
1. CMS ya fara ƙoƙarin daidaita yankin SIP tare da wuraren da aka saita a cikin ƙa'idodin kira mai shigowa. Ana iya tura waɗannan kira zuwa wurare ("masu niyya") ko takamaiman masu amfani, IVRs na ciki, ko haɗa kai tsaye wuraren Microsoft Lync/Skype don Kasuwanci (S4B).
2. Idan babu wasa a cikin dokokin kira mai shigowa, CMS za ta yi ƙoƙarin daidaita yankin da aka saita a cikin tebur isar da kira. Idan an yi wasa, doka na iya ƙin karɓar kira a sarari ko tura kiran. A wannan lokacin, CMS na iya sake rubuta yankin, wanda wani lokaci yana da amfani don kiran yankin Lync. Hakanan zaka iya zaɓar wuce jifa, wanda ke nufin babu ɗayan filayen da za a ƙara inganta, ko amfani da shirin bugun kiran CMS na ciki. Idan babu wasa a cikin dokokin isar da kira, tsoho shine ƙin karɓar kiran. Ka tuna cewa a cikin CMS, kodayake kiran yana "gabatar da", har yanzu kafofin watsa labaru suna daure zuwa CMS, wanda ke nufin zai kasance a cikin sigina da hanyoyin zirga-zirga.
Sannan kiran da aka tura kawai yana ƙarƙashin ka'idojin kira masu fita. Waɗannan saitunan suna ƙayyade wuraren da ake aika kira, nau'in akwati (ko sabon kiran Lync ne ko daidaitaccen kiran SIP), da duk wani juyi da za a iya yi idan ba a zaɓi canja wuri ba a cikin ƙa'idar tura kira.
Anan ga ainihin tarihin abin da ke faruwa yayin taron Ad-Hoc
Hoton hoton yana nuna shi da kyau (Ban san yadda zan inganta shi ba), don haka zan rubuta log ɗin kamar haka:
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:12Taron Ad-Hoc da kansa:
Dokokin kira mai shigowa
Saita sigogin kira mai shigowa ya zama dole don samun damar karɓar kira a cikin CMS. Kamar yadda kuka gani a cikin saitin LDAP, duk masu amfani an shigo da su tare da yankin conf.pod6.cms.lab. Don haka aƙalla, kuna son kira zuwa wannan yanki don niyya wurare. Hakanan kuna buƙatar saita dokoki don duk abin da aka yi niyya don cikakken sunan yankin da ya cancanta (har ma da adireshin IP) na kowane sabar CMS. Ikon kiran mu na waje, Unified CM, zai saita kututturan SIP da aka keɓe ga kowane sabar CMS daban-daban. Dangane da ko inda waɗannan kututturen SIP ɗin ke zuwa adireshin IP ne ko kuma FQDN na uwar garken zai ƙayyade ko CMS yana buƙatar daidaitawa don karɓar kira zuwa adireshin IP ko FQDN.
Yankin da ke da mafi girman fifikon dokar shiga ana amfani da shi azaman yanki don kowane sarari mai amfani. Lokacin da masu amfani suka yi aiki tare ta hanyar LDAP, CMS yana ƙirƙirar sarari ta atomatik, amma ɓangaren mai amfani kawai na URI (coSpaceUriMapping), misali, user.space. Sashe An samar da cikakken URI bisa wannan ka'ida. A zahiri, idan za ku shiga Gadar Yanar Gizo a wannan lokacin, zaku ga cewa Space URI ba shi da yanki. Ta hanyar saita wannan doka a matsayin fifiko mafi girma, kuna saita yankin don wuraren da aka samar su kasance conf.misali.com.
Dokokin Kira masu fita
Don bawa masu amfani damar yin kira na waje zuwa gungu na CM Unified, dole ne ku saita dokokin fita. Yankin wuraren ƙarshen rajista tare da Unified CM, kamar Jabber, shine example.com. Ya kamata a tunkuɗe kiran zuwa wannan yanki azaman daidaitaccen kiran SIP zuwa nodes ɗin sarrafa kiran Haɗin kai na CM. Babban uwar garken shine cucm-01.example.com, kuma ƙarin uwar garken shine cucm-02.example.com.
Doka ta farko ta bayyana mafi sauƙi ta hanyar kira tsakanin sabar tari.
filin Na gida daga yanki yana da alhakin abin da za a nuna a cikin SIP-URI mai kira ga wanda ake kira bayan alamar "@". Idan muka bar shi fanko, to bayan alamar "@" za a sami adireshin IP na CUCM wanda wannan kiran ke wucewa. Idan muka ƙayyade yanki, to bayan alamar "@" za a sami yanki a zahiri. Wannan yana da mahimmanci don samun damar sake kira, in ba haka ba ba zai yiwu a sake kira ta hanyar SIP-URI name@ip-address ba.
Kira lokacin da aka nuna Na gida daga yanki
Kira lokacin NOT aka nuna Na gida daga yanki
Tabbata a saka boye-boye ko Ba a rurrufe ba don kiran masu fita, saboda babu abin da ke aiki tare da sigar atomatik.
Recording
Ana yin rikodin taron bidiyo ta uwar garken Rikodi. Mai rikodin daidai yake da Sabar Taro ta Cisco. Mai rikodi baya buƙatar shigar da kowane lasisi. Ana buƙatar lasisin yin rikodi don sabobin da ke gudanar da ayyukan CallBridge, watau. Ana buƙatar lasisin yin rikodi kuma dole ne a yi amfani da shi zuwa ɓangaren CallBridge, ba ga uwar garken da ke aiki da Rikodi ba. Mai rikodi yana aiki azaman Abokin Hulɗar Saƙo da Kariya (XMPP), don haka dole ne a kunna uwar garken XMPP akan uwar garken mai karɓar CallBridge.
Domin Muna da gungu kuma lasisi yana buƙatar “miƙewa” a duk sabar guda uku a cikin tarin. Sannan kawai a cikin keɓaɓɓen asusun ku a cikin lasisin da muke haɗawa (ƙara) adiresoshin MAC na duk sabar CMS da aka haɗa a cikin tari.
Kuma wannan shine hoton da yakamata ya kasance akan kowane uwar garken da ke cikin gungu
Gabaɗaya, akwai yanayi da yawa don sanya Rikodi, amma za mu tsaya ga wannan:
Kafin kafa Rikodi, kuna buƙatar shirya wurin da za a yi rikodin taron bidiyo a zahiri. A gaskiya a nan , yadda ake saita duk Rikodi. Ina mai da hankali kan mahimman bayanai da bayanai:
1. Zai fi kyau a zame takardar shaidar daga uwar garken farko a cikin tari.
2. Kuskuren "Ba a samun rikodin rikodi" na iya faruwa saboda an ƙayyade takardar shaidar da ba daidai ba a cikin Rikodi Trust.
3. Rubutun bazai yi aiki ba idan NFS directory da aka ƙayyade don yin rikodi ba shine tushen tushen ba.
Wani lokaci ana buƙatar yin rikodin taro ta atomatik na takamaiman mai amfani ko sarari.
Don wannan, an ƙirƙira Bayanan Bayanan Kira guda biyu:
Tare da kashe rikodi
Kuma tare da aikin rikodi ta atomatik
Bayan haka, muna “haɗa” Profile ɗin Kira tare da aikin rikodi ta atomatik zuwa wurin da ake buƙata.
A cikin CMS an tabbatar da cewa idan an ɗaure CallProfile a sarari ga kowane sarari ko sarari, to wannan CallProfile yana aiki ne kawai dangane da waɗannan takamaiman wuraren. Kuma idan CallProfile ba a ɗaure shi da kowane sarari ba, to ta hanyar tsohuwa ana amfani da shi ga waɗancan wuraren da babu CallProfile ɗin da aka ɗaure su.
Lokaci na gaba zan yi ƙoƙarin bayyana yadda ake samun damar CMS a wajen cibiyar sadarwar cikin gida ta ƙungiyar.
Sources:
source: www.habr.com