Iseva Yomhlangano weCisco 2.5.2. Iqoqo elikumodi e-Scalable ne-Resilient enomsebenzi wokurekhoda wenkomfa yevidiyo

Kulolu shicilelo ngizobonisa futhi ngichaze ezinye zezinto eziyinkimbinkimbi zokusetha iseva ye-CMS kumodi yeqoqo le-faillover.


UmbonoNgokuvamile, kunezinhlobo ezintathu zokuthunyelwa kweseva ye-CMS:

• Okukodwa Kuhlanganisiwe(Ihlangene eyodwa), i.e. lena iseva eyodwa lapho zonke izinkonzo ezidingekayo zisebenza khona. Ezimweni eziningi, lolu hlobo lokuphakelwa lufaneleka kuphela ukufinyelela kwekhasimende langaphakathi nasezindaweni ezincane lapho ukulinganiselwa nokuphinda kuncishiswe kabusha kweseva eyodwa kungeyona indaba ebucayi, noma ezimeni lapho i-CMS yenza khona imisebenzi ethile kuphela, njenge-ad hoc. izinkomfa on Cisco UCM.

  Isikimu esilinganiselwe somsebenzi:
  

• I-Single Split(I-Single Split) inweba uhlobo lwangaphambilini lokuphakelwa ngokungeza iseva ehlukile yokufinyelela kwangaphandle. Ekuphakeleni kwefa, lokhu kwakusho ukuthunyelwa kweseva ye-CMS engxenyeni yenethiwekhi engahlotshaniswa namasosha (DMZ) lapho amaklayenti angaphandle akwazi ukuyifinyelela, kanye neseva ye-CMS eyodwa kungqikithi yenethiwekhi lapho amaklayenti angaphakathi akwazi ukufinyelela i-CMS. Le modeli ethile yokusatshalaliswa manje isithathelwa indawo yilolu okuthiwa uhlobo I-Single Edge, ehlanganisa amaseva I-Cisco Expressway, okungenzeka ukuthi inamakhono amaningi okudlula noma azoba namandla afanayo wokudlula i-Firewall ukuze amaklayenti angadingi ukungeza iseva enqenqemeni ye-CMS.

  Isikimu esilinganiselwe somsebenzi:
  

• I-Scalable futhi Iqinile(I-Scalable and Fault Tolerant) Lolu hlobo luhlanganisa ukuphinda kusetshenziswe ingxenye ngayinye, okuvumela isistimu ukuthi ikhule nezidingo zakho kuze kufike kumthamo wayo omkhulu kuyilapho ihlinzeka ngokuphinda isebenze uma kwenzeka yehluleka. Iphinde isebenzisa umqondo we-Single Edge ukunikeza ukufinyelela kwangaphandle okuphephile. Lolu wuhlobo esizolubheka kulesi siqephu. Uma siqonda ukuthi singalusebenzisa kanjani lolu hlobo lweqoqo, ngeke siqonde kuphela ezinye izinhlobo zokusatshalaliswa, kodwa sizokwazi nokuqonda ukuthi singawakha kanjani amaqoqo amaseva e-CMS ukuze kuhlangatshezwane nokukhula okungenzeka kwesidingo.

Ngaphambi kokudlulela ekusetshenzisweni, udinga ukuqonda izinto ezithile eziyisisekelo, okungukuthi

Izingxenye zesofthiwe ye-CMS eziyinhloko:

• Database: Ikuvumela ukuthi uhlanganise okunye ukucupha, okufana nohlelo lokudayela, izikhala zabasebenzisi, kanye nabasebenzisi ngokwabo. Isekela ukuhlanganisa ukutholakala okuphezulu (okuyinhloko eyodwa) kuphela.
• Shayela ibhuloho: isevisi yenkomfa yomsindo nevidiyo ehlinzeka ngokulawula okugcwele phezu kokuphathwa nokucutshungulwa kwezingcingo nezinqubo zemultimedia. Isekela ukuhlanganisa ukutholakala okuphezulu nokulinganisa.
• Iseva ye-XMPP: unesibopho sokubhalisa kanye nokuqinisekiswa kwamakhasimende esebenzisa i-Cisco Meeting Application kanye/noma i-WebRTC(ukuxhumana kwesikhathi sangempela, noma kusiphequluli nje), kanye nokusayina kwezakhi. Ingahlanganiswa ngokutholakala okuphezulu kuphela.
• Ibhuloho lewebhu: Inikeza ukufinyelela kweklayenti ku-WebRTC.
• Isilayishi: Ihlinzeka ngendawo eyodwa yokuxhumana ye-Cisco Meeting Apps ngemodi yokuhlukaniswa okukodwa. Ilalela isixhumi esibonakalayo sangaphandle kanye nembobo yokuxhumana okungenayo. Ngokulinganayo, isilinganisi somthwalo samukela uxhumo lwe-TLS olungenayo olusuka kuseva ye-XMPP, lapho lungashintsha khona ukuxhumana kwe-TCP kumakhasimende angaphandle.
  Esimeni sethu ngeke kudingeke.
• JINZA iseva: Ihlinzeka ngobuchwepheshe be-Firewall bypass obuvumela
  beka i-CMS yethu ngemuva kwe-Firewall noma i-NAT ukuze uxhume amaklayenti angaphandle usebenzisa i-Cisco Meeting App noma amadivayisi we-SIP. Esimeni sethu ngeke kudingeke.
• Umphathi Wewebhu: Isixhumi esibonakalayo sokuphatha nokufinyelela kwe-API, okuhlanganisa nezingqungquthela ezikhethekile ze-Unified CM.

Izindlela zokumisa

Ngokungafani neminye imikhiqizo eminingi ye-Cisco, i-Cisco Meeting Server isekela izindlela ezintathu zokumisa ukuze kuhlangatshezwane nanoma yiluphi uhlobo lokuthunyelwa.

• Umugqa womyalo (CLI): Ukuxhumana komugqa womyalo okwaziwa nge-MMP kokucushwa kokuqala kanye nemisebenzi yesitifiketi.
• Umphathi Wewebhu: Ikakhulukazi ngokulungiselelwa okuhlobene ne-CallBridge, ikakhulukazi uma usetha iseva eyodwa engahlanganisiwe.
• I-REST API: Isetshenziselwa imisebenzi yokumisa eyinkimbinkimbi kakhulu kanye nemisebenzi ehlobene nesizindalwazi esihlanganisiwe.

Ngaphezu kwalokhu okungenhla, iphrothokholi isetshenziswa SFTP ukudlulisa amafayela—ngokuvamile amalayisense, izitifiketi, noma amalogi—kuya noma kusuka kuseva ye-CMS.

Kumihlahlandlela yokuthunyelwa evela eCisco kubhalwe ngomhlophe nangesiNgisi ukuthi iqoqo lidinga ukuthunyelwa okungenani ezintathu amaseva (ama-node) kumongo wolwazi. Ngoba Kuphela ngenani eliyinqaba lama-node lapho indlela yokukhetha i-Database Master entsha izosebenza, futhi ngokuvamile i-Database Master inokuxhumana nedathabheyisi yeseva ye-CMS eminingi.

