Please what is the difference between term06 file and cmterm files? Please help.
On Mon, Jan 26, 2015 at 6:00 PM, <cisco-voip-requ...@puck.nether.net> wrote: > Send cisco-voip mailing list submissions to > cisco-voip@puck.nether.net > > To subscribe or unsubscribe via the World Wide Web, visit > https://puck.nether.net/mailman/listinfo/cisco-voip > or, via email, send a message with subject or body 'help' to > cisco-voip-requ...@puck.nether.net > > You can reach the person managing the list at > cisco-voip-ow...@puck.nether.net > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of cisco-voip digest..." > > > Today's Topics: > > 1. Re: RTMT logs for disconnect signal of RCC (Rajamani N) > 2. UCM - CUBE trusted IP address (Reto Gassmann) > 3. Re: UCM - CUBE trusted IP address (Anthony Holloway) > 4. Re: UCM - CUBE trusted IP address (Jorge L. Rodriguez Aguila) > 5. Re: UCM - CUBE trusted IP address (Daniel Pagan) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 26 Jan 2015 17:01:28 +0530 > From: Rajamani N <rajaman...@gmail.com> > To: Brian Meade <bmead...@vt.edu> > Cc: cisco-voip voyp list <cisco-voip@puck.nether.net> > Subject: Re: [cisco-voip] RTMT logs for disconnect signal of RCC > Message-ID: > <CANW=gO3FBT52_Ez4-4hs1Ga_RN= > ve-hhfanxmmfyqrmsfc+...@mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Please do look into the SIP Proxy logs from the CUPS, you can see the CSTA > events for RCC in them > > -Rajamani > > On Sat, Jan 24, 2015 at 2:45 AM, Brian Meade <bmead...@vt.edu> wrote: > > > 9.x has the interleaved traces as well. > > > > On Fri, Jan 23, 2015 at 4:10 PM, Ryan Ratliff (rratliff) < > > rratl...@cisco.com> wrote: > > > >> For an SCCP phone you'll see a StationInit from CCM to the phone > >> instructing the phone to go OnHook. Using SDL traces you can follow > that > >> back to where it originated from, which will likely be CTI if I recall > how > >> RCC works correctly. > >> This tracking is much easier in 10.x with interleaved traces. > >> > >> -Ryan > >> > >> On Jan 23, 2015, at 6:55 AM, Jefflin Choi <jefflin.c...@gmail.com> > wrote: > >> > >> All, > >> > >> We have lync remote call control integrated on our CCM/CUPS system. I'm > >> troubleshooting some call disconnect issues basically. > >> > >> Does anyone know which criteria to look for if it's caused by the lync > >> RCC on CCM and CUPS traces? > >> > >> If it's SIP phone, 9951 did saw one time with SIP REFER Message to the > >> phone to disconnect on CCM traces though not sure if this is also the > case > >> with SCCP phones. > >> Softkey event does show me if it was an end call press but i don't think > >> this applies if it was triggered by closing the call dialog box on lync. > >> > >> What's the normal logging trace configuration that needs to be enabled > >> also? > >> > >> TIA, > >> Jeff > >> > >> > >> _______________________________________________ > >> 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 > > > > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: < > https://puck.nether.net/pipermail/cisco-voip/attachments/20150126/4857eb9a/attachment-0001.html > > > > ------------------------------ > > Message: 2 > Date: Mon, 26 Jan 2015 13:23:43 +0100 > From: Reto Gassmann <v...@mrga.ch> > To: cisco-voip@puck.nether.net > Subject: [cisco-voip] UCM - CUBE trusted IP address > Message-ID: > <CAL4H0Z6tjeSL53W6Vd-E7TG77pjpwzXR7kbr_RF-vF= > 9ff+...@mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Hello Group > > we run a CUCM Cluster 9.1(2) with a SIP Trunk (CUBE) to our telephony > provider. > Our cluster has 8 Servers (1 Pub / 7 Sub). > On the CUBE we have three dialpeers pointing to three different subs for > redundancy: > > dial-peer voice 1000 voip > destination-pattern > session target ipv4: Server5 > > dial-peer voice 1001 voip > destination-pattern > session target ipv4: Server4 > > dial-peer voice 1002 voip > destination-pattern > session target ipv4: Server3 > > On the UCM we have a SIP Trunk configured with a device that contains > Server3, Server4 and Server5 in its CUCM Group. > All IP Phones register to Server4 or Server5. > > We now have the problem that Server4 has sometimes a pretty high CPU load > (Code yellow). > > I want to change the dialpeers on the CUBE so that they point to Server7 > and Server8 to reduce the load on Server4. > > What do we have to change on the UCM if we change the dial-peer voice 1000 > and 1001 on the CUBE to > dial-peer voice 1000 voip > destination-pattern > session target ipv4: Server7 > > dial-peer voice 1001 voip > destination-pattern > session target ipv4: Server8 > > Thanks a lot > Regards Reto > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: < > https://puck.nether.net/pipermail/cisco-voip/attachments/20150126/ff3cf5c9/attachment-0001.html > > > > ------------------------------ > > Message: 3 > Date: Mon, 26 Jan 2015 15:15:56 +0000 > From: Anthony Holloway <avholloway+cisco-v...@gmail.com> > To: Reto Gassmann <v...@mrga.ch>, cisco-voip@puck.nether.net > Subject: Re: [cisco-voip] UCM - CUBE trusted IP address > Message-ID: > <CACRCJOiPndJK0JYqfFC-kqs9B3rKc5QWHEaRRxfGqjwa=_ > j...@mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > It depends on whether or not you are using run on all nodes, where your > endpoints are registered, how you plan on taking server4 out of service, > etc. > > Your best bet is to put all CPE IP Addresses into the trusted list so you > will not have any toll fraud blocking going on when you change your SIP > trunk CMG. Assuming you're not using run on all nodes; which you probably > should be, for the route local benefit. > > On Mon Jan 26 2015 at 6:29:31 AM Reto Gassmann <v...@mrga.ch> wrote: > > > Hello Group > > > > we run a CUCM Cluster 9.1(2) with a SIP Trunk (CUBE) to our telephony > > provider. > > Our cluster has 8 Servers (1 Pub / 7 Sub). > > On the CUBE we have three dialpeers pointing to three different subs for > > redundancy: > > > > dial-peer voice 1000 voip > > destination-pattern > > session target ipv4: Server5 > > > > dial-peer voice 1001 voip > > destination-pattern > > session target ipv4: Server4 > > > > dial-peer voice 1002 voip > > destination-pattern > > session target ipv4: Server3 > > > > On the UCM we have a SIP Trunk configured with a device that contains > > Server3, Server4 and Server5 in its CUCM Group. > > All IP Phones register to Server4 or Server5. > > > > We now have the problem that Server4 has sometimes a pretty high CPU load > > (Code yellow). > > > > I want to change the dialpeers on the CUBE so that they point to Server7 > > and Server8 to reduce the load on Server4. > > > > What do we have to change on the UCM if we change the dial-peer voice > 1000 > > and 1001 on the CUBE to > > dial-peer voice 1000 voip > > destination-pattern > > session target ipv4: Server7 > > > > dial-peer voice 1001 voip > > destination-pattern > > session target ipv4: Server8 > > > > Thanks a lot > > Regards Reto > > > > > > _______________________________________________ > > cisco-voip mailing list > > cisco-voip@puck.nether.net > > https://puck.nether.net/mailman/listinfo/cisco-voip > > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: < > https://puck.nether.net/pipermail/cisco-voip/attachments/20150126/60a99987/attachment-0001.html > > > > ------------------------------ > > Message: 4 > Date: Mon, 26 Jan 2015 14:47:04 +0000 > From: "Jorge L. Rodriguez Aguila" <jorge.rodrig...@netxar.com> > To: Reto Gassmann <v...@mrga.ch> > Cc: Cisco-Voip <cisco-voip@puck.nether.net> > Subject: Re: [cisco-voip] UCM - CUBE trusted IP address > Message-ID: > <becd247fb55fa346bafc0e946fc848d29163d...@nx-colo-exch.netxar.com> > Content-Type: text/plain; charset="us-ascii" > > nothing for inbound > > Jorge Rodriguez, CCNP, CCNP-V > Senior Voice/Data Network Consultant > Netxar Technologies, a Digicel Company > Cel 7876888530 > Office 7877650058 > jorge.rodrig...@netxar.com<mailto:jorge.rodrig...@netxar.com> > > > > > On Jan 26, 2015, at 8:23 AM, Reto Gassmann <v...@mrga.ch<mailto: > v...@mrga.ch>> wrote: > > Hello Group > > we run a CUCM Cluster 9.1(2) with a SIP Trunk (CUBE) to our telephony > provider. > Our cluster has 8 Servers (1 Pub / 7 Sub). > On the CUBE we have three dialpeers pointing to three different subs for > redundancy: > > dial-peer voice 1000 voip > destination-pattern > session target ipv4: Server5 > > dial-peer voice 1001 voip > destination-pattern > session target ipv4: Server4 > > dial-peer voice 1002 voip > destination-pattern > session target ipv4: Server3 > > On the UCM we have a SIP Trunk configured with a device that contains > Server3, Server4 and Server5 in its CUCM Group. > All IP Phones register to Server4 or Server5. > > We now have the problem that Server4 has sometimes a pretty high CPU load > (Code yellow). > > I want to change the dialpeers on the CUBE so that they point to Server7 > and Server8 to reduce the load on Server4. > > What do we have to change on the UCM if we change the dial-peer voice 1000 > and 1001 on the CUBE to > dial-peer voice 1000 voip > destination-pattern > session target ipv4: Server7 > > dial-peer voice 1001 voip > destination-pattern > session target ipv4: Server8 > > Thanks a lot > Regards Reto > > > _______________________________________________ > cisco-voip mailing list > cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net> > https://puck.nether.net/mailman/listinfo/cisco-voip > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: < > https://puck.nether.net/pipermail/cisco-voip/attachments/20150126/89496eb3/attachment-0001.html > > > > ------------------------------ > > Message: 5 > Date: Mon, 26 Jan 2015 15:39:37 +0000 > From: Daniel Pagan <dpa...@fidelus.com> > To: "Jorge L. Rodriguez Aguila" <jorge.rodrig...@netxar.com>, Reto > Gassmann <v...@mrga.ch> > Cc: Cisco-Voip <cisco-voip@puck.nether.net> > Subject: Re: [cisco-voip] UCM - CUBE trusted IP address > Message-ID: > <c381847ff7df41f4bc101fced8701...@nyc-ex2k13-mb.fidelus.com> > Content-Type: text/plain; charset="windows-1252" > > Two options... > > 1. Ensure the two nodes (7 and 8) are in the CCM Group contained in > the assigned DP on this trunk. > > Or > > > 2. Enable it to run on all active nodes. > > Either way would allow the SIP daemon for this trunk to run on Server7 and > Server8, which is essentially what's needed. > > In this scenario I see nothing wrong with turning this on, but I'd be > careful if enabling this between UCM and 3rd party PBXs or applications > where only a limited number of SIP UA entries can be defined... can lead to > a situation where a SIP call is sourced from a CUCM node that's not defined > at the remote side, leading to call failure. Aside from that, for inbound > calls, the call will be rejected if the SIP INVITE is sent to a CUCM node > not running the SIP daemon for this trunk. For outbound, the SIP INVITE > should source from the node where the Route List used for the call is > registered (assuming #1 or #2 above is correct). > > - Dan > > From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of > Jorge L. Rodriguez Aguila > Sent: Monday, January 26, 2015 9:47 AM > To: Reto Gassmann > Cc: Cisco-Voip > Subject: Re: [cisco-voip] UCM - CUBE trusted IP address > > nothing for inbound > > Jorge Rodriguez, CCNP, CCNP-V > Senior Voice/Data Network Consultant > Netxar Technologies, a Digicel Company > Cel 7876888530 > Office 7877650058 > jorge.rodrig...@netxar.com<mailto:jorge.rodrig...@netxar.com> > > > > On Jan 26, 2015, at 8:23 AM, Reto Gassmann <v...@mrga.ch<mailto: > v...@mrga.ch>> wrote: > > Hello Group > > we run a CUCM Cluster 9.1(2) with a SIP Trunk (CUBE) to our telephony > provider. > Our cluster has 8 Servers (1 Pub / 7 Sub). > On the CUBE we have three dialpeers pointing to three different subs for > redundancy: > > dial-peer voice 1000 voip > destination-pattern > session target ipv4: Server5 > > dial-peer voice 1001 voip > destination-pattern > session target ipv4: Server4 > > > dial-peer voice 1002 voip > destination-pattern > session target ipv4: Server3 > > > On the UCM we have a SIP Trunk configured with a device that contains > Server3, Server4 and Server5 in its CUCM Group. > All IP Phones register to Server4 or Server5. > > > We now have the problem that Server4 has sometimes a pretty high CPU load > (Code yellow). > > > I want to change the dialpeers on the CUBE so that they point to Server7 > and Server8 to reduce the load on Server4. > > What do we have to change on the UCM if we change the dial-peer voice 1000 > and 1001 on the CUBE to > dial-peer voice 1000 voip > destination-pattern > session target ipv4: Server7 > > > dial-peer voice 1001 voip > destination-pattern > session target ipv4: Server8 > > > Thanks a lot > Regards Reto > > > > > _______________________________________________ > cisco-voip mailing list > cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net> > https://puck.nether.net/mailman/listinfo/cisco-voip > > > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: < > https://puck.nether.net/pipermail/cisco-voip/attachments/20150126/7189425f/attachment-0001.html > > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > cisco-voip mailing list > cisco-voip@puck.nether.net > https://puck.nether.net/mailman/listinfo/cisco-voip > > > ------------------------------ > > End of cisco-voip Digest, Vol 135, Issue 21 > ******************************************* > -- Eteng Okoi Network Engineer Cell: 234(703)4153530 Ext:2601 E-mail: eteng.o...@unicem.com.ng Website: www.unicem.com.ng -- If you are not the intended recipient and have received this e-mail in error, please delete it immediately from your system and notify the sender by e-mail or telephone. Be notified that you are not to copy, distribute or disclose this e-mail or any of its contents to any other party and any such action may be unlawful.
_______________________________________________ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip