Hi Marcus, Would it be possible for you to post your working CME config? I've had this on a system where it has been configured to 5065 and was working for a week. Then Exchange goes ahead and recycles itself and restarts on port 5067. I understand this is normal operation of the service on Exchange. It should actually work by sending our calls to 5060, then Exchange will send 302 back to CME and instruct it to go back to the currently active port 5065 or 5067. I haven't played too much with this yet, but it didn't seem to work. I can work around with another dial peer pointing to 5067, but I'd rather get the 302 working properly. Not sure if you encountered this after you got it working? Cheers, Tim
... View more
Hey good stuff. Where did you get the via-port part? Just from cli or did you find some more info on connection-reuse command? Cheers, Tim Sent from Cisco Technical Support iPhone App
... View more
Interesting! I read that via only needs port if it is not default. I didn't see anything on source ports except for this.. http://www.ietf.org/rfc/rfc3581.txt That seems to say that with UDP, it is expected that you would reply to the Via port (in broadsoft case, not specified, so assuming 5060) - so it seems 12.4 would be in line with this. Did you check bug toolkit? It seems like something that would appear. Or maybe as a changed behaviour in release notes? There is the connection-reuse command. My understanding is this one should ensure the CUBE sends the replies from source port 5060. I cant find any docco about what it does to destination. I think this command is on in both your configs, as source is 5060. But it may also be interesting to see what wireshark says with this off. i.e. if it wasn't re-using a connection, maybe it would just send the reply straight to 5060. Sorry that probably doesn't really help too much. Cheers, Tim.
... View more
Hey mate, As chrysostomos1980 says below, 7.x is not supported in VM, but it is fine in lab. In fact people have been running CCM in labs since 4.x. I did have issues with 7.x once with not enough disk space allocated to VM - it installed but wouldn't function. You can check 7.1 specs for physical and make sure you match them. Personally I would go with 1 cpu, 4 GB RAM, 160 GB disk. Ensure you select RHEL 4 as guest OS. Also what hypervisor are you using? Also as chrysostomos1980 said you can just use one of the Cisco provided OVA's, but make sure you pick the profile that meets the minimum hardware specs for your selected version of 7.1. Cheers, Tim.
... View more
Hi, This is a pretty open question. First questions would be around what you are trying to achieve (some sort of security or segmentation for example) Anyway, here is a pretty simplistic overview. Let's say you want to introduce 2 new vlans and subnets - data and voice for example A pretty standard approach here would be to introduce a layer 3 switch into the internal network behind the PIX. (Of course there are other ways too) This device could be configured to both segment the network at layer 2 and then provide the layer 3 routing (inter vlan routing) between those networks. For a small network something like a 3750 switch could perform this function. Very rough example of 3750 style config ! Create the layer 2 vlan's vlan 101 name Data101 ! vlan 102 name Voice102 ! Enable IP routing ip routing ! Create the layer 3 vlan SVI's / interfaces interface vlan 101 description *** Data VLAN 101 *** ip address 10.1.101.0 255.255.255.0 interface vlan 102 description *** Voice VLAN 102 *** ip address 10.1.102.0 255.255.255.0 ! Create default route to pix ip route 0.0.0.0 0.0.0.0 10.1.101.254 ! Assign switch ports to be in the various vlans int g1/0/1 description *** PC on data vlan *** switchport access vlan 101 int g1/0/2 description *** Phone on voice vlan *** switchport access vlan 102 int g1/0/3 description *** PC and Phone - using say a Cisco phone that supports 802.1q *** switchport access vlan 101 switchport voice vlan 102 Your VPN tunnels may also need to be updated to ensure that the remote sites will encrypt traffic to all of the new subnets on your internal network. i.e. Typically updating ACL's. i.e. summary of 10.1.0.0 / 16 could cover everything behind the pix. You may need to update route on pix as well. By no means definitive, but maybe it gives you a basic idea. Cheers, Tim
... View more
I think I'd be tempted to just try the work around: configure "no ip cef" in the router, see if it will help configure " ip virtual-reassembly" on the interface which will have the incoming SIP INVITE If that works you know it is a fragmentation problem. I think in our case we upgraded to 15.2.1 T2. Sorry I dont have bug ID or more details. Cheers, Tim.
... View more
Hey mate, Tell us more about how you set up your VM environment? Machine specs etc. It sounds like install has not gone well. Cheers, Tim
... View more
Hey mate, I think if toll fraud prevention was the issue, you could see it kicking in by debugging ccapi voip inout But you are receiving the INVITE from the far end, so I dont think that is the issue. I've seen fragmentation problems with UDP Your SIP message looks the same, so that shouldn't be the change But perhaps the way IOS is handling the packet could be an issue Exactly what IOS are you running? Check out this article (search for IP CEF) and you will see a couple of recommendations. https://supportforums.cisco.com/thread/2154873 I think in most of these cases it is a good idea to open a ticket with the carrier as well. Ask them to check their logs and see if they are receiving your messages (and responding) External wireshark cap is always nice as well, if you havent tried this. Cheers, Tim
... View more
Sorry slight correction.. Tiberie Kirijas wrote: Thank you jsmcniel88 for the information. As I understood the concept, MP 8.5 with WebEx (even with the WebEx Node) still uses the Cloud not just for external meetings, also for internal meetings too. The Web Conferencing data is mixed in the Cloud. Just the Audio and MP Video is done on the Node (wheatear MCS or ASR). If it's WebEx video, than the video too gets mixed in the Cloud. Node for MCS mixes the Web Conferencing part only. If you have MeetingPlace, then this would mix your audio (although with 8.5 you can also have another audio provider attached to your WebEx site as well - i.e. WebEx audio - you simply select provider when scheduling) WebEx video is mixed in the cloud, unless you have node for ASR - I believe this can mix video on board. So with WebEx, MeetingPlace and Node for ASR you can have an internal meeting that does not hit the cloud. With Node for MCS you could do the same exlcuding WebEx video. Cheers, Tim.
... View more
Hi, Yes you can support multiple registrars, but only a limited number. I think 6 possibly. Are you sure you cant turn off registration for your trunks? If they are all internal sites maybe its not required. In this case there are also other options such as SME. Cheers, Tim Sent from Cisco Technical Support iPhone App
... View more
Also there is the little plastic clip that holds your handset on. Usually used for wall mount. If someone flipped these round when installing then they can get in the way. Probably unlikely for so many phones and users though. Does dialtone start and break with headset off hook if you use your finger on the hook switch? Sent from Cisco Technical Support iPhone App
... View more
Wow. If you pick up handset, listen for dialtone then place handset back on hook, does the line light go off? Are they using headsets / electronic hook switch or anything additional? Have you got any other models that work? You could check ccm trace or packet capture to see if phone is actually sending the on hook message when you put the handset down. Cheers, Tim Sent from Cisco Technical Support iPhone App
... View more
Ive had exactly the same issue with a 4.1 migration. Was extension mobility involved? BAT updating them in 4.1 while still logged in definitely makes it worse. So as already mentioned it seems DB updates occur but dont get loaded into actual CM routing tables. CM restart way to go. Ive also had issues with large BAT updates where the DBL service would ens up getting stuck. We used to limit updates to 50 devices at a time. On 4.1 Some BAT functions just peg cpus at 100 percent. Even on 7845. Cheers, Tim Sent from Cisco Technical Support iPhone App
... View more