Futhi njengoba umkhuba ubonisa, amaseva amabili (ama-node) awanele ngempela. Indlela yokukhetha isebenza lapho i-Master iqalwa kabusha, iseva ye-Slave iba Inkosi kuphela ngemva kokuba iseva eqaliswe kabusha ilethwa. Kodwa-ke, uma eqoqweni lamaseva amabili iseva Eyinhloko iphuma ngokuzumayo, khona-ke iseva yeSigqila ngeke ibe Inkosi, futhi uma iSigqila siphuma, iseva Eyinhloko esele izoba Isigqila.

Kepha kumongo we-XMPP, kungadingeka ngempela ukuhlanganisa iqoqo lamaseva amathathu, ngoba uma, ngokwesibonelo, ukhubaza isevisi ye-XMPP kwenye yeziphakeli lapho i-XMMP isesimweni soMholi, kuseva esele i-XMPP izohlala ikusimo Somlandeli futhi uxhumo lwe-CallBridge ku-XMPP luzowa, ngoba I-CallBridge ixhumeka ngokukhethekile ku-XMPP enesimo soMholi. Futhi lokhu kubalulekile, ngoba ... alukho ucingo olulodwa oluzongena.

Futhi kuzinkombandlela ezifanayo zokuthunyelwa kuboniswa iqoqo elineseva eyodwa ye-XMPP.

Futhi ngokucabangela okungenhla, kuyacaca ukuthi kungani: isebenza ngoba ikwimodi ye-faillover.

Esimweni sethu, iseva ye-XMPP izoba khona kuwo womathathu ama-node.

Kucatshangwa ukuthi womathathu amaseva ethu aphakanyisiwe.

Amarekhodi e-DNS

Ngaphambi kokuthi uqale ukusetha amaseva, udinga ukudala amarekhodi e-DNS А и I-SRV izinhlobo:

Sicela uqaphele ukuthi kumarekhodi ethu e-DNS kunezizinda ezimbili ze-example.com kanye conf.example.com. I-Model.com isizinda bonke ababhalisi be-Cisco Unified Communication Manager abangasisebenzisa kuma-URI abo, okungenzeka akhona kungqalasizinda yakho noma okungenzeka abe khona. Noma i-example.com ifana nesizinda esifanayo esisetshenziswa abasebenzisi kumakheli abo e-imeyili. Noma iklayenti le-Jabber kukhompyutha yakho ephathekayo lingase libe ne-URI [i-imeyili ivikelwe]. Isizinda confI-.example.com isizinda esizolungiselelwa abasebenzisi Beseva Yomhlangano we-Cisco. Isizinda se-Cisco Meeting Server sizoba conf.example.com, ngakho kumsebenzisi ofanayo we-Jabber, umsebenzisi@ URI kuzodingeka asetshenziselwe ukungena Kuseva Yomhlangano ye-Ciscoconf.example.com.

Ukucushwa okuyisisekelo

Zonke izilungiselelo ezichazwe ngezansi ziboniswa kuseva eyodwa, kodwa zidinga ukwenziwa kuseva ngayinye kuqoqo.

QoS

Njengoba i-CMS ikhiqiza isikhathi sangempela ithrafikhi izwela ukubambezeleka nokulahlekelwa kwephakethe, ezimweni eziningi kuyanconywa ukuthi ulungiselele ikhwalithi yesevisi (QoS). Ukuze kuzuzwe lokhu, i-CMS isekela ukumaka amaphakethe Ngamakhodi Amasevisi Ahlukene (DSCPs) ewakhiqizayo. Nakuba ukubeka kuqala kwethrafikhi okusekelwe ku-DSCP kuncike ekutheni ithrafikhi icutshungulwa kanjani izingxenye zenethiwekhi zengqalasizinda yakho, esimweni sethu sizolungisa i-CMS yethu ngokubeka phambili okujwayelekile kwe-DSCP okusekelwe kuzinqubo ezihamba phambili ze-QoS.

Kuseva ngayinye sizofaka le miyalo

dscp 4 multimedia 0x22
dscp 4 multimedia-streaming 0x22
dscp 4 voice 0x2E
dscp 4 signaling 0x1A
dscp 4 low-latency 0x1A

Ngakho, yonke ithrafikhi yevidiyo yayimakwe ngokuthi AF41 (DSCP 0x22), yonke ithrafikhi yezwi yaphawulwa ngokuthi EF (DSCP 0x2E), ezinye izinhlobo zethrafikhi ephansi yokubambezeleka njenge-SIP ne-XMPP zisebenzisa i-AF31 (DSCP 0x1A).

Sihlola:

NTP

I-Network Time Protocol (NTP) ibalulekile hhayi kuphela ekunikezeni izitembu zesikhathi ezinembile zamakholi nezinkomfa, kodwa futhi nokuqinisekisa izitifiketi.

Engeza amaseva e-NTP kungqalasizinda yakho ngomyalo othi

ntp server add <server>

Esimweni sethu, kukhona amaseva amabili anjalo, ngakho-ke kuzoba namaqembu amabili.
Sihlola:

Bese usetha indawo yesikhathi yeseva yethu

DNS

Sengeza amaseva e-DNS ku-CMS ngomyalo ofana:

dns add forwardzone <domain-name> <server ip>

Esimweni sethu, kukhona amaseva amabili anjalo, ngakho-ke kuzoba namaqembu amabili.
Sihlola:

Ukucushwa kwe-Network Interface

Silungisa i-interface ngomyalo ofana:

ipv4 <interface> add <address>/<prefix length> <gateway>

Sihlola:

Igama leseva (Igama lomethuleli)

Setha igama leseva ngomyalo ofana:

hostname <name>

Futhi siqala kabusha.


Lokhu kuqeda ukucushwa okuyisisekelo.

Izitifiketi

UmbonoIseva Yomhlangano ye-Cisco idinga ukuxhumana okubethelwe phakathi kwezingxenye ezihlukahlukene, futhi ngenxa yalokho, izitifiketi ze-X.509 ziyadingeka kukho konke ukuthunyelwa kwe-CMS. Basiza ukuqinisekisa ukuthi amasevisi/iseva ithenjwa ngamanye amaseva/amasevisi.

Isevisi ngayinye idinga isitifiketi, kodwa ukudala izitifiketi ezihlukene zesevisi ngayinye kungaholela ekudidekeni nokubankimbinkimbi okungadingekile. Ngenhlanhla, singakwazi ukukhiqiza ipheya yesitifiketi esesidlangalaleni neyimfihlo bese siphinda siwasebenzise kuwo wonke amasevisi amaningi. Esimweni sethu, isitifiketi esifanayo sizosetshenziselwa i-Call Bridge, i-XMPP Server, i-Web Bridge kanye ne-Web Admin. Ngakho-ke, udinga ukudala ipheya yokhiye besitifiketi basesidlangalaleni nabayimfihlo kuseva ngayinye kuqoqo.

