[cisco-voip] configure Transcoders in AS5400XM router...
Hello folks, trying to configure 5400 router as my media resource box for transcoders and conference bridges but unable to find sccp, dsp commands etc. IOS version is c5400-ik9s-mz.151-3.T4.bin and inventory is listed down. any one has idea about how to configure these PVDMS in 5400?Thanks for your help,MAK KKVG1#show inventory NAME: AS5400XM chassis, DESCR: AS5400XM chassisPID: AS5400XM , VID: V05, SN: JAE162603MG NAME: AS5X-FC_1, DESCR: AS5000 Feature Card with Six AS5X PVDM DSP Module SlotsPID: AS5X-FC , VID: V01, SN: JAE163007ZF NAME: PVDMII DSP SIMM with four DSPs 1/0, DESCR: PVDMII DSP SIMM with four DSPsPID: AS5X-PVDM2-64 , VID: V01, SN: FOC163221YC NAME: PVDMII DSP SIMM with four DSPs 1/1, DESCR: PVDMII DSP SIMM with four DSPsPID: AS5X-PVDM2-64 , VID: V01, SN: FOC163221Z6 NAME: PVDMII DSP SIMM with four DSPs 1/2, DESCR: PVDMII DSP SIMM with four DSPsPID: AS5X-PVDM2-64 , VID: V01, SN: FOC163221VH NAME: PVDMII DSP SIMM with four DSPs 1/3, DESCR: PVDMII DSP SIMM with four DSPsPID: AS5X-PVDM2-64 , VID: V01, SN: FOC163221Y7 NAME: PVDMII DSP SIMM with four DSPs 1/4, DESCR: PVDMII DSP SIMM with four DSPsPID: AS5X-PVDM2-64 , VID: V01, SN: FOC163221PH NAME: PVDMII DSP SIMM with four DSPs 1/5, DESCR: PVDMII DSP SIMM with four DSPsPID: AS5X-PVDM2-64 , VID: V01, SN: FOC1632220Q NAME: AS5X-FC_2, DESCR: AS5000 Feature Card with Six AS5X PVDM DSP Module SlotsPID: AS5X-FC , VID: V01, SN: JAE163007ZD NAME: PVDMII DSP SIMM with four DSPs 2/0, DESCR: PVDMII DSP SIMM with four DSPsPID: AS5X-PVDM2-64 , VID: V01, SN: FOC163221Z7 NAME: PVDMII DSP SIMM with four DSPs 2/1, DESCR: PVDMII DSP SIMM with four DSPsPID: AS5X-PVDM2-64 , VID: V01, SN: FOC163221VF NAME: PVDMII DSP SIMM with four DSPs 2/2, DESCR: PVDMII DSP SIMM with four DSPsPID: AS5X-PVDM2-64 , VID: V01, SN: FOC163221ZF NAME: PVDMII DSP SIMM with four DSPs 2/3, DESCR: PVDMII DSP SIMM with four DSPsPID: AS5X-PVDM2-64 , VID: V01, SN: FOC163221W1 NAME: PVDMII DSP SIMM with four DSPs 2/4, DESCR: PVDMII DSP SIMM with four DSPsPID: AS5X-PVDM2-64 , VID: V01, SN: FOC163221Q7 NAME: PVDMII DSP SIMM with four DSPs 2/5, DESCR: PVDMII DSP SIMM with four DSPsPID: AS5X-PVDM2-64 , VID: V01, SN: FOC163221ZW NAME: AS5X-FC_3, DESCR: AS5000 Feature Card with Six AS5X PVDM DSP Module SlotsPID: AS5X-FC , VID: V01, SN: JAE16300812 NAME: PVDMII DSP SIMM with four DSPs 3/0, DESCR: PVDMII DSP SIMM with four DSPsPID: AS5X-PVDM2-64 , VID: V01, SN: FOC16322200 NAME: PVDMII DSP SIMM with four DSPs 3/1, DESCR: PVDMII DSP SIMM with four DSPsPID: AS5X-PVDM2-64 , VID: V01, SN: FOC1632220C NAME: PVDMII DSP SIMM with four DSPs 3/2, DESCR: PVDMII DSP SIMM with four DSPsPID: AS5X-PVDM2-64 , VID: V01, SN: FOC163221PN NAME: PVDMII DSP SIMM with four DSPs 3/3, DESCR: PVDMII DSP SIMM with four DSPsPID: AS5X-PVDM2-64 , VID: V01, SN: FOC163221VE NAME: PVDMII DSP SIMM with four DSPs 3/4, DESCR: PVDMII DSP SIMM with four DSPsPID: AS5X-PVDM2-64 , VID: V01, SN: FOC16322203 NAME: PVDMII DSP SIMM with four DSPs 3/5, DESCR: PVDMII DSP SIMM with four DSPsPID: AS5X-PVDM2-64 , VID: V01, SN: FOC1632220X NAME: AS5X-FC_4, DESCR: AS5000 Feature Card with Six AS5X PVDM DSP Module SlotsPID: AS5X-FC , VID: V01, SN: JAE15400DKU NAME: PVDMII DSP SIMM with four DSPs 4/0, DESCR: PVDMII DSP SIMM with four DSPsPID: AS5X-PVDM2-64 , VID: V01, SN: FOC163221QK NAME: PVDMII DSP SIMM with four DSPs 4/1, DESCR: PVDMII DSP SIMM with four DSPsPID: AS5X-PVDM2-64 , VID: V01, SN: FOC163221YW NAME: PVDMII DSP SIMM with four DSPs 4/2, DESCR: PVDMII DSP SIMM with four DSPsPID: AS5X-PVDM2-64 , VID: V01, SN: FOC1632220Z NAME: PVDMII DSP SIMM with four DSPs 4/3, DESCR: PVDMII DSP SIMM with four DSPsPID: AS5X-PVDM2-64 , VID: V01, SN: FOC16322206 NAME: PVDMII DSP SIMM with four DSPs 4/4, DESCR: PVDMII DSP SIMM with four DSPsPID: AS5X-PVDM2-64 , VID: V01, SN: FOC163221ZB NAME: PVDMII DSP SIMM with four DSPs 4/5, DESCR: PVDMII DSP SIMM with four DSPsPID: AS5X-PVDM2-64 , VID: V01, SN: FOC163221ZV NAME: AS5X-FC_5, DESCR: AS5000 Feature Card with Six AS5X PVDM DSP Module SlotsPID: AS5X-FC , VID: V01, SN: JAE162401C0 NAME: PVDMII DSP SIMM with four DSPs 5/0, DESCR: PVDMII DSP SIMM with four DSPsPID: AS5X-PVDM2-64 , VID: V01, SN: FOC163221VK NAME: PVDMII DSP SIMM with four DSPs 5/1, DESCR: PVDMII DSP SIMM with four DSPsPID: AS5X-PVDM2-64 , VID: V01, SN: FOC163221VA NAME: PVDMII DSP SIMM with four DSPs 5/2, DESCR: PVDMII DSP SIMM with four DSPsPID: AS5X-PVDM2-64 , VID: V01, SN: FOC163221Q6 NAME: PVDMII DSP SIMM with four DSPs 5/3, DESCR: PVDMII DSP SIMM with four DSPsPID: AS5X-PVDM2-64 , VID: V01, SN: FOC1632220W NAME: T3_7, DESCR: CT3 DFC, HwVer#: 6.0PID: , VID: , SN: JAE163107DZ___ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
Re: [cisco-voip] configure Transcoders in AS5400XM router...
Do you have dsp services dspfarm configured under the voice-cards? On Wed, Aug 12, 2015 at 5:18 PM, Mudassar M via cisco-voip cisco-voip@puck.nether.net wrote: Hello folks, trying to configure 5400 router as my media resource box for transcoders and conference bridges but unable to find sccp, dsp commands etc. IOS version is c5400-ik9s-mz.151-3.T4.bin and inventory is listed down. any one has idea about how to configure these PVDMS in 5400? Thanks for your help, MAK KKVG1#show inventory NAME: AS5400XM chassis, DESCR: AS5400XM chassis PID: AS5400XM , VID: V05, SN: JAE162603MG NAME: AS5X-FC_1, DESCR: AS5000 Feature Card with Six AS5X PVDM DSP Module Slots PID: AS5X-FC , VID: V01, SN: JAE163007ZF NAME: PVDMII DSP SIMM with four DSPs 1/0, DESCR: PVDMII DSP SIMM with four DSPs PID: AS5X-PVDM2-64 , VID: V01, SN: FOC163221YC NAME: PVDMII DSP SIMM with four DSPs 1/1, DESCR: PVDMII DSP SIMM with four DSPs PID: AS5X-PVDM2-64 , VID: V01, SN: FOC163221Z6 NAME: PVDMII DSP SIMM with four DSPs 1/2, DESCR: PVDMII DSP SIMM with four DSPs PID: AS5X-PVDM2-64 , VID: V01, SN: FOC163221VH NAME: PVDMII DSP SIMM with four DSPs 1/3, DESCR: PVDMII DSP SIMM with four DSPs PID: AS5X-PVDM2-64 , VID: V01, SN: FOC163221Y7 NAME: PVDMII DSP SIMM with four DSPs 1/4, DESCR: PVDMII DSP SIMM with four DSPs PID: AS5X-PVDM2-64 , VID: V01, SN: FOC163221PH NAME: PVDMII DSP SIMM with four DSPs 1/5, DESCR: PVDMII DSP SIMM with four DSPs PID: AS5X-PVDM2-64 , VID: V01, SN: FOC1632220Q NAME: AS5X-FC_2, DESCR: AS5000 Feature Card with Six AS5X PVDM DSP Module Slots PID: AS5X-FC , VID: V01, SN: JAE163007ZD NAME: PVDMII DSP SIMM with four DSPs 2/0, DESCR: PVDMII DSP SIMM with four DSPs PID: AS5X-PVDM2-64 , VID: V01, SN: FOC163221Z7 NAME: PVDMII DSP SIMM with four DSPs 2/1, DESCR: PVDMII DSP SIMM with four DSPs PID: AS5X-PVDM2-64 , VID: V01, SN: FOC163221VF NAME: PVDMII DSP SIMM with four DSPs 2/2, DESCR: PVDMII DSP SIMM with four DSPs PID: AS5X-PVDM2-64 , VID: V01, SN: FOC163221ZF NAME: PVDMII DSP SIMM with four DSPs 2/3, DESCR: PVDMII DSP SIMM with four DSPs PID: AS5X-PVDM2-64 , VID: V01, SN: FOC163221W1 NAME: PVDMII DSP SIMM with four DSPs 2/4, DESCR: PVDMII DSP SIMM with four DSPs PID: AS5X-PVDM2-64 , VID: V01, SN: FOC163221Q7 NAME: PVDMII DSP SIMM with four DSPs 2/5, DESCR: PVDMII DSP SIMM with four DSPs PID: AS5X-PVDM2-64 , VID: V01, SN: FOC163221ZW NAME: AS5X-FC_3, DESCR: AS5000 Feature Card with Six AS5X PVDM DSP Module Slots PID: AS5X-FC , VID: V01, SN: JAE16300812 NAME: PVDMII DSP SIMM with four DSPs 3/0, DESCR: PVDMII DSP SIMM with four DSPs PID: AS5X-PVDM2-64 , VID: V01, SN: FOC16322200 NAME: PVDMII DSP SIMM with four DSPs 3/1, DESCR: PVDMII DSP SIMM with four DSPs PID: AS5X-PVDM2-64 , VID: V01, SN: FOC1632220C NAME: PVDMII DSP SIMM with four DSPs 3/2, DESCR: PVDMII DSP SIMM with four DSPs PID: AS5X-PVDM2-64 , VID: V01, SN: FOC163221PN NAME: PVDMII DSP SIMM with four DSPs 3/3, DESCR: PVDMII DSP SIMM with four DSPs PID: AS5X-PVDM2-64 , VID: V01, SN: FOC163221VE NAME: PVDMII DSP SIMM with four DSPs 3/4, DESCR: PVDMII DSP SIMM with four DSPs PID: AS5X-PVDM2-64 , VID: V01, SN: FOC16322203 NAME: PVDMII DSP SIMM with four DSPs 3/5, DESCR: PVDMII DSP SIMM with four DSPs PID: AS5X-PVDM2-64 , VID: V01, SN: FOC1632220X NAME: AS5X-FC_4, DESCR: AS5000 Feature Card with Six AS5X PVDM DSP Module Slots PID: AS5X-FC , VID: V01, SN: JAE15400DKU NAME: PVDMII DSP SIMM with four DSPs 4/0, DESCR: PVDMII DSP SIMM with four DSPs PID: AS5X-PVDM2-64 , VID: V01, SN: FOC163221QK NAME: PVDMII DSP SIMM with four DSPs 4/1, DESCR: PVDMII DSP SIMM with four DSPs PID: AS5X-PVDM2-64 , VID: V01, SN: FOC163221YW NAME: PVDMII DSP SIMM with four DSPs 4/2, DESCR: PVDMII DSP SIMM with four DSPs PID: AS5X-PVDM2-64 , VID: V01, SN: FOC1632220Z NAME: PVDMII DSP SIMM with four DSPs 4/3, DESCR: PVDMII DSP SIMM with four DSPs PID: AS5X-PVDM2-64 , VID: V01, SN: FOC16322206 NAME: PVDMII DSP SIMM with four DSPs 4/4, DESCR: PVDMII DSP SIMM with four DSPs PID: AS5X-PVDM2-64 , VID: V01, SN: FOC163221ZB NAME: PVDMII DSP SIMM with four DSPs 4/5, DESCR: PVDMII DSP SIMM with four DSPs PID: AS5X-PVDM2-64 , VID: V01, SN: FOC163221ZV NAME: AS5X-FC_5, DESCR: AS5000 Feature Card with Six AS5X PVDM DSP Module Slots PID: AS5X-FC , VID: V01, SN: JAE162401C0 NAME: PVDMII DSP SIMM with four DSPs 5/0, DESCR: PVDMII DSP SIMM with four DSPs PID: AS5X-PVDM2-64 , VID: V01, SN: FOC163221VK NAME: PVDMII DSP SIMM with four DSPs 5/1, DESCR: PVDMII DSP SIMM with four DSPs PID: AS5X-PVDM2-64 , VID: V01, SN: FOC163221VA NAME: PVDMII DSP SIMM with four DSPs 5/2, DESCR: PVDMII DSP SIMM with four DSPs PID: AS5X-PVDM2-64 , VID: V01, SN: FOC163221Q6 NAME: PVDMII DSP SIMM with four DSPs 5/3, DESCR: PVDMII DSP SIMM with
Re: [cisco-voip] tokenless CTL client - how to move devices between mixed mode clusters?
The tokenless CTL is signed by the CallManager.pem on the publisher. Upload that cert as a phone-trust cert and TVS on that cluster will be able to authenticate files signed by that cert. CTL Record #:1 BYTEPOS TAG LENGTH VALUE --- --- -- - 1 RECORDLENGTH 2 1701 2 DNSNAME 20 videolab-ucm11a-pub 3 SUBJECTNAME 70 CN=videolab-ucm11a-pub.videolab.local;OU=TAC;O=Cisco;L=NC;ST=RTP;C=US 4 FUNCTION 2 System Administrator Security Token 5 ISSUERNAME 70 CN=videolab-ucm11a-pub.videolab.local;OU=TAC;O=Cisco;L=NC;ST=RTP;C=US 6 SERIALNUMBER 16 52:0B:74:69:CF:4F:5A:CD:5B:48:6F:EE:99:9E:E0:B8 7 PUBLICKEY 270 8 SIGNATURE 256 9 CERTIFICATE 961 76 5D 15 01 0E 41 0D 16 BE EA 8A 98 29 33 EE 27 B6 3E D3 01 (SHA1 Hash HEX) 10 IPADDRESS 4 This etoken was used to sign the CTL file. admin:show cert own CallManager/CallManager.pem [ Version: V3 Serial Number: 520B7469CF4F5ACD5B486FEE999EE0B8 … - Ryan On Aug 12, 2015, at 9:06 PM, Dave Goodwin dave.good...@december.netmailto:dave.good...@december.net wrote: For anyone who has an environment with multiple mixed mode clusters (CTL file is present), do you know of a way to move devices from one cluster to another? Using the eToken SAST (physical USB devices), it seems you can do this by using the same signing token to sign the CTL file on each cluster. With the new tokenless CTL client, it seems each cluster's publisher private key is used to sign that cluster's CTL file - so it seems the old way will not work. I realize it can be done by deleting the CTL file on the phone (or factory reset) if you're standing in front of it, and I also realize there are commercial software tools that can perform feats like this (like UnifiedFX and other competitive offerings). I am looking for a way to do this without either of those methods. -Dave ___ cisco-voip mailing list cisco-voip@puck.nether.netmailto:cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip ___ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
Re: [cisco-voip] tokenless CTL client - how to move devices between mixed mode clusters?
Ryan, let me lay out an example to make sure I understand. Please note that I haven't found anywhere that this has been well-explained, so I am laying out the following logic flow as a guess. Hopefully it's at least close; please set me straight. Say we have an old cluster and a new cluster, and that I want to move phones registered to the old cluster to instead register to the new cluster. Are you saying: 1. Download the CallManager.pem from new cluster pub and upload that cert as phone-trust to the old cluster. This will enable the old cluster TVS to have TVS-aware phones trust the new cluster. 2. When the phone is told (say, via change in DHCP option 150 value) to register to the new cluster, it will fail to authenticate the new cluster's CTL file due to a different file signer. 3. So, the phone will then connect with its already-trusted TVS server in the old cluster. At this point, since the new cluster pub cert was added as phone-trust in the old cluster, TVS will instruct the phone to trust the cert. 4. Then, based on TVS's go-ahead, the phone will now load and install the new cluster CTL file. 5. At this stage, the phone will trust only the entries in the new cluster CTL file - and also any certs that the new cluster's TVS can trust. Also, it seems like this procedure would also work with the token-based CTL client, as long as TVS is present and all the moving endpoints support TVS. -Dave On Wed, Aug 12, 2015 at 10:45 PM, Brian Meade bmead...@vt.edu wrote: Ryan, would you need to add the other cluster in the TFTP server list? I know I usually had to do this with the actual CTL client but not sure how this would work in tokenless unless there's a CLI command for it. On Wed, Aug 12, 2015 at 10:03 PM, Ryan Ratliff (rratliff) rratl...@cisco.com wrote: The tokenless CTL is signed by the CallManager.pem on the publisher. Upload that cert as a phone-trust cert and TVS on that cluster will be able to authenticate files signed by that cert. CTL Record #:1 BYTEPOS TAG LENGTH VALUE --- --- -- - 1 RECORDLENGTH 2 1701 2 DNSNAME 20 videolab-ucm11a-pub 3 SUBJECTNAME 70 CN=videolab-ucm11a-pub.videolab.local;OU=TAC;O=Cisco;L=NC;ST=RTP;C=US 4 FUNCTION 2 System Administrator Security Token 5 ISSUERNAME 70 CN=videolab-ucm11a-pub.videolab.local;OU=TAC;O=Cisco;L=NC;ST=RTP;C=US 6 SERIALNUMBER 16 52:0B:74:69:CF:4F:5A:CD:5B:48:6F:EE:99:9E:E0:B8 7 PUBLICKEY 270 8 SIGNATURE 256 9 CERTIFICATE 961 76 5D 15 01 0E 41 0D 16 BE EA 8A 98 29 33 EE 27 B6 3E D3 01 (SHA1 Hash HEX) 10 IPADDRESS 4 This etoken was used to sign the CTL file. admin:show cert own CallManager/CallManager.pem [ Version: V3 Serial Number: 520B7469CF4F5ACD5B486FEE999EE0B8 … - Ryan On Aug 12, 2015, at 9:06 PM, Dave Goodwin dave.good...@december.net wrote: For anyone who has an environment with multiple mixed mode clusters (CTL file is present), do you know of a way to move devices from one cluster to another? Using the eToken SAST (physical USB devices), it seems you can do this by using the same signing token to sign the CTL file on each cluster. With the new tokenless CTL client, it seems each cluster's publisher private key is used to sign that cluster's CTL file - so it seems the old way will not work. I realize it can be done by deleting the CTL file on the phone (or factory reset) if you're standing in front of it, and I also realize there are commercial software tools that can perform feats like this (like UnifiedFX and other competitive offerings). I am looking for a way to do this without either of those methods. -Dave ___ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip ___ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip ___ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
Re: [cisco-voip] configure Transcoders in AS5400XM router...
No Sir. dsp? command is even not available under 7 voice-cards. MAK COL2VG3(config)#voice-card 1 COL2VG3(config-voicecard)#dspf COL2VG3(config-voicecard)#dsp? % Unrecognized command Do you have dsp services dspfarm configured under the voice-cards? On Wed, Aug 12, 2015 at 5:18 PM, Mudassar M via cisco-voip cisco-voip at puck.nether.net wrote: Hello folks, trying to configure 5400 router as my media resource box for transcoders and conference bridges but unable to find sccp, dsp commands etc. IOS version is c5400-ik9s-mz.151-3.T4.bin and inventory is listed down. any one has idea about how to configure these PVDMS in 5400? Thanks for your help, MAK KKVG1#show inventory NAME: AS5400XM chassis, DESCR: AS5400XM chassis PID: AS5400XM , VID: V05, SN: JAE162603MG NAME: AS5X-FC_1, DESCR: AS5000 Feature Card with Six AS5X PVDM DSP Module Slots PID: AS5X-FC , VID: V01, SN: JAE163007ZF NAME: PVDMII DSP SIMM with four DSPs 1/0, DESCR: PVDMII DSP SIMM with four DSPs PID: AS5X-PVDM2-64 , VID: V01, SN: FOC163221YC NAME: PVDMII DSP SIMM with four DSPs 1/1, DESCR: PVDMII DSP SIMM with four DSPs PID: AS5X-PVDM2-64 , VID: V01, SN: FOC163221Z6 NAME: PVDMII DSP SIMM with four DSPs 1/2, DESCR: PVDMII DSP SIMM with four DSPs PID: AS5X-PVDM2-64 , VID: V01, SN: FOC163221VH NAME: PVDMII DSP SIMM with four DSPs 1/3, DESCR: PVDMII DSP SIMM with four DSPs PID: AS5X-PVDM2-64 , VID: V01, SN: FOC163221Y7 NAME: PVDMII DSP SIMM with four DSPs 1/4, DESCR: PVDMII DSP SIMM with four DSPs PID: AS5X-PVDM2-64 , VID: V01, SN: FOC163221PH NAME: PVDMII DSP SIMM with four DSPs 1/5, DESCR: PVDMII DSP SIMM with four DSPs PID: AS5X-PVDM2-64 , VID: V01, SN: FOC1632220Q NAME: AS5X-FC_2, DESCR: AS5000 Feature Card with Six AS5X PVDM DSP Module Slots PID: AS5X-FC , VID: V01, SN: JAE163007ZD NAME: PVDMII DSP SIMM with four DSPs 2/0, DESCR: PVDMII DSP SIMM with four DSPs PID: AS5X-PVDM2-64 , VID: V01, SN: FOC163221Z7 NAME: PVDMII DSP SIMM with four DSPs 2/1, DESCR: PVDMII DSP SIMM with four DSPs PID: AS5X-PVDM2-64 , VID: V01, SN: FOC163221VF NAME: PVDMII DSP SIMM with four DSPs 2/2, DESCR: PVDMII DSP SIMM with four DSPs PID: AS5X-PVDM2-64 , VID: V01, SN: FOC163221ZF NAME: PVDMII DSP SIMM with four DSPs 2/3, DESCR: PVDMII DSP SIMM with four DSPs PID: AS5X-PVDM2-64 , VID: V01, SN: FOC163221W1 NAME: PVDMII DSP SIMM with four DSPs 2/4, DESCR: PVDMII DSP SIMM with four DSPs PID: AS5X-PVDM2-64 , VID: V01, SN: FOC163221Q7 NAME: PVDMII DSP SIMM with four DSPs 2/5, DESCR: PVDMII DSP SIMM with four DSPs PID: AS5X-PVDM2-64 , VID: V01, SN: FOC163221ZW NAME: AS5X-FC_3, DESCR: AS5000 Feature Card with Six AS5X PVDM DSP Module Slots PID: AS5X-FC , VID: V01, SN: JAE16300812 NAME: PVDMII DSP SIMM with four DSPs 3/0, DESCR: PVDMII DSP SIMM with four DSPs PID: AS5X-PVDM2-64 , VID: V01, SN: FOC16322200 NAME: PVDMII DSP SIMM with four DSPs 3/1, DESCR: PVDMII DSP SIMM with four DSPs PID: AS5X-PVDM2-64 , VID: V01, SN: FOC1632220C NAME: PVDMII DSP SIMM with four DSPs 3/2, DESCR: PVDMII DSP SIMM with four DSPs PID: AS5X-PVDM2-64 , VID: V01, SN: FOC163221PN NAME: PVDMII DSP SIMM with four DSPs 3/3, DESCR: PVDMII DSP SIMM with four DSPs PID: AS5X-PVDM2-64 , VID: V01, SN: FOC163221VE NAME: PVDMII DSP SIMM with four DSPs 3/4, DESCR: PVDMII DSP SIMM with four DSPs PID: AS5X-PVDM2-64 , VID: V01, SN: FOC16322203 NAME: PVDMII DSP SIMM with four DSPs 3/5, DESCR: PVDMII DSP SIMM with four DSPs PID: AS5X-PVDM2-64 , VID: V01, SN: FOC1632220X NAME: AS5X-FC_4, DESCR: AS5000 Feature Card with Six AS5X PVDM DSP Module Slots PID: AS5X-FC , VID: V01, SN: JAE15400DKU NAME: PVDMII DSP SIMM with four DSPs 4/0, DESCR: PVDMII DSP SIMM with four DSPs PID: AS5X-PVDM2-64 , VID: V01, SN: FOC163221QK NAME: PVDMII DSP SIMM with four DSPs 4/1, DESCR: PVDMII DSP SIMM with four DSPs PID: AS5X-PVDM2-64 , VID: V01, SN: FOC163221YW NAME: PVDMII DSP SIMM with four DSPs 4/2, DESCR: PVDMII DSP SIMM with four DSPs PID: AS5X-PVDM2-64 , VID: V01, SN: FOC1632220Z NAME: PVDMII DSP SIMM with four DSPs 4/3, DESCR: PVDMII DSP SIMM with four DSPs PID: AS5X-PVDM2-64 , VID: V01, SN: FOC16322206 NAME: PVDMII DSP SIMM with four DSPs 4/4, DESCR: PVDMII DSP SIMM with four DSPs PID: AS5X-PVDM2-64 , VID: V01, SN: FOC163221ZB NAME: PVDMII DSP SIMM with four DSPs 4/5, DESCR: PVDMII DSP SIMM with four DSPs PID: AS5X-PVDM2-64 , VID: V01, SN: FOC163221ZV NAME: AS5X-FC_5, DESCR: AS5000 Feature Card with Six AS5X PVDM DSP Module Slots PID: AS5X-FC , VID: V01, SN: JAE162401C0 NAME: PVDMII DSP SIMM with four DSPs 5/0, DESCR: PVDMII DSP SIMM with four DSPs PID: AS5X-PVDM2-64 , VID: V01, SN: FOC163221VK NAME: PVDMII DSP SIMM with four DSPs 5/1, DESCR: PVDMII DSP SIMM with four DSPs PID: AS5X-PVDM2-64 , VID: V01, SN: FOC163221VA NAME: PVDMII DSP
[cisco-voip] tokenless CTL client - how to move devices between mixed mode clusters?
For anyone who has an environment with multiple mixed mode clusters (CTL file is present), do you know of a way to move devices from one cluster to another? Using the eToken SAST (physical USB devices), it seems you can do this by using the same signing token to sign the CTL file on each cluster. With the new tokenless CTL client, it seems each cluster's publisher private key is used to sign that cluster's CTL file - so it seems the old way will not work. I realize it can be done by deleting the CTL file on the phone (or factory reset) if you're standing in front of it, and I also realize there are commercial software tools that can perform feats like this (like UnifiedFX and other competitive offerings). I am looking for a way to do this without either of those methods. -Dave ___ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
Re: [cisco-voip] tokenless CTL client - how to move devices between mixed mode clusters?
Ryan, would you need to add the other cluster in the TFTP server list? I know I usually had to do this with the actual CTL client but not sure how this would work in tokenless unless there's a CLI command for it. On Wed, Aug 12, 2015 at 10:03 PM, Ryan Ratliff (rratliff) rratl...@cisco.com wrote: The tokenless CTL is signed by the CallManager.pem on the publisher. Upload that cert as a phone-trust cert and TVS on that cluster will be able to authenticate files signed by that cert. CTL Record #:1 BYTEPOS TAG LENGTH VALUE --- --- -- - 1 RECORDLENGTH 2 1701 2 DNSNAME 20 videolab-ucm11a-pub 3 SUBJECTNAME 70 CN=videolab-ucm11a-pub.videolab.local;OU=TAC;O=Cisco;L=NC;ST=RTP;C=US 4 FUNCTION 2 System Administrator Security Token 5 ISSUERNAME 70 CN=videolab-ucm11a-pub.videolab.local;OU=TAC;O=Cisco;L=NC;ST=RTP;C=US 6 SERIALNUMBER 16 52:0B:74:69:CF:4F:5A:CD:5B:48:6F:EE:99:9E:E0:B8 7 PUBLICKEY 270 8 SIGNATURE 256 9 CERTIFICATE 961 76 5D 15 01 0E 41 0D 16 BE EA 8A 98 29 33 EE 27 B6 3E D3 01 (SHA1 Hash HEX) 10 IPADDRESS 4 This etoken was used to sign the CTL file. admin:show cert own CallManager/CallManager.pem [ Version: V3 Serial Number: 520B7469CF4F5ACD5B486FEE999EE0B8 … - Ryan On Aug 12, 2015, at 9:06 PM, Dave Goodwin dave.good...@december.net wrote: For anyone who has an environment with multiple mixed mode clusters (CTL file is present), do you know of a way to move devices from one cluster to another? Using the eToken SAST (physical USB devices), it seems you can do this by using the same signing token to sign the CTL file on each cluster. With the new tokenless CTL client, it seems each cluster's publisher private key is used to sign that cluster's CTL file - so it seems the old way will not work. I realize it can be done by deleting the CTL file on the phone (or factory reset) if you're standing in front of it, and I also realize there are commercial software tools that can perform feats like this (like UnifiedFX and other competitive offerings). I am looking for a way to do this without either of those methods. -Dave ___ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip ___ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip ___ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
[cisco-voip] CDR Load issue in 10.5(1)
Has anyone seen where CDR files stop loading in 10.5(1)? CDR Search web page showed no calls for the day and the reports for past days were not showing calls either. The CDR files were there and showed processed at the CLI in the processed folder. I disabled the CDR loader under CDR Scheduler in the CAR Web admin and re-enabled it and it corrected the issues. Not finding any bugs for this yet either. ___ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
Re: [cisco-voip] TAC Hot Issues RSS Feed?
Nothing since Sept ish You think they would have published via RSS that it was being discontinued in advanced vs going dark :) From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of Erick Bergquist Sent: Wednesday, August 12, 2015 1:41 PM To: voip puck cisco-voip@puck.nether.net Subject: [cisco-voip] TAC Hot Issues RSS Feed? Does anyone know if the TAC hot issues feed is active still? Have not seen much activity there in some time. Regards, Erick ___ cisco-voip mailing list cisco-voip@puck.nether.netmailto:cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip itevomcid ___ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
[cisco-voip] TAC Hot Issues RSS Feed?
Does anyone know if the TAC hot issues feed is active still? Have not seen much activity there in some time. Regards, Erick ___ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
