MPLS issues with redundant PE routers

Hello,
i'd like to set up an mpls lab. the layout of the gear is attached (mpls.jpg) At site A i have to PE router R4 and R6 which should have knowledge of the network 10.0.129.0/24 from site B. Router R1 is configured as a route reflector. the configuration of R1, R4, R5 and R6 are attached as well.
with the configuration
Routing Table R6
O E2     10.0.129.0 [110/1] via 172.16.128.9, 00:04:37, FastEthernet0/1.200
Routing table R4
B        10.0.129.0 [200/11] via 150.1.5.5, 00:05:00
a traceroute shows the path goes through R4 instead direkt through R1
Tracing the route to 10.0.129.1
VRF info: (vrf in name/id, vrf out name/id)
  1 172.16.128.9 4 msec 0 msec 4 msec
  2 172.16.128.1 [MPLS: Labels 19/29 Exp 0] 96 msec 100 msec 96 msec
  3 150.1.0.2 [MPLS: Labels 19/29 Exp 0] 68 msec 64 msec 68 msec
  4 172.16.129.9 [MPLS: Label 29 Exp 0] 64 msec 64 msec 64 msec
  5 172.16.129.10 40 msec *  36 msec
show bgp vpnv4 unicast all 10.0.129.0 indicates an error
Rack1R6# show bgp vpnv4 unicast all 10.0.129.0
BGP routing table entry for 200:1:10.0.129.0/24, version 63
Paths: (1 available, best #1, table CENTRAL, RIB-failure(17) - next-hop mismatch)
  Not advertised to any peer
  Local
    150.1.5.5 (metric 67) from 150.1.1.1 (150.1.1.1)
      Origin incomplete, metric 11, localpref 100, valid, internal, best
      Extended Community: RT:200:1 OSPF DOMAIN ID:0x0005:0x000000C80200
        OSPF RT:0.0.0.0:3:0 OSPF ROUTER ID:172.16.129.242:0
      Originator: 150.1.5.5, Cluster list: 150.1.1.1
      mpls labels in/out nolabel/29
Rack1R4#show bgp vpnv4 unicast all 10.0.129.0
BGP routing table entry for 200:1:10.0.129.0/24, version 146
Paths: (1 available, best #1, table CENTRAL)
  Not advertised to any peer
  Local
    150.1.5.5 (metric 67) from 150.1.1.1 (150.1.1.1)
      Origin incomplete, metric 11, localpref 100, valid, internal, best
      Extended Community: RT:200:1 OSPF DOMAIN ID:0x0005:0x000000C80200
        OSPF RT:0.0.0.0:3:0 OSPF ROUTER ID:172.16.129.242:0
      Originator: 150.1.5.5, Cluster list: 150.1.1.1
      mpls labels in/out nolabel/29
any ideas what i have to do in order to have a redundant path towards site B?
thanks in advanced
Alex

Hi Alex,
I think you still have redundancy via R6, but BGP route on R6 is not getting installed in routing table because it is having OSPF route with lesser AD value. If R4 goes down, R6 will loose OSPF route for 10.0.129.0/24 coming from R4, install BGP route ,redistribute this to OSPF and will advertise it to SW4.
Routing Table R6
O E2     10.0.129.0 [110/1] via 172.16.128.9, 00:04:37, FastEthernet0/1.200
Rack1R6# show bgp vpnv4 unicast all 10.0.129.0
BGP routing table entry for 200:1:10.0.129.0/24, version 63
Paths: (1 available, best #1, table CENTRAL, RIB-failure(17) - next-hop mismatch)
  Not advertised to any peer
  Local
    150.1.5.5 (metric 67) from 150.1.1.1 (150.1.1.1)
      Origin incomplete, metric 11, localpref 100, valid, internal, best
      Extended Community: RT:200:1 OSPF DOMAIN ID:0x0005:0x000000C80200
        OSPF RT:0.0.0.0:3:0 OSPF ROUTER ID:172.16.129.242:0
      Originator: 150.1.5.5, Cluster list: 150.1.1.1
      mpls labels in/out nolabel/29

Similar Messages

  • Atheros WLAN Driver Fixes Connection Issues With Many New Routers (Linksys, Netgear, D-Link, etc...)

    Hi:
    This post is for those that have the below listed Atheros adapters, and recently upgraded their routers (usually from a Wireless G to a Wireless N router from 2009 or newer), only to find they cannot connect to the internet anymore.
    Atheros AR5006 802.11a/b/g WiFi Adapter
    Atheros AR5007 802.11b/g WiFi Adapter
    Atheros AR5009 802.11a/g/n WiFi Adapter
    When using their old equipment, there were no problems.
    Symptom:  When upgrading to a new router, normally connection is made to the local network, but one cannot access the internet.
    Symptom:  Wireless connects if using WEP security or no security, but will not connect when using WPA2-Personal security.
    For those who have the above Atheros wireless adapters, and are experiencing issues with connecting to the internet, there is a driver available that should remedy the situation. 
    It is good for Windows operating systems -- Windows XP through Windows 7 -- 32 or 64 bit.
    It may work on Windows 8 too, but I haven't tested it on Windows 8.
    Here is the link to the driver download page:
    http://h20564.www2.hp.com/hpsc/swd/public/detail?sp4ts.oid=5060881&swItemId=ob_108905_1&swEnvOid=405...
    Best Regards,
    Paul

    I created an HP account just to thank you for this link. I've spent 2 days online and talking to call centers trying to get this driver. I was finally going to just return my router to Best Buy. Thank you SO much!

  • Anyone else having issues with third party routers...

    Last week I started having issues with my Asus RT-N66U where certain wireless devices e.g. PS3, Xbox 360, Laptop, etc. have issues connecting to the internet (the PS3 reporting a DNS issue) even after I replaced it with a second rt-n66u.
    I then tried using the HH3 I got with BT and have none of these problems.
    Back on the Asus I tried a manual DNS (BTs 62.6.40.178 and 62.6.40.162) but these are having issues as well although strangely it will work fine if I use it purely as a wireless access point via the HH3 (With HH3's internal wifi disabled), right now I'm testing it again with Google's DNS but I want to know, is anyone else having any issues?

    Is your firmware up to date? http://support.asus.com/Download.aspx?SLanguage=en&m=RT-N66U+%28VER.B1%29&os=8

  • Issue with 2wire dsl router when connecting power pc g4 via ethernet

    Issue with 2wire dsl router when connecting power pc g4 via ethernet. The 2wire will keep resetting. When I connect my macbook pro via ethernet to the 2wire all is ok, but as soon as i connect the power pc. . . .reset. I have emailed 2wire support. They recommended using a different patch cable. Tried that.. .. anyone else having this issue???? Any help would be appreciated. . .

    Search the discussions for issues with 2wire dsl routers. This has come up before in a discussion I've been involved with, but probably not to do with the MDD. I do remember it being a design issue with the router, something that was done to it before dispatch.
    Let us know if you can't find it and we'll have a look.
    If you afford it, bin the 2wire and go buy something decent like a Netgear.

  • Windows 7 Update Internet Connection Issue with Router

    I updated two of four toshiba laptops with Windows 7 and installed Toshiba's wireless adapter driver for Windows 7. The adapter connects to the router and I can access all resources on my home network, however, Internet service is not available on the two laptops with the Windows 7 update. After disconnecting and reconnecting 7-10 times, the Internet Service connection does not drop. The other two laptops and two desktops that are not running Windows 7 do not have this problem. Is there any known issues with lynksys wireless routers and Windows 7?

    When your Windows 7 machine is having problems, can it ping the following IP addresses:
    127.0.0.1 (local loopback)
    192.168.1.x - the DHCP IP address it was issued by the router
    192.168.1.254 - your router
    8.8.8.8 - Google DNS out on the internet
    -- Dan Meyer
    http://www.linkedin.com/in/danielrmeyer

  • HT204409 I have a new iphone 5 and it won't connect to a wireless router that my old iphone 3GS would pick up. Is there a compatibility issue with some routers or is the antenna weaker in the new iphone 5?

    I have a new iphone 5 and I can't pick up a wireless router that I could use with my old iphone 3GS. Is there an issue with the new iphone and is the antenna weaker than the 3GS?

    Please read this :
    https://discussions.apple.com/message/20053332?ac_cid=tw123456#20053332
    Well I copyed it to you here.
    Re: Anyone still having IOS 6 wifi issues?
    created by mpa9366 in Using iPad - View the full discussion
    Having done a lot of reading today and having found a very good online tablet magazine (will post link tomorrow) there seems to be a few tech bods onto the problem.
    The magazine I was reading identified wifi problems within hours of the ios 6 release and have been analysing since then with almost daily updates - the story seems to be:
    The apple authenthication transmission is normal, it should slip through event prior to a full handshake with the host network being completed - however if not authenthicated then apple will not permit the device to connect (kills the connection) this is designed to protect apple from counterfeiting. So thats problem 1 if you dont receive a token from apple.
    Problem 2 is that ios 6 only supports ipv6 (the new ip protocol) whereas outside silicon valley a large proportion of routers modems etc are still ipv4 protocol.
    So youre locked into ipv6 in a world where ipv4 devices are everywhere and apple have not allowed for the ability to handle both protocols. This is like GM telling you your car requires an upgrade, everything will improve etc and as part of the upgrade fits a fuel cell motor and stays silent when their upgraded vehicles are simply parked up because they cannot get fuel.
    A very basic expectation would have been dual protocol handling - we know the HW supports ipv4 as all wad fine on ios5.
    So its going to be hit and miss with networks - more hit than miss in techy areas like silicon valley, but more miss in places like where I am - a small town in rural Switzerland.
    Only apple can fix this with a patch to enable ipv4 protocol handling.
    There you go. you just need to buy a new router, I'm sure Apple has one for sale, cause it's not there fault for sure.
    Wonder why people start to migrate to other devices ?

  • 10.4.8 network issue with some routers (Zyxel)

    Since I have installed 10.4.8 there is a problem with my Zyxel Prestige 310 router, which after a short period of time "hangs up" - so nobody in the network has Internet conection ( PC's and other Macs with 10.4.7).
    After restarting the router everything works fine, until I start a Mac with 10.4.8..
    This happens on Intel and G5 Macs..
    Today I had a long phonecall with my Provider here in Austria, who told me that a lot of people are having this problem - all with Zyxel Routers - but he doesn't know a solution.
    He (and me) is waiting for a fix from apple...:-)

    I also have an issue with the 10.4.8 update and a Zyxel router, although mine is not as severe as yours.
    Mine has to do with WPA encryption and a timeout setting.
    The thread is here:
    http://discussions.apple.com/thread.jspa?messageID=3246932
    So, maybe this helps?
    MacBook white, 2.0 GHz, 1,25 GB RAM   Mac OS X (10.4.8)  

  • Apple Support admitted an Issue with WEP authentication and some Routers

    After reading many posts here and other places I logged a service call to Apple support. With the particulars: AT&T U-verse 2 Wire router would not connect with WEP would connect with Security disabled. I wanted a call logged before I went past the return time
    I got a call back immediately after a few basic questions I was passed to a product manager for ipads, it seems connectivity issues are taken seriously.
    The upper level support said there were known issues with some routers and WEP security we steeped through changing the security and it works fine now.
    Bottom Line:
    Apple knows there is an issue with some routers
    They were very helpful and acknowledged the issue.
    He even stayed on the line while I reconfigured one of my Windows PC to make sure it connected to the new settings
    I suggest to all to log a call and get a tech support involved before taking the iPad to the local store
    They certainly new their are some connectivity issues. If that does not work you can always return it.
    He did not admit it was a Apple issue and did not commit that Apple was working on it but it is something they are aware of.
    So skip the Apple store got right to tech support.
    Just my 2 cents.

    "But folks need to go straight to tech support. I live in oz, so it will be interesting to see if they help me.. or not.. but if support gets inundated they will fix it or have a massive recall (not likely on the latter)."
    Can't agree more. I used to manage a tech support department and it is all about the numbers. No matter how many forum entries the issues that get addressed are dictated by the reports.
    So for those that are buying new routers contact Tech Support first even if you end up getting a new router the call is logged that will get Apple's attention.
    People that are not familiar with post launch processes have no idea how things that need to get corrected and enhanced are dictated by support requests

  • Can I configure a wireless home network with two cable routers (both with separate connections to the same cable company)?  Issue is poor signal strength even with multiple Airport Expresses added to the network.

    I have a wireless home network consisting of a time capsule, two airport expresses and a cable modem.  Even with this configuration I get a very weak signal in much of be condo - the walls, etc. are solid concrete. I want to see if I can add another separately connected cable modem and connect one of the existing airport express to it by Ethernet cable.  If so, this would give me two wired hubs and greatly improve signal strength. I do not know if this configuration will in fact work or if I will just wind up with two, separate and unrelateable networks.  Unfortunately, there is no way to run any additional Ethernet cable and I doubt simply adding more Airport Express will help. Thanks.

    Try Ethernet over Power adapters.. these are very popular for your kind of environment.. being able to make non-wireless link to another area where you can setup a wireless access point.
    Airport Express are not great for wireless power.. if you really have issues with wireless strength in a bad environment apple stuff is not the way to go.
    The comparison chart here.
    http://www.smallnetbuilder.com/lanwan/router-charts/bar/58-2_4-ghz-dn?see=P_F
    This is their worst test location you can also see averages.. the latest airport extreme.. is there a long way down.. and that is a much better wireless device than Airport Express.
    The Ubiquiti power AP is small cheap and designed for precisely this duty.. useless in an apple wireless network.. you will need to run ethernet or EOP adapters back to the main router.. but if the normal omni directional antennas don't provide enough signal you can get directional ones.. I suspect you can cover your whole apartment with a pair of these and high gain directional antenna.

  • I'm having issues with Safari and Mavericks. It encounters errors frequently and cannot attach docs to my web e-mail without redundant steps. Any solution ideas?

    When using my web e-mail (Outlook web app) Safari frequently closes the page and says it must reload the page...then it errors-out. When this happens I must close Safari completely then reopen it, and reopen Outlook web app. My cache is cleared frequently (at least once per day). I am also unable to directly attach docs to e-mails - I must go the through the process twice. This never occured before Mavericks.
    Any ideas on a solution...anyone else experience issues with Safari/Mavericks operations?

    Hello Cabamyk,
    It sounds like you are having issues loading this web app for Outlook. I was thinking that there may be a 3rd party add-ons interfering with Safari or perhaps one may need to ge re installed. Use this article to help troubleshoot add-ons:
    Safari: Unsupported third-party add-ons may cause Safari to unexpectedly quit or have performance issues
    http://support.apple.com/kb/ts3230
    Use the add-on's uninstaller, if possible
    Quit Safari.
    Remove any unsupported third-party add-ons you've installed (see if the add-on's installer includes an uninstall feature).
    Open Safari again.
    If these steps fix the issue you were having, check the website of the software's developer to see if there is an updated version available, or avoid using the add-on.Manually uninstall third-party add-onsIf the software doesn't have an uninstall feature, quit Safari and try manually moving the third-party add-on files. These files are usually installed in one or more of the following locations:
    /Library/Internet Plug-Ins/
    /Library/Input Methods/
    /Library/InputManagers/
    /Library/ScriptingAdditions
    ~/Library/Internet Plug-Ins/
    ~/Library/Input Methods/
    ~/Library/InputManagers/
    ~/Library/ScriptingAdditions
    The first four locations listed are in the root-level Library on your hard disk, not the user-level Library in your Home folder.The tilde (~) represents your Home folder.
    To access the Home folder in OS X Lion, OS X Mountain Lion, or OS X Mavericks, open the Finder, hold the Option key, and choose Go > Library.
    To access the Home folder in Mac OS X v10.6 and earlier, open the Finder and choose Go > Home. Then, click the Library folder.
    If the issue is resolved by removing items from the above locations to a different location, return the items one at a time and test Safari. That way you can determine which item is causing the issue. Once identified, remove the problematic item and put the others back. Check for updates to the items that are found to cause issues, or report the issue to the add-on developer.Important: When removing items from the above locations, do not put them in the Trash. Instead, put them in a new folder or on the desktop while troubleshooting. If removing the item does not resolve the issue, you can put it back where it came from. In Mac OS X v10.6 or later, you can use the Put Back feature of the Trash to automatically put items back where they came from.Files that should not be removedThe following items should not be deleted from your system:
    /Library/Internet Plug-Ins/iPhotoPhotocast.plugin
    /Library/Internet Plug-Ins/nsIQTScriptablePlugin.xpt
    /Library/Internet Plug-Ins/Quartz Composer.webplugin
    /Library/Internet Plug-Ins/QuickTime Plugin.plugin
    /Library/Internet Plug-Ins/QuickTime Plugin.webplugin (Mac OS X v10.5.x only)
    /Library/Internet Plug-Ins/VerifiedDownloadPlugin.plugin (Mac OS X v10.5.x only)
    Reinstalling the above plug-ins requires reinstalling OS X. Some application or system updates may restore specific plug-ins.
    Thank you for using Apple Support Communities.
    All the very best,
    Sterling

  • Calling issue with Cisco 7937 conference station

    Hi Friends,
    I am facing issue wiht Cisco 7937 conference station, our customer have various branch offices accross the world. All branches are connected over MPLS through service provider( SIP service provider) . there is a centralized CUCM and remote office have SIP Voice gateways .
    When making calls from once remote site to another using Cisco 6921 phones calls working fine
    When making calls from once remote site to another using Cisco 7937 conference station to make call  any phone at remote office, calls are getting disconneted, remote phone rings when calls,  but its gets fast busy tone when other party picks up the phone and  not able to talk.
    I suspect the issue with Codec but we have configured transcoders  in VG and registered with CUCM
    Please help me if any one experience such issue earlier.
    Regards
    Siva

    hi Basant,
    1. Actually tow phones A and B are registerd with centralized CUCM, A and B are located in two different locations, RTP traffic between And B pass through service provider. 
    Call Flow --> Phone A ---->CUCMRouterpattern--> SIP trunk ----> Voice gateway--->Service provider cloud---> Respective Voice Gateway---> CUCM -- Phone B
    Show Run
    =~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2014.02.27 15:14:52 =~=~=~=~=~=~=~=~=~=~=~=
    sh run
    Building configuration...
    Current configuration : 12139 bytes
    ! Last configuration change at 06:35:59 UTC Tue Feb 25 2014
    ! NVRAM config last updated at 11:16:38 UTC Mon Feb 24 2014 by administrator
    ! NVRAM config last updated at 11:16:38 UTC Mon Feb 24 2014 by administrator
    version 15.1
    service timestamps debug datetime msec
    service timestamps log datetime msec
    no service password-encryption
    hostname eucamvgw01
    boot-start-marker
    boot system flash:c2900-universalk9-mz.SPA.151-4.M5.bin
    boot-end-marker
    card type e1 0 0
    logging buffered 51200 warnings
    no logging console
    no aaa new-model
    no network-clock-participate wic 0
    no ipv6 cef
    ip source-route
    ip traffic-export profile cuecapture mode capture
    bidirectional
    ip cef
    ip multicast-routing
    ip domain name drreddys.eu
    ip name-server 10.197.20.1
    ip name-server 10.197.20.2
    multilink bundle-name authenticated
    stcapp ccm-group 2
    stcapp
    stcapp feature access-code
    stcapp feature speed-dial
    stcapp supplementary-services
    port 0/1/0
    fallback-dn 5428025
    port 0/1/1
    fallback-dn 5428008
    port 0/1/2
    fallback-dn 5421462
    port 0/1/3
    fallback-dn 5421463
    isdn switch-type primary-net5
    crypto pki token default removal timeout 0
    voice-card 0
    dsp services dspfarm
    voice call send-alert
    voice call disc-pi-off
    voice call convert-discpi-to-prog
    voice rtp send-recv
    voice service voip
    ip address trusted list
    ipv4 10.198.0.0 255.255.255.0
    ipv4 152.63.1.0 255.255.255.0
    address-hiding
    allow-connections sip to sip
    no supplementary-service h225-notify cid-update
    no supplementary-service sip moved-temporarily
    no supplementary-service sip refer
    fax protocol t38 version 0 ls-redundancy 0 hs-redundancy 0 fallback none
    fax-relay ans-disable
    sip
    rel1xx supported "track"
    privacy pstn
    no update-callerid
    early-offer forced
    call-route p-called-party-id
    voice class uri 100 sip
    host 41.206.187.71
    voice class codec 10
    codec preference 1 g711alaw
    codec preference 2 g711ulaw
    codec preference 3 ilbc
    codec preference 4 g729r8
    codec preference 5 g729br8
    voice class codec 20
    codec preference 1 g729br8
    codec preference 2 g729r8
    voice moh-group 1
    moh flash:moh/Panjo.alaw.wav
    description MOH G711 alaw
    multicast moh 239.1.1.2 port 16384 route 10.198.2.9
    voice translation-rule 1
    rule 1 /^012237280\(..\)/ /54280\1/
    rule 2 /^012236514\(..\)/ /54214\1/
    rule 3 /^01223651081/ /5428010/
    rule 4 /^01223506701/ /5428010/
    voice translation-rule 2
    rule 1 /^00\(.+\)/ /+\1/
    rule 2 /^0\(.+\)/ /+44\1/
    rule 3 /^\([0-9].+\)/ /+\1/
    voice translation-rule 3
    rule 1 /^9\(.+\)/ /\1/
    rule 2 /^\+44\(.+\)/ /0\1/
    rule 3 /^\+\(.+\)/ /00\1/
    voice translation-rule 4
    rule 1 /^54280\(..\)/ /12237280\1/
    rule 2 /^54214\(..\)/ /12236514\1/
    rule 3 /^\+44\(.+\)/ /\1/
    rule 4 /^.54280\(..\)/ /12237280\1/
    rule 5 /^.54214\(..\)/ /12236514\1/
    voice translation-rule 9
    rule 1 /^\(....\)/ /542\1/
    voice translation-rule 10
    voice translation-rule 11
    rule 1 /^\+44122372\(....\)/ /542\1/
    rule 2 /^\+44122365\(....\)/ /542\1/
    voice translation-rule 12
    voice translation-rule 13
    rule 1 /^\([18]...\)/ /542\1/
    voice translation-rule 14
    voice translation-profile MPLS-incoming
    translate calling 10
    translate called 9
    voice translation-profile MPLS-outgoing
    translate calling 11
    translate called 12
    voice translation-profile PSTN-incoming
    translate calling 2
    translate called 1
    voice translation-profile PSTN-outgoing
    translate calling 4
    translate called 3
    voice translation-profile SRST-incoming
    translate calling 14
    translate called 13
    license udi pid CISCO2921/K9 sn FGL145110RE
    hw-module ism 0
    hw-module pvdm 0/0
    username administrator privilege 15 secret 5 $1$syu5$DsxdOgfS7Wltx78o4PV.60
    redundancy
    controller E1 0/0/0
    ip tcp path-mtu-discovery
    ip scp server enable
    interface Embedded-Service-Engine0/0
    no ip address
    shutdown
    interface GigabitEthernet0/0
    description internal LAN
    ip address 10.198.2.9 255.255.255.0
    duplex auto
    speed auto
    interface ISM0/0
    ip unnumbered GigabitEthernet0/0
    service-module ip address 10.198.2.8 255.255.255.0
    !Application: CUE Running on ISM
    service-module ip default-gateway 10.198.2.9
    interface GigabitEthernet0/1
    description to TATA NGN
    ip address 115.114.225.122 255.255.255.252
    duplex auto
    speed auto
    interface GigabitEthernet0/2
    description SIP Trunks external
    ip address 79.121.254.83 255.255.255.248
    ip access-group SIP-InBound in
    ip traffic-export apply cuecapture size 8000000
    duplex auto
    speed auto
    interface ISM0/1
    description Internal switch interface connected to Internal Service Module
    no ip address
    shutdown
    interface Vlan1
    no ip address
    ip forward-protocol nd
    no ip http server
    no ip http secure-server
    ip route 0.0.0.0 0.0.0.0 10.198.2.1
    ip route 10.198.2.8 255.255.255.255 ISM0/0
    ip route 41.206.187.0 255.255.255.0 115.114.225.121
    ip route 77.37.25.46 255.255.255.255 79.121.254.81
    ip route 83.245.6.81 255.255.255.255 79.121.254.81
    ip route 83.245.6.82 255.255.255.255 79.121.254.81
    ip route 95.223.1.107 255.255.255.255 79.121.254.81
    ip route 192.54.47.0 255.255.255.0 79.121.254.81
    ip access-list extended SIP-InBound
    permit ip host 77.37.25.46 any
    permit ip host 83.245.6.81 any
    permit ip host 83.245.6.82 any
    permit ip 192.54.47.0 0.0.0.255 any
    permit icmp any any
    permit ip host 95.223.1.107 any
    deny ip any any log
    control-plane
    voice-port 0/1/0
    compand-type a-law
    timeouts initial 60
    timeouts interdigit 60
    timeouts ringing infinity
    caller-id enable
    voice-port 0/1/1
    compand-type a-law
    timeouts initial 60
    timeouts interdigit 60
    timeouts ringing infinity
    caller-id enable
    voice-port 0/1/2
    compand-type a-law
    timeouts initial 60
    timeouts interdigit 60
    timeouts ringing infinity
    caller-id enable
    voice-port 0/1/3
    compand-type a-law
    timeouts initial 60
    timeouts interdigit 60
    timeouts ringing infinity
    caller-id enable
    no ccm-manager fax protocol cisco
    ccm-manager music-on-hold bind GigabitEthernet0/0
    ccm-manager config server 152.63.1.19 152.63.1.100 172.27.210.5
    ccm-manager sccp local GigabitEthernet0/0
    ccm-manager sccp
    mgcp profile default
    sccp local GigabitEthernet0/0
    sccp ccm 10.198.2.9 identifier 3 priority 3 version 7.0
    sccp ccm 152.63.1.19 identifier 4 version 7.0
    sccp ccm 152.63.1.100 identifier 5 version 7.0
    sccp ccm 172.27.210.5 identifier 6 version 7.0
    sccp
    sccp ccm group 2
    bind interface GigabitEthernet0/0
    associate ccm 4 priority 1
    associate ccm 5 priority 2
    associate ccm 6 priority 3
    associate ccm 3 priority 4
    associate profile 1002 register CFB_UK_CAM_02
    associate profile 1001 register XCODE_UK_CAM_02
    associate profile 1000 register MTP_UK_CAM_02
    dspfarm profile 1001 transcode
    codec ilbc
    codec g722-64
    codec g729br8
    codec g729r8
    codec gsmamr-nb
    codec pass-through
    codec g711ulaw
    codec g711alaw
    codec g729ar8
    codec g729abr8
    maximum sessions 18
    associate application SCCP
    dspfarm profile 1002 conference
    codec g711ulaw
    codec g711alaw
    codec g729ar8
    codec g729abr8
    codec g729r8
    codec g729br8
    maximum sessions 2
    associate application SCCP
    dspfarm profile 1000 mtp
    codec g711alaw
    maximum sessions software 200
    associate application SCCP
    dial-peer cor custom
    name SRSTMode
    dial-peer cor list SRST
    member SRSTMode
    dial-peer voice 100 voip
    description *** Inbound CUCM ***
    translation-profile incoming PSTN-incoming
    incoming called-number .
    voice-class codec 10
    voice-class sip call-route p-called-party-id
    dtmf-relay rtp-nte
    no vad
    dial-peer voice 500 voip
    description *** Inbound TATA MPLS ***
    translation-profile incoming MPLS-incoming
    session protocol sipv2
    session target sip-server
    incoming called-number ....
    incoming uri from 100
    voice-class codec 20
    dtmf-relay rtp-nte
    no vad
    dial-peer voice 510 voip
    description *** Outbound TATA MPLS ***
    translation-profile outgoing MPLS-outgoing
    destination-pattern 54[013-9]....
    session protocol sipv2
    session target ipv4:41.206.187.71
    session transport udp
    voice-class codec 20
    dtmf-relay rtp-nte
    no vad
    dial-peer voice 520 voip
    description *** Outbound TATA MPLS ***
    translation-profile outgoing MPLS-outgoing
    destination-pattern 5[0-35-9].....
    session protocol sipv2
    session target ipv4:41.206.187.71
    session transport udp
    voice-class codec 20
    dtmf-relay rtp-nte
    no vad
    dial-peer voice 200 voip
    description *** Inbound M12 *** 01223651081, 01223651440 - 01223651489
    translation-profile incoming PSTN-incoming
    session protocol sipv2
    session target sip-server
    session transport udp
    incoming called-number 0122365....
    dtmf-relay rtp-nte
    codec g711ulaw
    no vad
    dial-peer voice 201 voip
    description *** Inbound M12 *** 012237280XX
    translation-profile incoming PSTN-incoming
    session protocol sipv2
    session target sip-server
    session transport udp
    incoming called-number 012237280..
    dtmf-relay rtp-nte
    codec g711ulaw
    no vad
    dial-peer voice 202 voip
    description *** Inbound M12 *** 01223506701
    translation-profile incoming PSTN-incoming
    session protocol sipv2
    session target sip-server
    session transport udp
    incoming called-number 01223506701
    dtmf-relay rtp-nte
    codec g711ulaw
    no vad
    dial-peer voice 210 voip
    description *** Outbound M12 ***
    translation-profile outgoing PSTN-outgoing
    destination-pattern +...T
    session protocol sipv2
    session target ipv4:83.245.6.81
    session transport udp
    dtmf-relay rtp-nte
    codec g711alaw
    no vad
    dial-peer voice 211 voip
    description *** Outbound ISDN for SRST and emergency ***
    translation-profile outgoing PSTN-outgoing
    destination-pattern 9.T
    session protocol sipv2
    session target ipv4:83.245.6.81
    session transport udp
    dtmf-relay rtp-nte
    codec g711alaw
    no vad
    dial-peer voice 212 voip
    description *** Outbound ISDN for emergency ***
    translation-profile outgoing PSTN-outgoing
    destination-pattern 11[02]
    session protocol sipv2
    session target ipv4:83.245.6.81
    session transport udp
    dtmf-relay rtp-nte
    codec g711alaw
    no vad
    dial-peer voice 2000 voip
    description *** Outbound to CUCM Primary ***
    preference 1
    destination-pattern 542....
    session protocol sipv2
    session target ipv4:152.63.1.19
    voice-class codec 10
    voice-class sip call-route p-called-party-id
    dtmf-relay rtp-nte
    no vad
    dial-peer voice 2001 voip
    description *** Outbound to CUCM Secondary ***
    preference 2
    destination-pattern 542....
    session protocol sipv2
    session target ipv4:152.63.1.100
    voice-class codec 10
    voice-class sip call-route p-called-party-id
    dtmf-relay rtp-nte
    no vad
    dial-peer voice 2002 voip
    description *** Outbound to CUCM Teritiary ***
    preference 3
    destination-pattern 542....
    session protocol sipv2
    session target ipv4:172.27.210.5
    voice-class codec 10
    voice-class sip call-route p-called-party-id
    dtmf-relay rtp-nte
    no vad
    dial-peer voice 999010 pots
    service stcapp
    port 0/1/0
    dial-peer voice 999011 pots
    service stcapp
    port 0/1/1
    dial-peer voice 999012 pots
    service stcapp
    port 0/1/2
    dial-peer voice 999013 pots
    service stcapp
    port 0/1/3
    sip-ua
    no remote-party-id
    gatekeeper
    shutdown
    call-manager-fallback
    secondary-dialtone 9
    max-conferences 4 gain -6
    transfer-system full-consult
    ip source-address 10.198.2.9 port 2000
    max-ephones 110
    max-dn 400 dual-line no-reg
    translation-profile incoming SRST-incoming
    moh flash:/moh/Panjo.ulaw.wav
    multicast moh 239.1.1.1 port 16384 route 10.198.2.9
    time-zone 22
    time-format 24
    date-format dd-mm-yy
    line con 0
    login local
    line aux 0
    line 2
    no activation-character
    no exec
    transport preferred none
    transport input all
    transport output pad telnet rlogin lapb-ta mop udptn v120 ssh
    stopbits 1
    line 131
    no activation-character
    no exec
    transport preferred none
    transport input all
    transport output pad telnet rlogin lapb-ta mop udptn v120 ssh
    stopbits 1
    line vty 0 4
    session-timeout 60
    exec-timeout 60 0
    privilege level 15
    login local
    transport input all
    line vty 5 15
    session-timeout 60
    exec-timeout 60 0
    privilege level 15
    login local
    transport input all
    scheduler allocate 20000 1000
    ntp server 10.1.30.1
    end
    eucamvgw01#
    Sh SCCP
    =~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2014.03.03 17:57:44 =~=~=~=~=~=~=~=~=~=~=~=
    SCCP Admin State: UP
    Gateway Local Interface: GigabitEthernet0/0
    IPv4 Address: 10.198.2.9
    Port Number: 2000
    IP Precedence: 5
    User Masked Codec list: None
    Call Manager: 10.198.2.9, Port Number: 2000
    Priority: 3, Version: 7.0, Identifier: 3
    Call Manager: 152.63.1.19, Port Number: 2000
    Priority: N/A, Version: 7.0, Identifier: 4
    Trustpoint: N/A
    Call Manager: 152.63.1.100, Port Number: 2000
    Priority: N/A, Version: 7.0, Identifier: 5
    Trustpoint: N/A
    Call Manager: 172.27.210.5, Port Number: 2000
    Priority: N/A, Version: 7.0, Identifier: 6
    Trustpoint: N/A
    MTP Oper State: ACTIVE - Cause Code: NONE
    Active Call Manager: 152.63.1.19, Port Number: 2000
    TCP Link Status: CONNECTED, Profile Identifier: 1000
    Reported Max Streams: 400, Reported Max OOS Streams: 0
    Supported Codec: g711alaw, Maximum Packetization Period: 30
    Supported Codec: rfc2833 dtmf, Maximum Packetization Period: 30
    Supported Codec: rfc2833 pass-thru, Maximum Packetization Period: 30
    Supported Codec: inband-dtmf to rfc2833 conversion, Maximum Packetization Period: 30
    TLS : ENABLED
    Transcoding Oper State: ACTIVE - Cause Code: NONE
    Active Call Manager: 152.63.1.19, Port Number: 2000
    TCP Link Status: CONNECTED, Profile Identifier: 1001
    Reported Max Streams: 36, Reported Max OOS Streams: 0
    Supported Codec: ilbc, Maximum Packetization Period: 120
    Supported Codec: g722r64, Maximum Packetization Period: 30
    Supported Codec: g729br8, Maximum Packetization Period: 60
    Supported Codec: g729r8, Maximum Packetization Period: 60
    Supported Codec: gsmamr-nb, Maximum Packetization Period: 60
    Supported Codec: pass-thru, Maximum Packetization Period: N/A
    Supported Codec: g711ulaw, Maximum Packetization Period: 30
    Supported Codec: g711alaw, Maximum Packetization Period: 30
    Supported Codec: g729ar8, Maximum Packetization Period: 60
    Supported Codec: g729abr8, Maximum Packetization Period: 60
    Supported Codec: rfc2833 dtmf, Maximum Packetization Period: 30
    Supported Codec: rfc2833 pass-thru, Maximum Packetization Period: 30
    Supported Codec: inband-dtmf to rfc2833 conversion, Maximum Packetization Period: 30
    Conferencing Oper State: ACTIVE - Cause Code: NONE
    Active Call Manager: 152.63.1.19, Port Number: 2000
    TCP Link Status: CONNECTED, Profile Identifier: 1002
    Reported Max Streams: 16, Reported Max OOS Streams: 0
    Supported Codec: g711ulaw, Maximum Packetization Period: 30
    Supported Codec: g711alaw, Maximum Packetization Period: 30
    Supported Codec: g729ar8, Maximum Packetization Period: 60
    Supported Codec: g729abr8, Maximum Packetization Period: 60
    Supported Codec: g729r8, Maximum Packetization Period: 60
    Supported Codec: g729br8, Maximum Packetization Period: 60
    Supported Codec: rfc2833 dtmf, Maximum Packetization Period: 30
    Supported Codec: rfc2833 pass-thru, Maximum Packetization Period: 30
    Supported Codec: inband-dtmf to rfc2833 conversion, Maximum Packetization Period: 30
    TLS : ENABLED
    Alg_Phone Oper State: ACTIVE - Cause Code: NONE
    Active Call Manager: 152.63.1.19, Port Number: 2000
    TCP Link Status: CONNECTED, Device Name: AN71FEF7F070080
    Reported Max Streams: 1, Reported Max OOS Streams: 0
    Supported Codec: rfc2833 dtmf, Maximum Packetization Period: 30
    Supported Codec: g711ulaw, Maximum Packetization Period: 20
    Supported Codec: g711alaw, Maximum Packetization Period: 20
    Supported Codec: g729r8, Maximum Packetization Period: 220Supported Codec: g729ar8, Maximum Packetization Period: 220
    Supported Codec: g729br8, Maximum Packetization Period: 220
    Supported Codec: g729r8, Maximum Packetization Period: 220
    Supported Codec: ilbc, Maximum Packetization Period: 120
    Alg_Phone Oper State: ACTIVE - Cause Code: NONE
    Active Call Manager: 152.63.1.19, Port Number: 2000
    TCP Link Status: CONNECTED, Device Name: AN71FEF7F070081
    Reported Max Streams: 1, Reported Max OOS Streams: 0
    Supported Codec: rfc2833 dtmf, Maximum Packetization Period: 30
    Supported Codec: g711ulaw, Maximum Packetization Period: 20
    Supported Codec: g711alaw, Maximum Packetization Period: 20
    Supported Codec: g729r8, Maximum Packetization Period: 220
    Supported Codec: g729ar8, Maximum Packetization Period: 220
    Supported Codec: g729br8, Maximum Packetization Period: 220
    Supported Codec: g729r8, Maximum Packetization Period: 220
    Supported Codec: ilbc, Maximum Packetization Period: 120
    Alg_Phone Oper State: ACTIVE - Cause Code: NONE
    Active Call Manager: 152.63.1.19, Port Number: 2000
    TCP Link Status: CONNECTED, Device Name: AN71FEF7F070082
    Reported Max Streams: 1, Reported Max OOS Streams: 0
    Supported Codec: rfc2833 dtmf, Maximum Packetization Period: 30
    Supported Codec: g711ulaw, Maximum Packetization Period: 20Supported Codec: g711alaw, Maximum Packetization Period: 20
    Supported Codec: g729r8, Maximum Packetization Period: 220
    Supported Codec: g729ar8, Maximum Packetization Period: 220
    Supported Codec: g729br8, Maximum Packetization Period: 220
    Supported Codec: g729r8, Maximum Packetization Period: 220
    Supported Codec: ilbc, Maximum Packetization Period: 120
    Alg_Phone Oper State: ACTIVE - Cause Code: NONE
    Active Call Manager: 152.63.1.19, Port Number: 2000
    TCP Link Status: CONNECTED, Device Name: AN71FEF7F070083
    Reported Max Streams: 1, Reported Max OOS Streams: 0
    Supported Codec: rfc2833 dtmf, Maximum Packetization Period: 30
    Supported Codec: g711ulaw, Maximum Packetization Period: 20
    Supported Codec: g711alaw, Maximum Packetization Period: 20
    Supported Codec: g729r8, Maximum Packetization Period: 220
    Supported Codec: g729ar8, Maximum Packetization Period: 220
    Supported Codec: g729br8, Maximum Packetization Period: 220
    Supported Codec: g729r8, Maximum Packetization Period: 220
    Supported Codec: ilbc, Maximum Packetization Period: 120
    eucamvgw01#

  • MPLS, GRE (with no IPSEC) & Dynamic Routing

    Good day my friends!
    Just wondering if any of you could help shed some light on how I would do something. We are switching over from a Point to Point connection between sites to an MPLS one. I have read that Multicast is not permitted across MPLS, so after terminating the MPLS circuits into our network, I created some GRE Tunnels to allow for Multicast (for Dynamic routing as well as Music on Hold)... Everything went well, other then all traffic between the sites is going over the Tunnel interfaces. I would prefer that only multicast traffic go over the GRE tunnel and all other traffic traverse the MPLS without GRE Encapsulation.
    I attempted to do this by doing the following... I wrote an access list indicating Multicast source addresses, then created a route map and did a match ip address acl and set interface to tunnel. then I applied that route map to the vlan (although it doesn't give me the option for direction on the 6509 switch) that the single interface is a member of. That interface goes to the router provided by the service provider. I did the same in the other site as well (2811 router, appied to the interface). What have I done wrong so far?
    We run EIGRP and I did inject the tunnel ip addresses into eigrp, after which traffic started going across it (the tunnel). I need to make sure that routing can find a path via MPLS in EIGRP outside of GRE, and for that all I have done so far is create static routes (on our 6509 and 2811 devices that the MPLS terminates to) with the destination subnet being in the other site between the qwest router and our router (Did that at both sites). I havent created any static routes for remote sites internal subnets because I would like EIGRP to do that, I don't want to rely on Static routes for routing between sites as far as our internal routing.
    So I guess, my question is 2 fold:
    What else do I need to do to get EIGRP to know about the path between sites over MPLS besides through the GRE tunnel?
    How would you control traffic so only Multicast traversed the GRE tunnel where all other traffic would go over MPLS natively?
    Any help you could lend would be very much appriciated!

    Thanks for the reply Laurent!
    Ok, so I just got off the phone our SP and they said they do not support Multicast transport over MPLS... so your assumption is correct...
    I see, so it sounds like I want to stay away from allowing all traffic to traverse between sites over MPLS via GRE... I never considered the issue with scaling when using GRE for all traffic. Good to know!
    While I was on the phone with our SP, I talked with them about routing protocol's they support via MPLS, to which they responded with BGP as really the only option.
    FYI, this is our current WAN arrangement between 2 of the sites:
    Site A>Cisco 2811>Adtran Router (SP provided)>PE-PESite B
    Site A>Cisco 2811 (same as above)>Adtran Router (SP provided)>PE-PESite B
    The SP suggested we run OSPF between our hardware and the Adtran routers and then 2-way redistribute subnets between EIGRP to OSPF and then from OSPF to BGP as follows:
    EIGRP ran inside Site A and B
    OSPF running on outside facing interface on 2811 and 6509
    OSPF running on inside interfaces on Adtran routers
    Private AS BGP running on Adtran with Public AS neighbor to PE device
    This should work, but wouldn't it work for me to just configure BGP on our 2811 and have a IBGP adjacency between it and the Adtran Router and then filter what routes are redistributed from and to IBGP on our 2811 into EIGRP? If this would work, does one design have any advantages over the other? It seems like the EIGRP to OSPF to BGP idea has to many moving parts...
    My objective is to allow all devices in all locations (4 MPLS sites) to route dynamically, verses relying on static routes.
    Regarding the Tunnel config's... I see... Excellent example. OK, so it sounds and looks like I would first configure each site with the routing protocol solution, then, implement GRE with per the example provided, and that would accomplish Multicast over GRE and everything else over MPLS! Thanks alot Laurent!
    So what would you recommend regarding the routing protocol structure?

  • Multiple Issues with Adobe Creative Cloud app.

    I'm having multiple issues with the Adobe Creative Cloud app.
    1. Neither Photoshop CC nor Prelude CC get past the 47% mark when installing. They constantly give me "Installation Failed" messages. When I click on "Learn More", I'm told that:
    "Installation Failed
    Errors during Installation.(7)
    More Information"
    So naturally, I click on More Information to get the following thrown at me (none of which I understand):
    Exit Code: 7 Please see specific errors below for troubleshooting. For example,  ERROR:   -------------------------------------- Summary --------------------------------------  - 0 fatal error(s), 2 error(s)    ERROR: 12/01/13 13:16:06:425 | [INFO] |  | OOBE | DE |  |  |  | 6076 | ---------- CustomHook_Helperx64 ---- Start ----------  12/01/13 13:16:06:426 | [ERROR] |  | OOBE | DE |  |  |  | 6076 | Cannot load function name 'CSInstallerCustomHookProc' from library C:\Program Files (x86)\Common Files\Adobe\Installers\uninstall\{5F816B76-62F3-41C9-B651-27F49F25F50B}.data. Error 0    ERROR: System check returned with error : -4  -------------------------------------------------------------------------------------
    2. I installed Lightroom 5, then uninstalled it. When I went back to re-install it, the Adobe Creative Cloud app wouldn't let me. It states that my Lightroom 5 is "Up to date" and is in my "Your Apps" section, not in the "Find New Apps" section. I've double checked my Programs and Features in Control Panel, and it's not there. I cleaned my registry, and it's still there. I deleted the "opm.db" file in my OOBE folder, and restarted CC - still nothing.
    I've got to say, guys. I'm not very happy with the amount of time I've spent just trying to install programs on my PC. While the plan is for this to be intuitive at some point, it's not very functional at the moment. Any help you can provide me would be amazing - if you can provide it sooner than later, I'd be over the moon.
    Thanks.

    I fixed it. I fixed it on my own. My journey took over a week (forty hours of back and forths, trial and error, and service!!) and included multiple calls, multiple online chats, unanswered forum posts, Twitter conversations with the Adobe Customer Service team, remote access sessions with Adobe technical teams, and finally this series of emails. In the end, I had to figure it out myself. I'm not happy - not with the time it took, and not with the level service I received based on the urgency that I made clear.
    For anyone else that had this issue (or similar), here is what I did to fix it. This may seem excessive, but that's because I didn't know what else to do. Some of these steps may be redundant, or not required... but I wouldn't know because once I saw that it was working, I just kept going.
    Anyway, here is the solution I came upon (I'm running Windows 7 64-bit):
    1) I uninstalled every single Adobe product (including Flash Player, Acrobat Player, Air, and Digital Editions).
    2) I ran the Cleaner Tool (which is not very good) and came across errors in trying to delete certain folders.
    3) I restarted my computer in Safe Mode, and logged into Windows 7 under my Administrator account.
    4) I manually went into every folder that contained the words "Adobe" and deleted everything. This includes my Program Data folder, my Program Files folders (both x86 and 64-bit), my AppData folders, my Roaming folders, my Temp folders - ANYTHING and EVERYTHING that contained any trace of Adobe, I deleted.
    5) I ran Microsoft Disk Cleanup and Piriform CCleaner to clean my registry and temp files.
    6) I restarted my computer using the normal boot process and logged into Windows as Administrator.
    7) I downloaded the Adobe Creative Cloud installer.
    8) I restarted my computer again, and logged into Windows as Administrator.
    9) I ran the Creative Cloud installer, and installed Premiere Pro.
    10) I restarted my computer again, and logged into Windows as Administrator.
    11) I ran the Creative Cloud installer, and installed Photoshop.
    12) I restarted my computer again, and logged into Windows as Administrator.
    13, 14, 15...) I ran the Creative Cloud installer and installed whatever programs I needed, then I IMMEDIATELY restarted my computer before installing anything else.
    Hope this helps. Good luck!

  • Windows 7 Pro DNS issue with static IP

    0
    down vote
    favorite
    I have been unable to solve a DNS problem I am having as follows:
    I have a Windows 7 Professional (64 bit) computer running VirtualBox with a couple of Windows XP guests (not sure if this bit is relevant). After heavy file copying/transfer on both of the Windows XP machines, both the guest machines AND the host loose anything
    DNS related, so I cannot call anything by name, but by direct IP works fine. The only resolution is to reboot the (host) machine and it will then work OK for a while until it happens again. The only trigger to make it seem to happen quicker is to re-initiate
    the heavy file transfer and this then causes the DNS resolution to stop working again.
    The machine has a fixed IP address, so it isn't related to DHCP.
    I've tried the machine connected wired and wireless, no difference.
    The IP settings are manual and I have tried giving it the DNS settings of the router (normal settings) and I have also tried giving it Google's DNS servers (8.8.8.8 & 8.8.4.4). No difference.
    It seems to happen (sooner) during heavy traffic.
    Other Windows 7 machines in the network work fine (though they are Home version, not Pro).
    ONLY DNS fails, direct IP works OK.
    Reboot seems only solution at the moment.
    I am now lost as to what to try to resolve this issue, I do not really want to reload Windows 7 as it is a relatively new install... I have read about issues with wired connections on my router (BT Home Hub 2.0) so tried a wireless connection, still the
    same.
    Here is my ipconfig /all (it shows the BT Home Hub router DNS settings, but it also failed with Google's 8.8.8.8 and 8.8.4.4 entered here and also with the routers 192.168.1.254 (default).
    Microsoft Windows [Version 6.1.7601]
    Copyright (c) 2009 Microsoft Corporation. All rights reserved.
    C:\Users\G>ipconfig /all
    Windows IP Configuration
    Host Name . . . . . . . . . . . . : e1
    Primary Dns Suffix . . . . . . . :
    Node Type . . . . . . . . . . . . : Hybrid
    IP Routing Enabled. . . . . . . . : No
    WINS Proxy Enabled. . . . . . . . : No
    Ethernet adapter Local Area Connection:
    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
    Physical Address. . . . . . . . . : 30-85-A9-AD-07-81
    DHCP Enabled. . . . . . . . . . . : No
    Autoconfiguration Enabled . . . . : Yes
    Link-local IPv6 Address . . . . . : fe80::59f:484a:827f:42ba%11(Preferred)
    IPv4 Address. . . . . . . . . . . : 192.168.1.87(Preferred)
    Subnet Mask . . . . . . . . . . . : 255.255.255.0
    Default Gateway . . . . . . . . . : 192.168.1.254
    DHCPv6 IAID . . . . . . . . . . . : 238060969
    DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1A-39-2B-4D-30-85-A9-AD-07-81
    DNS Servers . . . . . . . . . . . : 217.32.171.21
    213.120.234.30
    NetBIOS over Tcpip. . . . . . . . : Enabled
    Ethernet adapter VirtualBox Host-Only Network:
    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : VirtualBox Host-Only Ethernet Adapter
    Physical Address. . . . . . . . . : 08-00-27-00-28-56
    DHCP Enabled. . . . . . . . . . . : No
    Autoconfiguration Enabled . . . . : Yes
    Link-local IPv6 Address . . . . . : fe80::8d2d:7418:381b:8dc0%15(Preferred)
    IPv4 Address. . . . . . . . . . . : 192.168.56.1(Preferred)
    Subnet Mask . . . . . . . . . . . : 255.255.255.0
    Default Gateway . . . . . . . . . :
    DHCPv6 IAID . . . . . . . . . . . : 336068647
    DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1A-39-2B-4D-30-85-A9-AD-07-81
    DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
    fec0:0:0:ffff::2%1
    fec0:0:0:ffff::3%1
    NetBIOS over Tcpip. . . . . . . . : Enabled
    Tunnel adapter isatap.{486D4DCC-9CB7-417E-A796-596E0E6B1D54}:
    Media State . . . . . . . . . . . : Media disconnected
    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : Microsoft ISATAP Adapter
    Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
    DHCP Enabled. . . . . . . . . . . : No
    Autoconfiguration Enabled . . . . : Yes
    Tunnel adapter Teredo Tunneling Pseudo-Interface:
    Media State . . . . . . . . . . . : Media disconnected
    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
    Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
    DHCP Enabled. . . . . . . . . . . : No
    Autoconfiguration Enabled . . . . : Yes
    Tunnel adapter isatap.{67455999-75A5-436E-9EAC-12B093363132}:
    Media State . . . . . . . . . . . : Media disconnected
    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
    Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
    DHCP Enabled. . . . . . . . . . . : No
    Autoconfiguration Enabled . . . . : Yes
    C:\Users\G>
    Any ideas where to look, or what other info to provide for any assistance?
    Many thanks in advance.

    Hi,
    This has just happened again, here is the content of the netstat results as requested...
    If I kill the VirtualBox virtual machines, it starts working again. It is as if there are no ports left, but I am not occupying that many? Surely Windows 7 can cope with this?
    I feel I am missing something important, but cannot put my finger on it...
    Further below, I have re-run the netstat command AFTER I have closed the VirtualBox machines and the system works OK.
    netstat results DURING ISSUE:
    Active Connections
      Proto  Local Address          Foreign Address        State           PID
      TCP    0.0.0.0:21             0.0.0.0:0              LISTENING       1444
     [FileZilla Server.exe]
      TCP    0.0.0.0:25             0.0.0.0:0              LISTENING       1692
     [MESMTPC.EXE]
      TCP    0.0.0.0:80             0.0.0.0:0              LISTENING       4
     Can not obtain ownership information
      TCP    0.0.0.0:110            0.0.0.0:0              LISTENING       1660
     [MEPOPS.EXE]
      TCP    0.0.0.0:135            0.0.0.0:0              LISTENING       752
      RpcSs
     [svchost.exe]
      TCP    0.0.0.0:143            0.0.0.0:0              LISTENING       1524
     [MEIMAPS.exe]
      TCP    0.0.0.0:445            0.0.0.0:0              LISTENING       4
     Can not obtain ownership information
      TCP    0.0.0.0:1221           0.0.0.0:0              LISTENING       4796
     [VirtualBox.exe]
      TCP    0.0.0.0:2199           0.0.0.0:0              LISTENING       4820
     [VirtualBox.exe]
      TCP    0.0.0.0:3306           0.0.0.0:0              LISTENING       1756
     [mysqld.exe]
      TCP    0.0.0.0:3389           0.0.0.0:0              LISTENING       1104
      CryptSvc
     [svchost.exe]
      TCP    0.0.0.0:6901           0.0.0.0:0              LISTENING       4636
     [WinVNC.exe]
      TCP    0.0.0.0:6901           0.0.0.0:0              LISTENING       4636
     [WinVNC.exe]
      TCP    0.0.0.0:8300           0.0.0.0:0              LISTENING       3464
     [sc_serv.exe]
      TCP    0.0.0.0:8301           0.0.0.0:0              LISTENING       3464
     [sc_serv.exe]
      TCP    0.0.0.0:8360           0.0.0.0:0              LISTENING       3080
     [sc_serv.exe]
      TCP    0.0.0.0:8361           0.0.0.0:0              LISTENING       3080
     [sc_serv.exe]
      TCP    0.0.0.0:9022           0.0.0.0:0              LISTENING       4804
     [VirtualBox.exe]
      TCP    0.0.0.0:9023           0.0.0.0:0              LISTENING       4804
     [VirtualBox.exe]
      TCP    0.0.0.0:9080           0.0.0.0:0              LISTENING       4804
     [VirtualBox.exe]
      TCP    0.0.0.0:10001          0.0.0.0:0              LISTENING       4828
     [VirtualBox.exe]
      TCP    0.0.0.0:10002          0.0.0.0:0              LISTENING       4828
     [VirtualBox.exe]
      TCP    0.0.0.0:10003          0.0.0.0:0              LISTENING       4828
     [VirtualBox.exe]
      TCP    0.0.0.0:10011          0.0.0.0:0              LISTENING       4780
     [VirtualBox.exe]
      TCP    0.0.0.0:10012          0.0.0.0:0              LISTENING       4780
     [VirtualBox.exe]
      TCP    0.0.0.0:10013          0.0.0.0:0              LISTENING       4780
     [VirtualBox.exe]
      TCP    0.0.0.0:25566          0.0.0.0:0              LISTENING       3648
     [TerrariaServer.exe]
      TCP    0.0.0.0:30001          0.0.0.0:0              LISTENING       4788
     [VirtualBox.exe]
      TCP    0.0.0.0:30002          0.0.0.0:0              LISTENING       4788
     [VirtualBox.exe]
      TCP    0.0.0.0:30003          0.0.0.0:0              LISTENING       4788
     [VirtualBox.exe]
      TCP    0.0.0.0:30004          0.0.0.0:0              LISTENING       4788
     [VirtualBox.exe]
      TCP    0.0.0.0:30005          0.0.0.0:0              LISTENING       4788
     [VirtualBox.exe]
      TCP    0.0.0.0:30006          0.0.0.0:0              LISTENING       4788
     [VirtualBox.exe]
      TCP    0.0.0.0:30007          0.0.0.0:0              LISTENING       4788
     [VirtualBox.exe]
      TCP    0.0.0.0:30020          0.0.0.0:0              LISTENING       4788
     [VirtualBox.exe]
      TCP    0.0.0.0:30021          0.0.0.0:0              LISTENING       4788
     [VirtualBox.exe]
      TCP    0.0.0.0:30039          0.0.0.0:0              LISTENING       4788
     [VirtualBox.exe]
      TCP    0.0.0.0:30080          0.0.0.0:0              LISTENING       4788
     [VirtualBox.exe]
      TCP    0.0.0.0:30081          0.0.0.0:0              LISTENING       4788
     [VirtualBox.exe]
      TCP    0.0.0.0:30082          0.0.0.0:0              LISTENING       4788
     [VirtualBox.exe]
      TCP    0.0.0.0:30083          0.0.0.0:0              LISTENING       4788
     [VirtualBox.exe]
      TCP    0.0.0.0:30084          0.0.0.0:0              LISTENING       4788
     [VirtualBox.exe]
      TCP    0.0.0.0:30085          0.0.0.0:0              LISTENING       4788
     [VirtualBox.exe]
      TCP    0.0.0.0:30086          0.0.0.0:0              LISTENING       4788
     [VirtualBox.exe]
      TCP    0.0.0.0:30087          0.0.0.0:0              LISTENING       4788
     [VirtualBox.exe]
      TCP    0.0.0.0:30088          0.0.0.0:0              LISTENING       4788
     [VirtualBox.exe]
      TCP    0.0.0.0:30089          0.0.0.0:0              LISTENING       4788
     [VirtualBox.exe]
      TCP    0.0.0.0:30090          0.0.0.0:0              LISTENING       4788
     [VirtualBox.exe]
      TCP    0.0.0.0:30091          0.0.0.0:0              LISTENING       4788
     [VirtualBox.exe]
      TCP    0.0.0.0:30092          0.0.0.0:0              LISTENING       4788
     [VirtualBox.exe]
      TCP    0.0.0.0:30093          0.0.0.0:0              LISTENING       4788
     [VirtualBox.exe]
      TCP    0.0.0.0:30094          0.0.0.0:0              LISTENING       4788
     [VirtualBox.exe]
      TCP    0.0.0.0:30095          0.0.0.0:0              LISTENING       4788
     [VirtualBox.exe]
      TCP    0.0.0.0:30096          0.0.0.0:0              LISTENING       4788
     [VirtualBox.exe]
      TCP    0.0.0.0:30097          0.0.0.0:0              LISTENING       4788
     [VirtualBox.exe]
      TCP    0.0.0.0:30098          0.0.0.0:0              LISTENING       4788
     [VirtualBox.exe]
      TCP    0.0.0.0:30099          0.0.0.0:0              LISTENING       4788
     [VirtualBox.exe]
      TCP    0.0.0.0:30101          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30102          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30103          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30104          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30105          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30106          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30107          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30108          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30109          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30110          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30111          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30112          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30113          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30114          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30115          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30116          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30117          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30118          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30119          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30120          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30121          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30139          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30180          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30181          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30182          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30183          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30184          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30185          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30186          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30187          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30188          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30189          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30190          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30191          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30192          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30193          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30194          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30195          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30196          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30197          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30198          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30199          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30201          0.0.0.0:0              LISTENING       4796
     [VirtualBox.exe]
      TCP    0.0.0.0:30239          0.0.0.0:0              LISTENING       4796
     [VirtualBox.exe]
      TCP    0.0.0.0:33306          0.0.0.0:0              LISTENING       4796
     [VirtualBox.exe]
      TCP    0.0.0.0:49152          0.0.0.0:0              LISTENING       440
     [wininit.exe]
      TCP    0.0.0.0:49153          0.0.0.0:0              LISTENING       880
      eventlog
     [svchost.exe]
      TCP    0.0.0.0:49154          0.0.0.0:0              LISTENING       1000
      Schedule
     [svchost.exe]
      TCP    0.0.0.0:49156          0.0.0.0:0              LISTENING       508
     [lsass.exe]
      TCP    0.0.0.0:49157          0.0.0.0:0              LISTENING       500
     [services.exe]
      TCP    0.0.0.0:49158          0.0.0.0:0              LISTENING       3048
      PolicyAgent
     [svchost.exe]
      TCP    127.0.0.1:8361         127.0.0.1:49364        ESTABLISHED     3080
     [sc_serv.exe]
      TCP    127.0.0.1:14147        0.0.0.0:0              LISTENING       1444
     [FileZilla Server.exe]
      TCP    127.0.0.1:14147        127.0.0.1:49162        ESTABLISHED     1444
     [FileZilla Server.exe]
      TCP    127.0.0.1:49162        127.0.0.1:14147        ESTABLISHED     3156
     [FileZilla Server Interface.exe]
      TCP    127.0.0.1:49212        127.0.0.1:49213        ESTABLISHED     4288
     [java.exe]
      TCP    127.0.0.1:49213        127.0.0.1:49212        ESTABLISHED     4288
     [java.exe]
      TCP    127.0.0.1:49214        127.0.0.1:49215        ESTABLISHED     4288
     [java.exe]
      TCP    127.0.0.1:49215        127.0.0.1:49214        ESTABLISHED     4288
     [java.exe]
      TCP    127.0.0.1:49216        127.0.0.1:49217        ESTABLISHED     4288
     [java.exe]
      TCP    127.0.0.1:49217        127.0.0.1:49216        ESTABLISHED     4288
     [java.exe]
      TCP    127.0.0.1:49218        127.0.0.1:49219        ESTABLISHED     4288
     [java.exe]
      TCP    127.0.0.1:49219        127.0.0.1:49218        ESTABLISHED     4288
     [java.exe]
      TCP    127.0.0.1:49220        127.0.0.1:49221        ESTABLISHED     4288
     [java.exe]
      TCP    127.0.0.1:49221        127.0.0.1:49220        ESTABLISHED     4288
     [java.exe]
      TCP    127.0.0.1:49222        127.0.0.1:49223        ESTABLISHED     4288
     [java.exe]
      TCP    127.0.0.1:49223        127.0.0.1:49222        ESTABLISHED     4288
     [java.exe]
      TCP    127.0.0.1:49224        127.0.0.1:49225        ESTABLISHED     4288
     [java.exe]
      TCP    127.0.0.1:49225        127.0.0.1:49224        ESTABLISHED     4288
     [java.exe]
      TCP    127.0.0.1:49226        127.0.0.1:49227        ESTABLISHED     4288
     [java.exe]
      TCP    127.0.0.1:49227        127.0.0.1:49226        ESTABLISHED     4288
     [java.exe]
      TCP    127.0.0.1:49364        127.0.0.1:8361         ESTABLISHED     3100
     [Instore_Radioboss.exe]
      TCP    192.168.1.87:139       0.0.0.0:0              LISTENING       4
     Can not obtain ownership information
      TCP    192.168.1.87:3389      217.156.134.12:22971   ESTABLISHED     1104
      CryptSvc
     [svchost.exe]
      TCP    192.168.1.87:8360      81.148.248.221:1026    ESTABLISHED     3080
     [sc_serv.exe]
      TCP    192.168.1.87:25565     0.0.0.0:0              LISTENING       4288
     [java.exe]
      TCP    192.168.1.87:50644     37.139.0.151:8233      ESTABLISHED     4796
     [VirtualBox.exe]
      TCP    192.168.1.87:51019     81.27.96.46:21         TIME_WAIT       0
      TCP    192.168.1.87:53126     192.168.1.86:445       ESTABLISHED     4
     Can not obtain ownership information
      TCP    192.168.1.87:60462     192.168.1.86:445       CLOSE_WAIT      4
     Can not obtain ownership information
      TCP    192.168.1.87:65029     37.139.0.151:8231      ESTABLISHED     4796
     [VirtualBox.exe]
      TCP    192.168.56.1:139       0.0.0.0:0              LISTENING       4
     Can not obtain ownership information
      TCP    [::]:21                [::]:0                 LISTENING      
    1444
     [FileZilla Server.exe]
      TCP    [::]:25                [::]:0                 LISTENING      
    1692
     [MESMTPC.EXE]
      TCP    [::]:80                [::]:0                 LISTENING      
    4
     Can not obtain ownership information
      TCP    [::]:135               [::]:0                 LISTENING      
    752
      RpcSs
     [svchost.exe]
      TCP    [::]:445               [::]:0                 LISTENING      
    4
     Can not obtain ownership information
      TCP    [::]:3306              [::]:0                 LISTENING      
    1756
     [mysqld.exe]
      TCP    [::]:3389              [::]:0                 LISTENING      
    1104
      CryptSvc
     [svchost.exe]
      TCP    [::]:30239             [::]:0                 LISTENING      
    4796
     [VirtualBox.exe]
      TCP    [::]:49152             [::]:0                 LISTENING      
    440
     [wininit.exe]
      TCP    [::]:49153             [::]:0                 LISTENING      
    880
      eventlog
     [svchost.exe]
      TCP    [::]:49154             [::]:0                 LISTENING      
    1000
      Schedule
     [svchost.exe]
      TCP    [::]:49156             [::]:0                 LISTENING      
    508
     [lsass.exe]
      TCP    [::]:49157             [::]:0                 LISTENING      
    500
     [services.exe]
      TCP    [::]:49158             [::]:0                 LISTENING      
    3048
      PolicyAgent
     [svchost.exe]
      TCP    [::1]:14147            [::]:0                 LISTENING       1444
     [FileZilla Server.exe]
      UDP    0.0.0.0:123            *:*                                   
    964
      W32Time
     [svchost.exe]
      UDP    0.0.0.0:500            *:*                                   
    1000
      IKEEXT
     [svchost.exe]
      UDP    0.0.0.0:3702           *:*                                   
    964
      EventSystem
     [svchost.exe]
      UDP    0.0.0.0:3702           *:*                                   
    964
      EventSystem
     [svchost.exe]
      UDP    0.0.0.0:4500           *:*                                   
    1000
      IKEEXT
     [svchost.exe]
      UDP    0.0.0.0:5355           *:*                                   
    1104
      Dnscache
     [svchost.exe]
      UDP    0.0.0.0:53274          *:*                                   
    4780
     [VirtualBox.exe]
      UDP    0.0.0.0:53727          *:*                                   
    4788
     [VirtualBox.exe]
      UDP    0.0.0.0:54111          *:*                                   
    4828
     [VirtualBox.exe]
      UDP    0.0.0.0:54112          *:*                                   
    4828
     [VirtualBox.exe]
      UDP    0.0.0.0:54113          *:*                                   
    4780
     [VirtualBox.exe]
      UDP    0.0.0.0:55421          *:*                                   
    964
      EventSystem
     [svchost.exe]
      UDP    0.0.0.0:58596          *:*                                   
    964
      EventSystem
     [svchost.exe]
      UDP    0.0.0.0:59838          *:*                                   
    4812
     [VirtualBox.exe]
      UDP    0.0.0.0:62498          *:*                                   
    4796
     [VirtualBox.exe]
      UDP    127.0.0.1:1900         *:*                                   
    4172
      SSDPSRV
     [svchost.exe]
      UDP    127.0.0.1:55045        *:*                                   
    4172
      SSDPSRV
     [svchost.exe]
      UDP    192.168.1.87:137       *:*                                   
    4
     Can not obtain ownership information
      UDP    192.168.1.87:138       *:*                                   
    4
     Can not obtain ownership information
      UDP    192.168.1.87:1900      *:*                                   
    4172
      SSDPSRV
     [svchost.exe]
      UDP    192.168.1.87:55043     *:*                                   
    4172
      SSDPSRV
     [svchost.exe]
      UDP    192.168.56.1:137       *:*                                   
    4
     Can not obtain ownership information
      UDP    192.168.56.1:138       *:*                                   
    4
     Can not obtain ownership information
      UDP    192.168.56.1:1900      *:*                                   
    4172
      SSDPSRV
     [svchost.exe]
      UDP    192.168.56.1:55044     *:*                                   
    4172
      SSDPSRV
     [svchost.exe]
      UDP    [::]:123               *:*                                   
    964
      W32Time
     [svchost.exe]
      UDP    [::]:500               *:*                                   
    1000
      IKEEXT
     [svchost.exe]
      UDP    [::]:3702              *:*                                   
    964
      EventSystem
     [svchost.exe]
      UDP    [::]:3702              *:*                                   
    964
      EventSystem
     [svchost.exe]
      UDP    [::]:4500              *:*                                   
    1000
      IKEEXT
     [svchost.exe]
      UDP    [::]:5355              *:*                                   
    1104
      Dnscache
     [svchost.exe]
      UDP    [::]:55422             *:*                                   
    964
      EventSystem
     [svchost.exe]
      UDP    [::]:58597             *:*                                   
    964
      EventSystem
     [svchost.exe]
      UDP    [::1]:1900             *:*                                   
    4172
      SSDPSRV
     [svchost.exe]
      UDP    [::1]:55042            *:*                                   
    4172
      SSDPSRV
     [svchost.exe]
      UDP    [fe80::59f:484a:827f:42ba%11]:1900  *:*                                   
    4172
      SSDPSRV
     [svchost.exe]
      UDP    [fe80::59f:484a:827f:42ba%11]:55040  *:*                                   
    4172
      SSDPSRV
     [svchost.exe]
      UDP    [fe80::11a6:2283:bc40:c0cb%16]:1900  *:*                                   
    4172
      SSDPSRV
     [svchost.exe]
      UDP    [fe80::11a6:2283:bc40:c0cb%16]:55041  *:*                                   
    4172
      SSDPSRV
     [svchost.exe]

  • Issue with instant ringback when using sip trunk to SP

    Hi all,
    We use CUCM 8.0.2.
    We have a SIP trunk to a SP connected via one of our Cisco 2911 routers configured as a CUBE.
    Cisco IOS Software, C2900 Software (C2900-UNIVERSALK9-M), Version 15.0(1)M3, RELEASE SOFTWARE (fc2)
    c2900-universalk9-mz.SPA.150-1.M3.bin
    Cisco CISCO2911/K9 (revision 1.0)
    Technology Package License Information for Module:'c2900'
    Technology Technology-package
                      Current       Type
    ipbase        ipbasek9      Permanent
    security      securityk9    Permanent
    uc              uck9            Permanent
    data           None            None
    We also have several ISDN lines that run out via various Cisco routers configured as H323 gateways.
    We use 7945 and CIPC for our phones.
    We're having an issue with calls going via the SIP trunk where we hear ringing instantly after dialling - but before the actual device at the other end starts ringing (considerable difference).
    Using the SIP trunk: If I make a call to my mobile phone - I hear ringing instantly - about 3 rings before my mobile phone actually starts ringing - undesireable.
    Using H323 gateway: If I make a call to my mobile phone - I hear silence for a bit - then ringing when the mobile starts ringing - desired.
    Using SIP trunk: If I make a call to a landline that is ready - it rings instantly for at least 1 ring - before the actual phone I'm calling starts ringing - undesireable.
    Using H323 gateway: There is a momentary pause before hearing ringing on my phone and the phone I dialled - desired.
    Using SIP trunk: If I make a call to a landline that is off-hook (with no call-waiting/etc.) - it rings once and then returns the busy signal (the worst issue) - undesireable.
    Using H323 gateway: There is a momentary pause before hearing busy signal - desired.
    Phone to phone internally (same network): Operates as expected (instantly rings locally and on the phone I'm calling). Between phones that utilise the SIP trunk and phones that utilise the H323 gateways within the same network - communication is instant and as expected.
    Any ideas why this happens and how to stop it?
    I want it to not ring until the situation is known and that it can provide the appropriate feedback (ringing/busy/etc.).
    Some possibly relevant config (note that there is a known bug with this IOS that meant I had to declare the codec in each dial-peer as the voice class would not work):
    voice service voip
    address-hiding
    mode border-element
    allow-connections sip to sip
    sip
      bind control source-interface GigabitEthernet0/0
      bind media source-interface GigabitEthernet0/0
      header-passing error-passthru
      early-offer forced
      midcall-signaling passthru
    interface GigabitEthernet0/0
    ip address x.x.x.x 255.255.255.252
    ip access-group acl.SIP-IN in
    no ip redirects
    no ip unreachables
    ip verify unicast reverse-path
    ip virtual-reassembly
    duplex full
    speed 100
    no cdp enable
    gateway
    timer receive-rtp 1200
    sip-ua
    connection-reuse
    gatekeeper
    shutdown
    dial-peer voice 1 voip
    description *** INBOUND CALLS FROM CARRIER ***
    translation-profile incoming SIPTRUNK-INCOMING
    session protocol sipv2
    incoming called-number #blah blah#
    dtmf-relay rtp-nte
    codec g711alaw
    ip qos dscp cs5 media
    no vad
    dial-peer voice 61 voip
    description **** WA, SA AND NT NUMBERS ****
    destination-pattern 0[8]........
    session protocol sipv2
    session target ipv4:<MY SP's SIP SERVER>
    incoming called-number 0[8]........
    dtmf-relay rtp-nte
    codec g711alaw
    ip qos dscp cs5 media
    no vad
    dial-peer voice 81 voip
    description **** MOBILE NUMBERS ****
    destination-pattern 0[4]........
    session protocol sipv2
    session target ipv4:<MY SP's SIP SERVER>
    incoming called-number 0[4]........
    dtmf-relay rtp-nte
    codec g711alaw
    ip qos dscp cs5 media
    no vad
    dial-peer voice 500 voip
    description *** INBOUND SIP TRUNK TO CUCM PUB ***
    translation-profile outgoing SIPTRUNK-CALLING-ADD-0
    preference 1
    destination-pattern 5[12]..
    session protocol sipv2
    session target ipv4:<OUR CUCM PUBLISHER IP>
    dtmf-relay rtp-nte
    codec g711alaw
    ip qos dscp cs5 media
    no vad
    Any help or a point in the right direction would be greatly appreciated.
    Cheers,
    Brett

    I ended up resolving this issue as follows:
    In CUCM, under Device > Device Settings > SIP Profile.
    I modifed the profile relevant to my SIP trunk, under the "Trunk Specific Configuration", I set "SIP Rel1XX Options" from "Disabled" to "Send PRACK if 1xx Contains SDP".
    Now, I get the expected delay before hearing ringback.
    Solved!

Maybe you are looking for