Ukuqoqwa kwesizindalwazi, nokho, kunezidingo zesitifiketi ezikhethekile ngakho kudinga izitifiketi zakhona ezehlukile kunezamanye amasevisi. I-CMS isebenzisa isitifiketi seseva, esifana nezitifiketi ezisetshenziswa ezinye iziphakeli, kodwa kukhona nesitifiketi seklayenti esisetshenziselwa ukuxhuma kusizindalwazi. Izitifiketi zesizindalwazi zisetshenziselwa kokubili ukuqinisekiswa nokubethela. Esikhundleni sokuhlinzeka ngegama lomsebenzisi nephasiwedi ukuze iklayenti lixhume kusizindalwazi, iveza isitifiketi seklayenti esithenjwa iseva. Iseva ngayinye kuqoqo lesizindalwazi izosebenzisa amapheya afanayo okhiye basesidlangalaleni nabayimfihlo. Lokhu kuvumela wonke amaseva kuqoqo ukuthi abethele idatha ngendlela yokuthi ingasuswa ukubethela kuphela ngamanye amaseva nawo abelana ngababili okhiye abafanayo.

Ukuze ukuphelelwa umsebenzi kusebenze, amaqoqo esizindalwazi kufanele abe nobuncane bamaseva angu-3, ​​kodwa angabi ngaphezu kuka-5, anesikhathi esiphezulu sokuya nokubuya esingu-200 ms phakathi kwanoma yimaphi amalungu eqoqo. Lo mkhawulo ukhawulelwe kakhulu kunokuhlanganiswa kwe-Call Bridge, ngakho-ke kuvame ukuba yisici esikhawulelayo ekusetshenzisweni okusatshalaliswe ngokwendawo.

Indima yedathabheyisi ye-CMS inenani lezidingo ezihlukile. Ngokungafani nezinye izindima, idinga iklayenti nesitifiketi seseva, lapho isitifiketi seklayenti sinenkambu ethile ye-CN ethulwa kuseva.

I-CMS isebenzisa isizindalwazi se-postgres esinenkosi eyodwa kanye namakhophi amaningana afana ngokuphelele. Kukhona isizindalwazi esisodwa kuphela ngesikhathi (“iseva yesizindalwazi”). Amalungu asele eqoqo ayizifaniso noma "amakhasimende esizindalwazi".

Iqoqo lesizindalwazi lidinga isitifiketi seseva esizinikele kanye nesitifiketi seklayenti. Kufanele zisayinwe izitifiketi, ngokuvamile iziphathimandla zesitifiketi sangasese sangaphakathi. Ngenxa yokuthi noma yiliphi ilungu leqoqo lesizindalwazi lingaba umpetha, iseva egciniwe kanye namapheya wesitifiketi seklayenti (esiqukethe okhiye basesidlangalaleni nabayimfihlo) kufanele akopishwe kuwo wonke amaseva ukuze akwazi ukuthatha ubunikazi beklayenti noma iseva yesizindalwazi. Ngaphezu kwalokho, isitifiketi sempande ye-CA kufanele silayishwe ukuze kuqinisekiswe ukuthi iklayenti kanye nezitifiketi zeseva zingaqinisekiswa.

Ngakho-ke, sakha isicelo sesitifiketi esizosetshenziswa yizo zonke izinsizakalo zeseva ngaphandle kwesizindalwazi (kuzoba nesicelo esihlukile salokhu) ngomyalo ofana:

pki csr hostname CN:cms.example.com subjectAltName:hostname.example.com,example.com,conf.example.com,join.example.com

Ku-CN sibhala igama elijwayelekile lamaseva ethu. Isibonelo, uma amagama osokhaya eziphakeli zethu iseva01, iseva02, iseva03, khona-ke i-CN izoba server.example.com

Senza okufanayo kumaseva amabili asele ngomehluko wokuthi imiyalo izoqukatha “amagama abasingathi” ahambisanayo.

Senza izicelo ezimbili zezitifiketi ezizosetshenziswa isevisi yedathabhesi enemiyalo efana nale:

pki csr dbclusterserver CN:hostname1.example.com subjectAltName:hostname2.example.com,hostname3.example.com

pki csr dbclusterclient CN:postgres

kuphi dbclusterserver и dbclusterclient amagama ezicelo zethu kanye nezitifiketi zesikhathi esizayo, igama lomethuleli1(2)(3) amagama amaseva ahambisanayo.

Senza le nqubo kuphela kuseva eyodwa (!), futhi sizolayisha izitifiketi namafayela .key ahambisanayo kwamanye amaseva.

Nika amandla imodi yesitifiketi seklayenti ku-AD CS

Udinga futhi ukuhlanganisa izitifiketi zeseva ngayinye zibe ifayela elilodwa.Ku-*NIX:

cat server01.cer server02.cer server03.cer > server.cer

Ku-Windows/DOS:

copy server01.cer + server02.cer + server03.cer  server.cer

Futhi layisha kuseva ngayinye:
1. Isitifiketi seseva “somuntu ngamunye”.
2. Isitifiketi sezimpande (kanye nezimaphakathi, uma sikhona).
3. Izitifiketi zesizindalwazi (“iseva” kanye “neklayenti”) namafayela anesandiso esithi .key, akhiqizwa lapho kwakhiwa isicelo sezitifiketi zesizindalwazi “seseva” kanye “neklayenti”. Lawa mafayela kufanele afane kuwo wonke amaseva.
4. Ifayela lazo zontathu izitifiketi “zomuntu ngamunye”.

Ngenxa yalokho, kufanele uthole okuthile okufana nalesi sithombe sefayela kuseva ngayinye.

Iqoqo lesizindalwazi

Manje njengoba usunazo zonke izitifiketi ezilayishwe kumaseva e-CMS, ungalungisa futhi unike amandla ukuqoqwa kwesizindalwazi phakathi kwamanodi amathathu. Isinyathelo sokuqala siwukukhetha iseva eyodwa njengenodi eyinhloko yeqoqo lesizindalwazi futhi uyilungiselele ngokugcwele.

I-Master Database

Isinyathelo sokuqala sokusetha ukuphindaphinda kwesizindalwazi ukucacisa izitifiketi ezizosetshenziswa kusizindalwazi. Lokhu kwenziwa kusetshenziswa umyalo onjengokuthi:

database cluster certs <server_key> <server_crt> <client_key> <client_crt> <ca_crt>

Manje ake sitshele i-CMS ukuthi yisiphi isixhumi esibonakalayo okufanele sisetshenziswe ukuze kuhlanganiswe isizindalwazi ngomyalo:

database cluster localnode a

Bese siqala i-database yeqoqo kuseva eyinhloko ngomyalo:

database cluster initialize

AmaNodi Wesizindalwazi Seklayenti

Senza inqubo efanayo, esikhundleni somyalo kuphela iqoqo lesizindalwazi qalisa faka umyalo njengo:

database cluster join <ip address existing master>

lapho ikheli le-ip elikhona eliyinhloko leseva ye-CMS lapho iqoqo laqalwa khona, ngokumane nje Eliyinhloko.

Sibheka ukuthi iqoqo lethu lesizindalwazi lisebenza kanjani kuwo wonke amaseva ngomyalo:

database cluster status

Senza okufanayo kuseva yesithathu esele.

Ngenxa yalokho, kuvele ukuthi iseva yethu yokuqala yiNkosi, abanye bayizigqila.

Isevisi yomqondisi wewebhu

Nika amandla isevisi yomqondisi wewebhu:

webadmin listen a 445

I-Port 445 ikhethiwe ngoba i-port 443 isetshenziselwa ukufinyelela komsebenzisi kuklayenti lewebhu

Silungiselela isevisi yoMphathi Wewebhu ngamafayela esitifiketi anomyalo ofana:

webadmin certs <keyfile> <certificatefile> <ca bundle>

Futhi unike amandla Umphathi Wewebhu ngomyalo:

webadmin enable

Uma konke kuhamba kahle, sizothola imigqa ye-SUCCESS ebonisa ukuthi Umphathi Wewebhu ulungiselelwe kahle inethiwekhi nesitifiketi. Sihlola ukusebenza kwesevisi sisebenzisa isiphequluli sewebhu bese sifaka ikheli lomphathi wewebhu, isibonelo: cms.example.com: 445

Shayela i-Bridge Cluster

I-Call Bridge ukuphela kwesevisi ekhona kukho konke ukuthunyelwa kwe-CMS. I-Call Bridge iyindlela eyinhloko yenkomfa. Iphinde inikeze isixhumi esibonakalayo se-SIP ukuze izingcingo zidluliselwe kuye noma zisuke kuyo, ngokwesibonelo, i-Cisco Unified CM.

Imiyalo echazwe ngezansi kufanele isetshenziswe kuseva ngayinye enezitifiketi ezifanele.
Ngakho:

Sihlobanisa izitifiketi nesevisi ye-Call Bridge ngomyalo ofana no:

callbridge certs <keyfile> <certificatefile>[<cert-bundle>]

Sibopha izinsiza ze-CallBridge kusixhumi esibonakalayo esisidingayo ngomyalo:

callbridge listen a

Bese uqala kabusha isevisi ngomyalo:

callbridge restart

Manje njengoba sesinamabhuloho ethu e-Call amisiwe, singalungiselela ukuhlanganisa i-Call Bridge. Ukuhlanganisa i-Call Bridge kuhlukile kusizindalwazi noma ukuhlanganisa kwe-XMPP. I-Call Bridge Cluster ingasekela kusuka ku-2 kuya ku-8 nodes ngaphandle kwemikhawulo. Ayihlinzeki nje kuphela ngokuphindaphindeka, kodwa futhi ilayisha ukulinganisa ukuze izingqungquthela zisatshalaliswe ngenkuthalo kuwo wonke amaseva e-Call Bridge kusetshenziswa ukusatshalaliswa kwezingcingo ezihlakaniphile. I-CMS inezici ezengeziwe, amaqembu e-Call Bridge nezici ezihlobene ezingasetshenziselwa ukuphatha okwengeziwe.

I-call bridge clustering ilungiswa ngokuyinhloko ngesixhumi esibonakalayo somlawuli wewebhu
Inqubo echazwe ngezansi kufanele yenziwe kuseva ngayinye kuqoqo.
Ngakho-ke,

1. Ngena kuwebhu uye kokuthi Ukucushwa > Iqoqo.
Buka Kufakiwe 2 In Shayela ubunikazi beBridge Njengegama eliyingqayizivele, faka i-callbridge[01,02,03] ehambisana negama leseva. Lawa magama awasho lutho, kodwa kufanele ahluke kuleli qoqo. Ziyachaza ngokwemvelo ngoba zibonisa ukuthi ziyizihlonzi zeseva [01,02,03].
3.B I-Clustered Call Bridges faka ama-URL womphathi wewebhu wamaseva ethu kuqoqo, CMS[01,02,03].example.com:445, kunkambu Yekheli. Qiniseka ukuthi ucacise imbobo. Ungashiya isizinda se-SIP sesixhumanisi sontanga singenalutho.
4. Engeza isitifiketi ku-CallBridge trust yeseva ngayinye, ifayela eliqukethe zonke izitifiketi zamaseva ethu, esizihlanganise naleli fayela ekuqaleni, ngomyalo ofana nalo:

callbridge trust cluster <trusted cluster certificate bundle>

Bese uqala kabusha isevisi ngomyalo:

callbridge restart

Njengomphumela, kuseva ngayinye kufanele uthole lesi sithombe:

Iqoqo le-XMPP

Isevisi ye-XMPP ku-CMS isetshenziselwa ukuphatha konke ukubhaliswa kanye nokuqinisekisa kwe-Cisco Meeting Apps (CMA), okuhlanganisa neklayenti lewebhu le-CMA WebRTC. I-Call Bridge ngokwayo nayo isebenza njengeklayenti le-XMPP ngezinjongo zokuqinisekisa ngakho-ke kufanele imiswe njengamanye amakhasimende. I-XMPP yokubekezelela amaphutha isici esiye sasekelwa ezindaweni zokukhiqiza kusukela kunguqulo 2.1

Imiyalo echazwe ngezansi kufanele isetshenziswe kuseva ngayinye enezitifiketi ezifanele.
Ngakho:

Sihlobanisa izitifiketi nesevisi ye-XMPP ngomyalo ofana no:

xmpp certs <keyfile> <certificatefile>[<cert-bundle>]

Bese uchaza isixhumi esibonakalayo sokulalela ngomyalo:

xmpp listen a

Isevisi ye-XMPP idinga isizinda esihlukile. Lokhu ukungena ngemvume kwabasebenzisi. Ngamanye amazwi, uma umsebenzisi ezama ukungena ngemvume esebenzisa uhlelo lokusebenza lwe-CMA (noma ngeklayenti le-WebRTC), ufaka umsebenzisiID@logindomain. Esimeni sethu kuzoba userid@conf.example.com. Kungani kungeyona nje i-example.com? Ekusetshenzisweni kwethu okuthile, sikhethe isizinda sethu se-Unified CM abasebenzisi be-Jabber abazosisebenzisa ku-Unified CM njenge-example.com, ngakho-ke besidinga isizinda esihlukile kubasebenzisi be-CMS ukuze bahambise amakholi aya futhi asuke ku-CMS ngokusebenzisa izizinda ze-SIP.

Misa isizinda se-XMPP usebenzisa umyalo ofana no:

xmpp domain <domain>

Futhi unike amandla isevisi ye-XMPP ngomyalo:

xmpp enable

