CSCtx91035 - ATA 187 unregister from CUCM for branch offices

This bug concerns the ATA 187. Fixed release should be 9.2(3)SR1 BUT not available for ATA 187 (Cisco IP Phone 6900 series !???).
We have the same problem here with our client in Belgium. When is the fixed release available for the ATA 187 please ?
Thanks in advance.
Best regards
Mike

Hey Mike,
Great Question. This bug has actually already been fixed.
The fixed release 9.2(3)SR1 is only available through TAC. You would have to open a case via phone or visit cisco.com.
Other known Bugs that you could ask TAC about are:
CSCtz22064 - ATA-187 hear Ring Back Tone with Directed Call Park unexpectedly
CSCtq85079 - ATA187 will crash if port2 keeps tftp downloading
CSCua01061 - ATA187 reset when there're mutiple ARP Reply
CSCua51467 - ATA187 memory leak
CSCty43474 - ATA 187 Allows telnet access on port 32000
CSCtz67038 - Cisco ATA 187 Analog Telephone Adaptor Remote Access Vulnerability
CSCub39248 - ATA 187 is not obtaining IP address from VLAN configured on its Eth port
CSCuc82525 - ATA187 units requires a reload to regain connectivity to CUCM
CSCuc14110 - ATA187 Sends empty SIP packet causing SIP ALG problems
CSCud88926 - ATA 187 provides its uptime instead of local time to analog phones.
CSCud74510 - Non secure ATA 187 not registering to SRST, if secure SRST checked
CSCuh49249 - ATA-187 Crashes in SRST mode when called via ISDN BRI
CSCuj59548 - ATA 187 don't honor configured Renewal(T1)
I hope this helps!

