Hi Rynard The phones are 7942?
If you reboot the gw the phones can register and then loose again the registration? Regards Chrysostomos -----Original Message----- From: ccie_voice-boun...@onlinestudylist.com [mailto:ccie_voice-boun...@onlinestudylist.com] On Behalf Of Rynard Coetzee Sent: Παρασκευή, 28 Σεπτεμβρίου 2012 9:48 πμ To: michael.se...@compucom.com; ccie_voice@onlinestudylist.com Subject: Re: [OSL | CCIE_Voice] CUCME in SRST mode IOS Version 15 / Toll Fraud Prevention. Hi Michael Yes ,I know about the Trust list on the routers ,my problem is that the SNAP protocol does not build the Ephone-dn`s of the phones when the site falls into SRST mode ,even though I have set to auto provision all. So one of the phones actually registers to GW but without a DN and the other phone does not even register ,but I have found this to be a problem in the phones config file. Thanks -----Original Message----- From: michael.se...@compucom.com [mailto:michael.se...@compucom.com] Sent: 28 September 2012 04:58 AM To: ccie_voice@onlinestudylist.com Cc: Rynard Coetzee Subject: CUCME in SRST mode IOS Version 15 / Toll Fraud Prevention. Raynard, http://www.cisco.com/en/US/docs/voice_ip_comm/cusrst/feature/guide/srst8_1.html I recently had a client that upgraded all their routers to 3900's Series routers and along with that of course 15.x code. SRST in original configuration stopped working with the 15.x code. We were seeing debugs similar to these and others (debug voice ccapi inout): *Aug 14 19:54:32.507: %VOICE_IEC-3-GW: Application Framework Core: Internal Error (Toll fraud call rejected): IEC=1.1.228.3.31.0 on callID 3 GUID=AE5066C5883E11DE8026A96657501A09. Cisco now enables IP Address Trusted Authentication by default. This was in an environment where two routers were being used as SRST gateways with crossbar H323 voip route between the routers in this MGCP to accommodate cross router calling while in SRST. The following configuration resolved our issue. voice service voip ip address trusted list ipv4 172.19.245.1 ipv4 172.19.247.1 ipv4 172.19.243.1 ipv4 171.19.245.1 ipv4 171.19.10.1 allow-connections h323 to h323 allow-connections h323 to sip allow-connections sip to h323 allow-connections sip to sip Adding trusted lists in this scenario resolved our SRST problem. No configuration changes were made with the exception of add the trusted list, in this case, we added all IP Interfaces to the trusted list on each router including the loopbacks. Hope this helps. Michael Sears _______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com Are you a CCNP or CCIE and looking for a job? Check out www.PlatinumPlacement.com _______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com Are you a CCNP or CCIE and looking for a job? Check out www.PlatinumPlacement.com