Kusevisi ye-XMPP, kufanele udale imininingwane ye-Call Bridge ngayinye ezosetshenziswa uma ubhalisa ngesevisi ye-XMPP. Lawa magama awasho lutho (futhi awahlobene namagama ahlukile owalungisele ukuhlanganisa i-call bridge). Kufanele wengeze amabhuloho okushaya ucingo amathathu kuseva eyodwa ye-XMPP bese ufaka lezo mininingwane kwamanye amaseva e-XMPP kuqoqo ngoba lokhu kulungiselelwa akungeni kusizindalwazi seqoqo. Kamuva sizomisa i-Call Bridge ngayinye ukusebenzisa leli gama nemfihlo ukuze ubhalise nesevisi ye-XMPP.

Manje sidinga ukumisa isevisi ye-XMPP kuseva yokuqala enama-Call Bridges amathathu callbridge01, callbridge02 kanye ne-callbridge03. I-akhawunti ngayinye izonikezwa amaphasiwedi angahleliwe. Kamuva zizongeniswa kwamanye amaseva e-Call Bridge ukuze ungene kule seva ye-XMPP. Faka imiyalo elandelayo:

xmpp callbridge add callbridge01
xmpp callbridge add callbridge02
xmpp callbridge add callbridge03

Ngenxa yalokho, sihlola ukuthi kwenzekeni ngomyalo:

xmpp callbridge list

Isithombe esifanayo kufanele sivele kumaseva asele ngemva kwezinyathelo ezichazwe ngezansi.

Okulandelayo, sengeza izilungiselelo ezifanayo ncamashi kumaseva amabili asele, kuphela ngemiyalo

xmpp callbridge add-secret callbridge01
xmpp callbridge add-secret callbridge02
xmpp callbridge add-secret callbridge03

Sengeza imfihlo ngokucophelela ukuze, ngokwesibonelo, zingabikho izikhala ezengeziwe kuyo.


Ngenxa yalokho, iseva ngayinye kufanele ibe nesithombe esifanayo:

Okulandelayo, kuwo wonke amaseva kuqoqo, sicacisa ngokuthemba ifayela eliqukethe zonke izitifiketi ezintathu, ezidalwe ngaphambili ngomyalo ofana nalo:

xmpp cluster trust <trust bundle>

Sivumela imodi yeqoqo le-xmpp kuwo wonke amaseva eqoqo ngomyalo:

xmpp cluster enable

Kuseva yokuqala yeqoqo, siqala ukudalwa kweqoqo le-xmpp ngomyalo:

xmpp cluster initialize

Kwamanye amaseva, engeza iqoqo ku-xmpp ngomyalo ofana no:

xmpp cluster join <ip address head xmpp server>

Sibheka kuseva ngayinye impumelelo yokudala iqoqo le-XMPP kuseva ngayinye ngemiyalo:

xmpp status
xmpp cluster status

Iseva yokuqala:

Iseva yesibili:

Iseva yesithathu:

Ixhuma i-Call Bridge ku-XMPP

Manje njengoba iqoqo le-XMPP selisebenza, udinga ukulungisa amasevisi e-Call Bridge ukuze uxhume kuqoqo le-XMPP. Lokhu kulungiselelwa kwenziwa ngomphathi wewebhu.

Kuseva ngayinye, yiya kokuthi Ukucushwa > Okuvamile nasensimini Igama eliyingqayizivele le-Call Bridge bhala amagama ahlukile ahambelana neseva Call Bridge i-callbridge[01,02,03]... Ensimini Domain conf.example.ru kanye namaphasiwedi ahambisanayo, ungawahlola
kunoma iyiphi iseva ku-cluster enomyalelo:

xmpp callbridge list

Shiya inkambu ethi “Iseva” ingenalutho ICallbridge izokwenza ukubheka kwe-DNS SRV _xmpp-component._tcp.conf.example.comukuthola iseva ye-XMPP etholakalayo. Amakheli e-IP wokuxhuma ama-callbridge ku-XMPP angase ahluke kuseva ngayinye, kuya ngokuthi yimaphi amanani abuyiselwa esicelweni serekhodi. _xmpp-component._tcp.conf.example.com callbridge, yona encike kuzilungiselelo ezibalulekile zerekhodi le-DNS elinikeziwe.

Okulandelayo, iya kokuthi Isimo > Okuvamile ukuze uqinisekise ukuthi isevisi ye-Call Bride ixhunywe ngempumelelo yini kusevisi ye-XMPP.

Ibhuloho lewebhu

Kuseva ngayinye kuqoqo, nika amandla isevisi ye-Web Bridge ngomyalo:

webbridge listen a:443

Silungiselela isevisi ye-Web Bridge ngamafayela esitifiketi anomyalo ofana no:

webbridge  certs <keyfile> <certificatefile> <ca bundle>

I-Web Bridge isekela i-HTTPS. Izoqondisa kabusha i-HTTP ku-HTTPS uma ilungiselelwe ukusebenzisa i-"http-redirect".
Ukuze unike amandla ukuqondisa kabusha kwe-HTTP, sebenzisa umyalo olandelayo:

webbridge http-redirect enable

Ukwazisa i-Call Bridge ukuthi i-Web Bridge ingathembela ekuxhumekeni okuvela ku-Call Bridge, sebenzisa umyalo:

webbridge trust <certfile>

lapho leli kuyifayela eliqukethe zonke izitifiketi ezintathu ezivela kuseva ngayinye kuqoqo.

Lesi sithombe kufanele sibe kuwo wonke amaseva kuqoqo.


Manje sidinga ukudala umsebenzisi ngendima ethi "appadmin", siyayidinga ukuze sikwazi ukumisa iqoqo lethu (!), hhayi iseva ngayinye kuqoqo ngokwehlukana, ngale ndlela izilungiselelo zizosetshenziswa ngokulinganayo kuseva ngayinye naphezu kwe iqiniso lokuthi zizokwenziwa kanye.


Ukuze sisethe kabusha sizosebenzisa Postman.

Ukuze uthole ukugunyazwa, khetha Okuyisisekelo esigabeni sokugunyaza

Ukuze uthumele kahle imiyalo kuseva ye-CMS, udinga ukusetha umbhalo wekhodi odingekayo

Sicacisa i-Webbridge ngomyalo I-POST ngepharamitha i-url kanye nencazelo cms.example.com



Kubhuloho ngokwayo, sibonisa imingcele edingekayo: ukufinyelela kwezivakashi, ukufinyelela okuvikelwe, njll.

Shayela Amaqembu Ebhuloho

Ngokuzenzakalelayo, i-CMS ayisebenzisi kahle kakhulu izinsiza zenkomfa ezitholakalayo kuyo.