Similar Messages

  • Cisco ATA 187 - will unregister from CUCM 10.5

    Hello,
    I've got some problems with my Cisco ATA 187. They keep unregistering from time to time. If you shutdown the Interface on the switch and no shut, it gets registered just straight away. According to cdp the device is pingable all the time, just the registration with the callmanager seems to be a problem.
    Versions are:
    App Load ID       APP187.9-2-3-1
    Boot Load ID      1.8.0.6
    SW_Version ID     187.9-2-3-1
    External Engineer told me that this series contains some kind of bug, but if I'll assign/configure the 2nd Port on that one, it shouldn't hung up. I've also tried this but without success.
    Any ideas? :)
    Thanks and regards
    Marc

    Marc,
    Yes the ATA 187 has always been a problem. I have had it doing the same thing with different versions of the Call Manager (starting 8.5). Anyways the only thing that made it bit stable for me has been to try and change the firmware. You can try to upgrade/downgrade the firmware on any one device that is having this issues and test if it makes any difference at all.
    You can also search this forum it should come up with quite a number of threads on this.
    -Terry

  • To make a new site or not? (for branch office with small number of people)

    We have a main office, with our DC (DC01) and a single site (SiteHO), and we are about to open up a new branch office in another city.  This branch office is connected to the head office via a 5 Mbps MPLS network.  The branch office will have around
    5-7 domain joined workstations, and the people there will require access to the existing file and exchange servers in the head office. 
    I was thinking about not adding a RODC in the branch office and not creating another site in AD for the branch office either.  My thinking is that since the number of users is relatively low, it doesn't warrant having a new RODC and site.  The
    traffic generated by the 5-7 user logon activities will be minimal, and the local profiles are stored on the workstations (no roaming profiles), so there shouldn't be much WAN link impact.  Obviously I would have to add the subnet from the branch office
    to the SiteHO site. 
    Can anybody think of something wrong with my reasoning?

    I think the dedicated line has a little to do with AD since its used both to authenticate the users and move the data.
    I am not sure what bandwith you get from an internet provider in your location, but for example you might get a 100Mb internet connection from an ISP. A VPN tunnel over a 100Mb internet connection I am guessing is faster then a 5Mb guaranteed MPLS link.
    The advantage of MPLS is that you can have QoS policies for voice and video traffic.
    If users move 'very large files' perhaps a local file server might be an good option. DFS replication can save a lot of bandwidth in that case. And then you would have 'local resources' in the branch and in case of wan failure the users will not be able
    to access the local file server resource. So you would need a secondary DC in that location.
    And if they are moving the files think (and check) the impact on the MPLS, because authentication requests go through that link, Exchange traffic (RPC MAPI) goes through that link so these might be affected. For example, lets say you have 2GB mailboxes.
    All Outlook users use OST files. One user's profile gets corrupted and needs to be rebuilt. The Outlook client sets up a fresh OST copy of the mailbox so now its downloading a 2GB mailbox copy over a 5Mb MPLS while some other user is moving a 'large file'.
    By local resources I am referring to file servers, printers, applications in the branch location that require AD authentication. Authentication works with both VPN and MPLS and in case the wan/vpn is down users can even log in with
    cached credentials.
    Hope it helps.
    http://mariusene.wordpress.com/

  • OSPF design for branch offices across MPLS

    Hello fellow networking engineers,
    I want to implement OSPF in our network. We have multiple branch offices, all linked to an MPLS backbone.
    I know that in order to get linked areas, I would need to setup GRE tunnels between them, but I want to avoid static/manual configurations as much as possible. With multiple sites, it would become cumbersome to create a mesh real fast.
    Is running OSPF independent areas at each site, and simply redistributing over eBGP a valid solution? This will host voice and data, and will failover to VPN connection (Cisco ASAs) if the MPLS goes down.
    For the VPN backup links, I thought of two options. Either simply using the default route to send everything to the ASA in case of MPLS "death", or inject routes using IP SLA...
    Any input would be appreciated.

    Marc
    You don't GRE tunnels to link your areas if that is what you want to do.
    If the SP supports it then you can exchange your OSPF routes between areas and they will still be seen as inter area routes rather than OSPF externals which they would if you simply treated each area as isolated from each other.
    In effect the MPLS network becomes an OSPF super backbone area and your main site would also be part of the backbone area with all your other sites having an area each.
    You still redistribute your OSPF routes into BGP but with some extra configuration on both your CEs and the SP PE devices.
    Like I say you would need to check with your SP but it is possible.
    Whether or not you need or want it I don't know.
    Your other option is as you have proposed to treat each OSPF area as an isolated one and simply redistribute into OSPF at each CE. Then within each site all non local routes would be seen as OSPF external routes.
    Either way in terms of backup I would keep it simple and use a default route at each site pointing to the ASA device. I can't see what you gain from IP SLA because if the main MPLS link goes down at any site the only other path they have out is via the ASA so there is nothing really worth tracking.
    The only other thing I would mention is remote site to remote site traffic. If there is any then presumably with your VPN tunnels you would be doing a sort of hub and spoke where the hub is the main site so you may need to think about traffic coming in from one VPN tunnel and going out to another VPN tunnel on the main site ASA.
    This would only really be needed if two or more sites had to use their backup links at the same time.
    In terms of which is better ie. OSPF inter area across the MPLS cloud or OSPF externals I can't really say to be honest. With the MPLS networks i have worked on we ran EIGRP and simply treated each remote site as an isolated AS.
    If you are already running OSPF then you may want to preserve your existing areas so it would make sense to go with the inter area option.
    If it is a new setup then I don't really know the pros and cons of either so can't really comment.
    Perhaps others may add to the thread with their thoughts.
    Jon

  • How to get logs from CUCM for initiated calls

    Dears,
    like in Voice Gateway for initiated calls we can run debugs command like debug voip ccapi inout to know the calling and the called number and the status of the call, matched dial-peer, ... etc
    Can we do the same in CUCM
    Thanks in advance for your help

    CDR is used mainly for call statistics, it is not designed for detailed troubleshooting. Reading cucm logs requires a detailed understanding of how different components function and some practice. It can be a little daunting.
    This book is excellent. This is what I always recommend as the starting point..
    http://books.google.co.in/books?id=YcCjKsssklIC&pg=PA42&lpg=PA42&dq=call+manager+trace+reading&source=bl&ots=ZW5_hvNFGA&sig=22rtALJZjQFfe9JrHjgAB_GgtRU&hl=en&ei=4qT3TLfTDsuYOs_I3YwI&sa=X&oi=book_result&ct=result&redir_esc=y#v=onepage&q=call%20manager%20trace%20reading&f=false
    This doc explains how to read h323 traces in cucm
    https://supportforums.cisco.com/docs/DOC-11779
    This blog explains how to understand sip traces..
    https://supportforums.cisco.com/document/113271/understanding-sip-traces

  • Which is better for Branch Office Cisco ASA or Cisco 1900 router for Branch Office?

    Which is a better solution ?
    Using ASA55XX or 1900 series router for WAN and Internet access for 25 - 100 users?

    Without knowing more about the environment and what the real requirements are, it is difficult to give a really good answer. If your main concern is effective stateful inspection of traffic entering and leaving the site then the ASA is optimized for that. If you want redundancy (active/active or active/standby) then the ASA is better for this. There are other potential requirements which may make the router the better choice:
    - what is the connection to the Internet? If it is Ethernet then either ASA or router will do fine. But if it is something other than Ethernet then you may need the router.
    - is there a need for services such as Policy Based Routing? These are available on the router and not on the ASA.
    - is there a need for load balancing on outbound traffic? This is available on the router and not on the ASA.
    - will there be a need to do routing on the inside network? The range of available options is wider on the router than on the ASA.
    - is there a need to run a routing protocol with the Internet provider? The usual choice for this is BGP and that is available on router and not on ASA.
    So consider these criteria as you make your choice. Or provide more detail about your environment and what your real requirements are and we may be able to give better advice.
    HTH
    Rick

  • Cisco ATA 187 faxing issues

    We have a site (a new site) that has about 50 or so ATA 187's being used for faxing. Were having faxing issues where some fax machines can't fax to external (to the PSTN) fax machines. They seem to be related to Ricoh fax machines that are Super G3. Any one come across similar troubles with the ATA's? Considering going to VG224's.
    Thanks!

    I have around 80 ATAs in production accross 11 sites and they gave me some headaches, a simple google search will produce dozens of similar issues.
    Obviously there is a lot of things that come into play such as your PSTN transport (SIP/ISDN?) and also your media transmission method (t.38 vs pass-through). Here are some questions so we can better help you.
    1.Start basic, make sure the affected ATAs have an external phone number mask properly assigned, sounds easy but this is the most common reason why my clients submit tickets.
    2. Are you using CUCM for call control? 
    3.Collect appropriate debugs and post them, "debug ccsip messages" or "debug isdn q931) depending of your transport. Also provide us a copy of your gw config.
    4. Symptoms: Issues with sending AND receiving? Error message/Busy signal? 
    - Frank

  • Hotline (PLAR) in ATA 187

    Hi,
    What is the configuration for hotline (PLAR) in ATA 187?
    The CUCM version is 8.6.1.20000-1
    The ATA-187 firmware version is ATA187.9-2-3-1, which support PLAR according to the Release Notes:
    http://www.cisco.com/en/US/docs/voice_ip_comm/cata/187/9_2_3/english/release/notes/atarn923.html
    The ATA 187 phone configuration window in the CUCM includes the following Note:
    ***** Note: A custom Softkey template without supplementary service Softkeys must be used for a Hot line Device.
    Thanks,
    Shlomi

    Hi
    See if this helps you
    http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/admin/8_0_1/ccmcfg/b03dn.html#wpxref85834
    step 5 and 6 are for SIP phone.
    Regards
    Ronak Patel

  • Branch office WDS still pullinh image from main site

    Hi,
    I'm trying to configure a WDS on our branch site.
    what i did was open a new folder named DeployFilesFromMaster on the branch office server and replicate the DeploymentShare from main to branch office using DFS.
    then i installed WDS services on the branch office and add a Boot Image (taken from DeployFilesFromMaster)
    next i configured, under Scope Option on the DHCP server, options 66 (giving the ip address of the branch WDS), and option 67 (giving the path \Boot\x64\wdsnbp.com).
    now when I'm booting a computer into PXE it start working, but when pressing F8 and use the netstat command i see it has a session to my main office deploy server instead to the branch office.
    what do i need to change?
    when looking in the branch office server, there is ofcourse the DeployFilesFromMaster folder and there is another folder named DeploymentShare that was made while installiing the WDS server, and there is a wdsnbp.com file as well. how do I know, when DHCP
    direct me to the boot file name, that it direct me to the right file, or it doesnt matter.
    thanks for your help

    The variable WDSSERVER is a variable that is figured out by MDT when booting a machine using the boot image created by Microsoft Deployment Toolkit. Therefore it is not available in Windows.
    If you want different WSUS servers depending on location of the client you can use for instance this technique in CustomSettings.ini. This will point clients on a specific subnet to a specific WSUS server.
    [Settings]
    Priority=DefaultGateway,Default
    [DefaultGateway]
    10.0.0.1=HQ
    10.0.1.1=BranchOffice
    [HQ]
    WSUSServer=http://wsus-hq:8530
     [BranchOffice]
    WSUSServer=http://wsus-branch:8530
    Blogging about Windows for IT pros at
    www.theexperienceblog.com

  • ASA5505 I cannot reach to an outside network from a branch office

    My customer has a HQ office and many Branch offices. In the HQ there is an ASA5510 configured as a default gateway, From HQ customer must access to internet (everythig works fine), from Inside LAN should reach to anyway including special services like Credit Card service provider and others (it works fine). From Branch offices must reach Inside LAN hosts (it works fine), from Branch Offices must reach DMZ (it works fine), from branch offices should reach CC Service provider and here's the point of this Q, From almost all branch offices they reach CCSP fine but branch offices where an ASA5505 is installed (Offices that reach CCSP have a RV042 installed or a TPlink ER6120 installed) but offices with ASA just can ping to LAN side of CCSP's router.
    I think ASA5505 conf is an opened door configuration. Here's the 5505 configuration and also attached the network diagram. Some one can help please

    Hi,
    Are the branch offices connected to the HQ through some ISP MPLS network since I do not see any L2L VPN configurations on the ASA5505?
    I presume this is the case. Since you say that the connections between Branch Office (with ASA5505) and HQ LAN work fine it should tell us that there should be no routing problems between those networks.
    The diagram possibly also suggests that all the Branch Office connections come to your HQ network through the same Router at the edge so if other Branc Offices connections CCSP work then there should be no routing problem between the Branch Offices and the CCSP (atleast regarding your part of the network)
    Now, some questions.
    Does the ISR Router forward traffic destined to CCSP directly to the Router at 192.168.2.249 ?
    Does the Router with the connection to the CCSP use the Internet to reach the CCSP or is there somekind of dedicated connection between these networks?
    If the Router towards CCSP uses Internet then does it lack some NAT configurations for the source network 192.168.27.0/24? Does it perhaps lack a route towards the network 192.168.27.0/24? Or is there any possible errors in the configurations (wrong gateway IP or network mask somewhere?)
    Is there any ACLs configured on the Router that has the connection to the CCSP that might block traffic?
    Does the CCSP have all the required routing information to pass traffic towards the network 192.168.27.0/24? (If were talking about a dedicated connection and not traffic through the Internet) Have they allowed traffic from the mentioned network 192.168.27.0/24 to their servers/network?
    Have you taken "packet-tracer" output from the ASA5505 to confirm that the ASA configurations allow the traffic and dont drop it for some reason?
    For example
    packet-tracer input inside tcp 192.168.27.100 12345 193.168.1.100 80
    You can modify the IP addresses (source/destination) and the used destination port and protocol to match the connections that are actually attempted.
    Have you monitored the connections on the ASA when users attempt them? This should atleast tell you why they are failing or give a hint. You could also configure traffic capture on the ASA5505 if you wanted to make sure if any traffic was coming from the CCSP towards this ASA (return traffic for connection attempt)
    Hope this helps :)
    Let me know if I missunderstood the situation wrong somehow.
    - Jouni

  • Branch Office Communication

    Hi,
    Supposingly we have many branch offices with good internet speed but no dedicated bandwidth between individual locations.
    We need to enable VoIP calling using Internet, can we use any skype product to tie all standalone EPABX system for branch office communications. 
    Can we have SIP trunks on skype gateway from each location and enable interoffice calling.
    Please suggest

    Hello Rahul,
    I see you are asking about connecting your offices together for calling and comminucations.
    Well,  Connecting the offices together will require a Communication Server of some sort.  Manufacturers like Nortel, Avaya, Cisco, and many others have these type of devices available to accomplish the "link" between your offices, as long as the equipment is all compliant with the Communication Server.   I suggest you contact a local agent for these manufacturers and have them take a look at what you have. They will provide you with a quote to get you connected.
    As for Skype, making and receiving calls is a snap for us.  We provide these services 24/7. We can get you connected in miinutes and have you making cheap calls all day long.  The cost just depends on where in the world you are calling.  Our "minutes" bundles are very cost effective to use.  And, all of your incoming calls are free. All you would need, would be a Skype Online Number, a Managed User for the Skype Clients that want to call you, and SIP Channels to connect to your PBX to talk on.
    That's pretty much it.  I hope this helps you in your research to get your offices connected and to start using Skype.  I have provided  a few links for you to look at below.
    http://www.skype.com/intl/en-us/business/skype-connect/
    http://www.skype.com/intl/en-us/business/skype-manager/
    http://download.skype.com/share/business/guides/skype-connect-rates.pdf
    http://skypeconnect.voxygen.com/#stage1
    Thank You for considering Skype and using the Skype Community Forums.
    Regards,
    Victor S.
    Skype Enterprise Support

  • Invoic & GSVERF IDocs with Head & Office Branch office relationship

    Hi ,
    We have maintained Head office & branch office relationship in vendor master.
    Based on this master data set up, all accounting documents are getting posted to Head office account. Currently we are facing the below issue:
    We have created purchase order for Branch office vendor (Eg. B) and as required accounting document is getting posted to Head office vendor(Eg. H). We are using Idoc Msg type 'Invoic' for this invoice verificaiton and using Idoc msg type 'GSVERF' to send acknowledgement for that Invoice.In this case, Acknowledgement IDoc has been getting transmitted to Head office vendor (H) and not the Branch vendor (B) who
    has originally sent the Invoice.
    Kindly let me know whether it is possible to forward acknowledgement vendor to branch account instead of Head office.
    Thanks
    Hari

    Moved from SAP ERP Sales and Distribution (SAP SD) to SAP ERP Financials
    G. Lakshmipathi

  • Install windows server 2012 DC on Branch office

    Hi ALL,
    i am planning to install a secondary DC on our branch office where currently they are on different domain and forest. our head office is currently on windows server 2008 R2 std, where forest and domain functional level are on windows server 2003. our headoffice
    domain name is:- (corpoffice.org) and branch office domain is:- ssl (its a single level domain on windows server 2003).
    am thinking to upgrade our headoffice DC to windows server 2012 r2 and the same i wanted to do for branch office as well.
    i need some guidance how to proceed with this DC setup as both vlan network is different and all the client settings are different. am getting few query like
    1. should i upgrade my headoffice DC first before i setup the branch office DC.
    2. how the branch office client will communicate to new DC.
    any suggestion and guidance would really helpful.
    Thanks
    srini

    Hi
    You will need to make sure all the ports are open for traffic to move between both DC's. Also need to check that you dont have replication problems, IE, slow link. First step would be to see if you can ping the HO DC from the branch, then once you have established
    that you have all the ports open and your VLAN is routing traffic correctly then you can start with your DC setup.
    You can first upgrade your DC, look at this blog: 
    http://blogs.technet.com/b/kevinholman/archive/2013/09/25/upgrading-domain-controllers-to-windows-server-2012-r2.aspx
    Hope this helps. Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

  • ATA 187 no good for PLAR

    I have an ATA 186 which I've configured as a PLAR phone, using this method:
    http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_configuration_example09186a0080232b9f.shtml
    It works a treat, someone picks up the analog phone connected to the ATA and it uses a translation pattern to autodial a certain number which is forwarded to voicemail and the person on the phone hears a pleasant message telling them something.
    However, business needs made me use this ATA for other uses and it was eventually replaced with an ATA 187, I configured it in exactly the same way, however the PLAR feature didn't work. I could manually dial the recipient number, but the translation pattern didn't kick in.
    Could it be related to the 187 using SIP as opposed to the 186 using SCCP?
    I'm not impressed with the 187. It looks good, but doesn't even draw PoE

    Did you see this info?
    http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/admin/6_0_1/ccmcfg/b03sdial.html#wpxref14049

  • Unity Connection - Certificate from cucm no more trusted for encrypted calls after upgrade to 10.5(1)

    Hello Support Community,
    i have a strange problem:
    after upgrading my cucm and unity connection from 9.1 to 10.5(1) enctrypted calls are no more working.
    situation 1: CUCM is down, Subscriber is up: Encrypted call to Unity Connection work correctly
    situation 2: CUCM is up: Encrypted Calls to Unity Connection not working.
    i get the following Info in the log for the Connection Conversion Manager:
    19:35:21.053 |15865,,,MiuGeneral,25,Invalid Certificate: Received Certificate -----BEGIN CERTIFICATE-----
    MIID8zCCAtugAwIBAgIQc/fBdUz1Zdh4CXhcPqGVuDANBgkqhkiG9w0BAQsFADBw
    MQswCQYDVQQGEwJERTELMAkGA1UEChMCSVQxGzAZBgNVBAsTEkhlbGxnYXRlIFRl
    XD0oD9d5MQ==
    -----END CERTIFICATE-----
     doesn't match with stored Certificate: -----BEGIN CERTIFICATE-----
    MIIC2DCCAkGgAwIBAgIIJWCm4bSdt+kwDQYJKoZIhvcNAQEFBQAw
    -----END CERTIFICATE-----
    so where does Unity Connection cache this certificate and how can i delete/replace it?
    the cert shown in the logs is the one from cucm: ("CallManager"), i recreated it through cucm os administration, now i see the same error message on unity connection for the new recreated certificate.

    Actually It doesn't. It says he's on a MacBook. I don't know all the different types of Macs. I was having a ton of problems with iChat. I opened DMZ to my computer, knocked down all firewalls etc and left everything exposed, still with bad results. A few weeks ago my power supply went out on my D-Link. I bought a linksys. Since I'd left all firewalls off I figured it couldn't be the router. I power cycled everything n the netork, still no luck. Today I bought a universal Power supply and started up my D-Link Router. Everything worked perfectly. My wifes computer - a laptop running Tiger worked fine with the Linksys and did my machine before the Leopard upgrade. Now that I've got the D-Link online everythings working.
    Message was edited by: graphico
    Message was edited by: graphico

Maybe you are looking for