Isibonelo, emhlanganweni onabahlanganyeli abathathu, umhlanganyeli ngamunye angase agcine etholakala kuma-Call Bridges amathathu ahlukene. Ukuze laba bahlanganyeli abathathu baxhumane, i-Call Bridges izosungula ngokuzenzakalelayo ukuxhumana phakathi kwawo wonke amaseva namaklayenti esikhaleni esifanayo, ukuze konke kubukeke sengathi wonke amaklayenti akuseva efanayo. Ngeshwa, okubi kulokhu ukuthi ingqungquthela eyodwa yabantu abathathu manje izodla izimbobo zemidiya eziyi-3. Lokhu ngokusobala ukusetshenziswa kwezinsiza ngendlela engafanele. Ukwengeza, lapho i-Call Bridge igcwele ngokweqile, indlela ezenzakalelayo iwukuqhubeka nokwamukela izingcingo nokuhlinzeka ngesevisi yekhwalithi encishisiwe kubo bonke ababhalisile balelo bhuloho lezingcingo.

Lezi zinkinga zixazululwa kusetshenziswa isici se-Call Bridge Group. Lesi sici sethulwe enguqulweni engu-2.1 yesofthiwe ye-Cisco Meeting Server futhi sinwetshiwe ukuze sisekele ukulinganisela kokulayisha kukho kokubili amakholi angenayo naphumayo e-Cisco Meeting App (CMA), okuhlanganisa ababambiqhaza be-WebRTC.

Ukuze kuxazululwe inkinga yokuxhuma kabusha, imikhawulo emithathu yokulayisha elungisekayo yethuliwe ku-Call Bridge ngayinye:

LoadLimit - Lona inani eliphezulu lomthwalo wezinombolo ze-Call Bridge ethile. Inkundla ngayinye inomkhawulo wokulayisha onconyiwe, njengokuthi 96000 ku-CMS1000 kanye no-1.25 GHz nge-vCPU ngayinye yomshini obonakalayo. Izingcingo ezihlukene zisebenzisa inani elithile lezinsiza kuye ngokulungiswa nezinga lozimele lomhlanganyeli.
I-NewConferenceLoadLimitBasisPoints (okuzenzakalelayo 50% loadLimit) - isetha umkhawulo wokulayisha iseva, ngemva kwalokho izingqungquthela ezintsha zenqatshwa.
I-ExistingConferenceLoadLimitBasisPoints (okuzenzakalelayo 80% of loadLimit) - inani lomthwalo weseva ngemva kwalokho ababambiqhaza abajoyina ingqungquthela ekhona bazonqatshwa.

Nakuba lesi sici sasidizayinelwe ukusatshalaliswa kwezingcingo nokulinganisa ukulayisha, amanye amaqembu afana namaseva e-TURN, Amaseva e-Web Bridge namaRekhoda nawo anganikezwa ku-Call Bridge Groups ukuze nawo aqoqwe kahle ukuze asetshenziswe ngokugcwele. Uma noma yiziphi zalezi zinto zingabelwe eqenjini lezingcingo, zithathwa njengezitholakala kuwo wonke amaseva ngaphandle kokuza kuqala okuthile.

Lawa mapharamitha amisiwe lapha: cms.example.com:445/api/v1/system/configuration/cluster

Okulandelayo, sibonisa ibhuloho ngalinye ukuthi iliphi iqembu le-callbridge eyingxenye yalo:

I-callbridge yokuqala

I-callbridge yesibili

I-callbridge yesithathu


Ngakho-ke, silungiselele iqembu le-Call Brdige ukuthi lisebenzise ngokuphumelelayo izinsiza zeqoqo le-Cisco Meeting Server.

Ingenisa abasebenzisi ku-Active Directory

Isevisi yoMphathi Wewebhu inesigaba sokumisa i-LDAP, kodwa ayinikezi izinketho zokumisa eziyinkimbinkimbi, futhi ulwazi alugcinwa kusizindalwazi seqoqo, ngakho-ke ukulungiselelwa kuyodingeka kwenziwe, ngokwenza ngesandla kuseva ngayinye ngokusebenzisa i-Web interface, noma ngokusebenzisa i-API, futhi ukuze "izikhathi ezintathu "Ungavuki" sisazosetha idatha nge-API.

Ukusebenzisa i-URL ukuze ufinyelele cms01.example.com:445/api/v1/ldapServer adala into Yeseva ye-LDAP, ecacisa amapharamitha afana nokuthi:

• IP yeseva
• inombolo yechweba
• Igama lomsebenzisi
• iphasiwedi
• kulondeke

Vikela - khetha iqiniso noma amanga kuye ngokuthi ichweba, 389 - ayivikelekile, 636 - ivikelwe.


Ukwenza imephu amapharamitha womthombo we-LDAP kuzibaluli Kuseva Yomhlangano we-Cisco.
Imephu ye-LDAP yenza imephu yezibaluli kuhla lwemibhalo lwe-LDAP kuya kuzibaluli eziku-CMS. Izibaluli zangempela:

• I-jidMapping
• IgamaMapping
• coSpaceNameMapping
• coSpaceUriMapping
• coSpaceSecondaryUriMapping

Incazelo yezimfaneloI-JID imele i-ID yokungena yomsebenzisi ku-CMS. Njengoba lena kuyiseva ye-LDAP ye-Microsoft Active Directory, i-CMS JID ibeka ku-sAMAccountName ku-LDAP, okuyi-ID yokungena ye-Active Directory yomsebenzisi. Futhi qaphela ukuthi uthatha sAMAccountName bese wengeza isizinda conf.pod6.cms.lab ekugcineni kwayo ngoba lokhu ukungena abasebenzisi bakho abazokusebenzisa ukuze bangene ku-CMS.

IgamaMapping ifanisa oqukethwe kunkambu ye-Active Directory displayName nenkambu yegama le-CMS yomsebenzisi.

coSpaceNameMapping idala igama lesikhala se-CMS ngokusekelwe kunkambu ye-DisplayName. Lesi sibaluli, kanye nesibaluli se-coSpaceUriMapping, yiso esidingekayo ukuze kwakhiwe isikhala somsebenzisi ngamunye.

coSpaceUriMapping ichaza ingxenye yomsebenzisi ye-URI ehlotshaniswa nesikhala somuntu siqu somsebenzisi. Ezinye izizinda zingalungiselelwa ukuthi zishayelwe emkhathini. Uma ingxenye yomsebenzisi ifana nale nkambu kwenye yalezi zizinda, ikholi izoqondiswa esikhaleni salowo msebenzisi.

coSpaceSecondaryUriMapping ichaza i-URI yesibili ukuze kufinyelelwe esikhaleni. Lokhu kungasetshenziswa ukwengeza isibizo sezinombolo zokuqondisa amakholi esikhaleni somsebenzisi ongenisiwe njengenye indlela ye-URI yezinhlamvu nezinombolo echazwe kupharamitha ye-coSpaceUriMapping.

Iseva ye-LDAP kanye nemephu ye-LDAP kumisiwe. Manje udinga ukuwaxhumanisa ndawonye ngokwakha umthombo we-LDAP.

Ukusebenzisa i-URL ukuze ufinyelele cms01.example.com:445/api/v1/ldapSource dala into engumthombo we-LDAP, ucacise amapharamitha afana nalawa:

• Iseva
• mapping
• baseDn
• lemifanekiso

Manje njengoba ukucushwa kwe-LDAP sekuqediwe, ungenza umsebenzi wokuvumelanisa owenziwe ngesandla.

Lokhu sikwenza ku-Web interface yeseva ngayinye ngokuchofoza Vumelanisa manje esigabeni I-Active Directory


noma nge-API ngomyalo I-POST usebenzisa i-URL ukuze ufinyelele cms01.example.com:445/api/v1/ldapSyncs

Izinkomfa ze-Ad-Hoc

Kuyini lokhu?Emcabangweni wendabuko, ingqungquthela yilapho abahlanganyeli ababili bekhuluma bodwa, futhi omunye wabahlanganyeli (esebenzisa idivayisi ebhaliswe ne-Unified CM) ecindezela inkinobho ethi "Conference", ashayele omunye umuntu, futhi ngemva kokukhuluma nalowo muntu wesithathu. , cindezela inkinobho "Inkomfa".

Okuhlukanisa ingqungquthela ye-Ad-Hoc engqungqutheleni ehleliwe ku-CMS ukuthi ingqungquthela ye-Ad-Hoc ayilona nje ucingo lwe-SIP oluya ku-CMS. Uma umqali wenkomfa echofoza inkinobho Yenkomfa okwesibili ukuze ameme wonke umuntu emhlanganweni ofanayo, i-Unified CM kufanele yenze ikholi ye-API eya ku-CMS ukuze idale ingqungquthela lapho zonke izingcingo zidluliselwa khona. Konke lokhu kwenzeka bengabonwa ababambe iqhaza.

Lokhu kusho ukuthi i-Unified CM kufanele ilungiselele izifakazelo ze-API nekheli/imbobo ye-WebAdmin yesevisi kanye ne-SIP Trunk ngokuqondile kuseva ye-CMS ukuze uqhubeke nekholi.

Uma kudingekile, i-CUCM ingakwazi ukudala isikhala ku-CMS ukuze ikholi ngayinye ifinyelele i-CMS futhi ifane nomthetho wekholi engenayo ohloselwe izikhala.

Ukuhlanganiswa ne-CUCM ihlelwe ngendlela efanayo njengoba kuchazwe esihlokweni phambilini ngaphandle kokuthi ku-Cisco UCM udinga ukwakha iziqu ezintathu ze-CMS, amabhuloho amathathu eNgqungquthela, kuPhrofayela Yokuphepha ye-SIP ucacise Amagama Ezihloko ezintathu, Amaqembu Omzila, Uhlu Lwemizila, Amaqembu Ezinsiza Zemidiya kanye Nohlu Lweqembu Lokuthola Imithombo Yezindaba, bese wengeza imithetho embalwa yomzila. ku-Cisco Meeting Server.

Iphrofayela Yokuphepha ye-SIP:


Iziqu:


Isiqu ngasinye sibukeka sifana:




Conference Bridge


Ibhuloho ngalinye leNgqungquthela libukeka ngendlela efanayo:


Iqembu Lomzila


Uhlu Lwemizila


Iqembu lemithombo yezindaba


Uhlu Lweqembu Lemithombo Yezindaba

Shayela Imithetho

Ngokungafani nezinhlelo zokuphatha ucingo ezithuthuke kakhulu njenge-Unified CM noma i-Expressway, i-CMS ibheka kuphela isizinda kunkambu ye-SIP Isicelo-URI ukuze uthole amakholi amasha. Ngakho-ke uma i-SIP INVITE ingeye-sip: [i-imeyili ivikelwe]I-CMS ikhathalela kuphela i-domain.com. I-CMS ilandela le mithetho ukuze inqume ukuthi izolushayela kuphi ucingo:

1. I-CMS iqala ngokuzama ukufanisa isizinda se-SIP nezizinda ezilungiselelwe emithethweni yezingcingo ezingenayo. Lawa makholi angase adluliselwe ezikhaleni (“ezihlosiwe”) noma kubasebenzisi abathile, ama-IVR angaphakathi, noma izindawo okuyiwa kuzo ezihlanganiswe ngokuqondile ze-Microsoft Lync/Skype for Business (S4B).
2. Uma kungekho okufanayo emithethweni yekholi engenayo, i-CMS izozama ukufanisa isizinda esimiswe kuthebula lokudlulisela ikholi. Uma okufanayo kwenziwa, umthetho unganqaba ngokusobala ucingo noma udlulisele ucingo. Ngalesi sikhathi, i-CMS ingase ibhale kabusha isizinda, ngezinye izikhathi esiwusizo ekushayeleni izizinda ze-Lync. Ungaphinda ukhethe ukudlula ukuphosa, okusho ukuthi azikho izinkambu ezizophinde zilungiswe, noma usebenzise uhlelo lwangaphakathi lokudayela lwe-CMS. Uma kungekho okufanayo emithethweni yokudlulisa ucingo, okumisiwe wukudikila ucingo. Khumbula ukuthi ku-CMS, nakuba ucingo "ludluliswa", abezindaba basaboshiwe ku-CMS, okusho ukuthi izoba semgwaqweni wokusayina kanye nabezindaba.
Bese kuphela izingcingo ezidlulisiwe zingaphansi kwemithetho yezingcingo eziphumayo. Lezi zilungiselelo zinquma izindawo lapho izingcingo zithunyelwa khona, uhlobo lwe-trunk (noma ngabe ucingo lwe-Lync olusha noma ucingo olujwayelekile lwe-SIP), kanye nanoma yikuphi ukuguqulwa okungenziwa uma ukudlulisa kungakhethwanga emthethweni wokudlulisela ikholi.

Nali ilogi langempela lalokho okwenzeka phakathi nengqungquthela ye-Ad-Hoc

Isithombe-skrini sibonisa kabi (angazi ukuthi ngingayenza kanjani ibe ngcono), ngakho-ke ngizobhala ilogi kanje:

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:12

Ingqungquthela ye-Ad-Hoc ngokwayo:


Imithetho Yezingcingo Ezingenayo
Ukulungisa amapharamitha amakholi angenayo kuyadingeka ukuze ukwazi ukwamukela ucingo ku-CMS. Njengoba ubonile ekusethweni kwe-LDAP, bonke abasebenzisi bangenisiwe ngesizinda conf.pod6.cms.lab. Ngakho-ke, okungenani, ufuna amakholi kulesi sizinda ukuze uqondise izikhala. Uzodinga futhi ukumisa imithetho yayo yonke into ehloselwe igama lesizinda elifaneleke ngokugcwele (futhi mhlawumbe nekheli le-IP) leseva ngayinye ye-CMS. Ukulawulwa kwethu kwezingcingo kwangaphandle, i-Unified CM, izomisa iziqu ze-SIP ezinikezelwe kuseva ngayinye ye-CMS ngayodwana. Kuye ngokuthi indawo yalezi ziqu ze-SIP iyikheli le-IP noma i-FQDN yeseva izonquma ukuthi i-CMS idinga ukulungiswa ukuze yamukele amakholi aqondiswe ekhelini layo le-IP noma i-FQDN.

Isizinda esinomthetho ongenayo ongenayo obalulekile kakhulu sisetshenziswa njengesizinda sanoma yiziphi izikhala zomsebenzisi. Uma abasebenzisi bavumelanisa nge-LDAP, i-CMS idala izikhala ngokuzenzakalelayo, kodwa ingxenye yomsebenzisi kuphela ye-URI (coSpaceUriMapping), isibonelo, user.space. Ingxenye domain I-URI egcwele ikhiqizwa ngokusekelwe kulo mthetho. Eqinisweni, uma ubungangena ku-Web Bridge ngalesi sikhathi, uzobona ukuthi i-Space URI ayinaso isizinda. Ngokusetha lo mthetho njengobaluleke kakhulu, ubeka isizinda ukuze izikhala ezikhiqiziwe zibe conf.example.com.


Imithetho Yezingcingo Eziphumayo

Ukuze uvumele abasebenzisi ukuthi benze amakholi aphumayo kuqoqo le-Unified CM, kufanele ulungiselele imithetho ephumayo. Isizinda samaphoyinti okugcina abhaliswe ne-Unified CM, njenge-Jabber, sithi example.com. Izingcingo eziya kulesi sizinda kufanele zihanjiswe njengezingcingo ezijwayelekile ze-SIP eziya kumanodi okucubungula amakholi e-CM Ehlanganisiwe. Iseva eyinhloko ithi cucm-01.example.com, futhi iseva eyengeziwe ithi cucm-02.example.com.

Umthetho wokuqala uchaza umzila olula wamakholi phakathi kwamaseva eqoqo.

Insimu Indawo kusuka esizindeni unesibopho salokho okuzoboniswa ku-SIP-URI yofonayo kumuntu obizwa ngemva kophawu “@”. Uma siyishiya ingenalutho, ngemva kophawu "@" kuzoba nekheli le-IP le-CUCM lapho lolu kholi ludlula khona. Uma sicacisa isizinda, ngemva kophawu “@” kuzoba khona isizinda. Lokhu kuyadingeka ukuze ukwazi ukuphinda ushayele, ngaphandle kwalokho ngeke ukwazi ukuphinda ushayele nge-SIP-URI name@ip-address.

Shayela uma kukhonjisiwe Indawo kusuka esizindeni


Shayela nini CHA kukhonjisiwe Indawo kusuka esizindeni


Qiniseka ukuthi ucacise ngokucacile Okubethelwe noma Okungabhaliwe kumakholi aphumayo, ngoba akukho okusebenzayo nepharamitha ye-Auto.

Ukurekhoda

Izinkomfa zevidiyo zirekhodwa iseva Yokurekhoda. Irekhoda ifana ncamashi ne-Cisco Meeting Server. Isirekhoda asidingi ukufakwa kwanoma yimaphi amalayisensi. Amalayisense okurekhoda ayadingeka kumaseva asebenzisa amasevisi e-CallBridge, i.e. ilayisensi Yokurekhoda iyadingeka futhi kufanele isetshenziswe engxenyeni ye-CallBridge, hhayi kwiseva esebenzisa Isiqophi. Irekhoda liziphatha njengeklayenti le-Extensible Messaging and Presence Protocol (XMPP), ngakho-ke iseva ye-XMPP kufanele inikwe amandla kuseva ebamba i-CallBridge.

Ngoba Sineqoqo futhi ilayisensi idinga "ukunwetshwa" kuwo wonke amaseva amathathu kuqoqo. Bese-ke ku-akhawunti yakho yomuntu siqu kumalayisensi esiwahlobanisa (sengeza) amakheli e-MAC we-a-interface yawo wonke amaseva e-CMS afakwe kuqoqo.

Futhi lesi yisithombe okufanele sibe kuyo yonke iseva kuqoqo

Ngokuvamile, kunezimo ezimbalwa zokubeka Irekhoda, kodwa sizonamathela kulokhu:


Ngaphambi kokusetha Isiqophi, udinga ukulungiselela indawo lapho izingqungquthela zevidiyo zizorekhodwa khona ngempela. Empeleni lapha isixhumanisi, indlela yokusetha konke Ukuqopha. Ngigxila emaphuzwini abalulekile nemininingwane:

1. Kungcono ukushelela isitifiketi kuseva yokuqala kuqoqo.
2. Iphutha elithi “Irekhodi alitholakali” lingase lenzeke ngoba isitifiketi esingalungile sishiwo ku-Trust Yokurekhoda.
3. Ukubhala kungase kungasebenzi uma uhla lwemibhalo lwe-NFS olushiwo ukuze luqoshwe kungelona umsuka wemibhalo.

Kwesinye isikhathi kunesidingo sokuqopha ngokuzenzakalelayo ingqungquthela yomsebenzisi oyedwa noma isikhala.

Ukuze wenze lokhu, kwakhiwa ama-CallProfiles amabili:
Ukurekhoda kukhutshaziwe


Futhi ngokuzenzakalelayo umsebenzi wokuqopha


Okulandelayo, "sinamathisela" i-CallProfile enomsebenzi wokurekhoda ozenzakalelayo endaweni oyifunayo.


Ku-CMS kusungulwe kangangokuthi uma i-CallProfile iboshelwe ngokusobala kunoma yisiphi isikhala noma isikhala, khona-ke le CallProfile isebenza kuphela ngokuhlobene nalezi zikhala ezithile. Futhi uma i-CallProfile ingaboshelwe kunoma yisiphi isikhala, ngokuzenzakalelayo isetshenziswa kulezo zikhala lapho i-CallProfile iboshelwe khona ngokucacile.

Ngokuzayo ngizozama ukuchaza ukuthi i-CMS ifinyelelwa kanjani ngaphandle kwenethiwekhi yangaphakathi yenhlangano.

Imithombo:

• www.cisco.com/c/dam/en/us/td/docs/conferencing/ciscoMeetingServer/Deployment_Guide/Version-2-5/Cisco-Meeting-Server-2-5-Single-Combined-Server-Deployment.pdf
• www.cisco.com/c/en/us/support/docs/conferencing/meeting-server/202722-Configure-Recorder-in-CMS-Acano-Call-Bri.html
• www.cisco.com/c/dam/en/us/td/docs/conferencing/ciscoMeetingServer/Reference_Guides/Version-2-3/Cisco-Meeting-Server-MMP-Command-Reference-2-3.pdf
• www.cisco.com/c/dam/en/us/td/docs/conferencing/ciscoMeetingServer/Reference_Guides/Version-2-5/Cisco-Meeting-Server-API-Reference-Guide-2-4-and-later. pdf

Source: www.habr.com