Wednesday, 29 August 2018
Tuesday, 28 August 2018
How to use BAT to add user devidce profile (UDP) on CUMC v11.5
- Download bat_xxxxxx.xlt from CUCM
- Select the User Device Profiles tab
- Click on Create File Format and confirm that you wish to overwrite the existing CSV format after selecting the required fields for UDP profile - this will re-create the file with all selected fields see the fields I have used.
- Next populate the form and click on export to BAT Format - this will generate the file we need to import the UDP profiles, it will look something like that:
DEVICE PROFILE NAME,DESCRIPTION,PHONE BUTTON TEMPLATE,SOFTKEY TEMPLATE,PRIVACY,SINGLE BUTTON BARGE,ALWAYS USE PRIME LINE,ALWAYS USE PRIME LINE FOR VOICE MESSAGE,DND OPTION,MLPP INDICATION,MLPP PREEMPTION
UDP_Test_User_1,UDP_Test_User_1,Standard 7911,Standard Comp 7911 User,Default,Off,Default,Default,Use Common Phone Profile Setting,Default,Default
UDP_Test_User_1,UDP_Test_User_1,Standard 7911,Standard Comp 7911 User,Default,Off,Default,Default,Use Common Phone Profile Setting,Default,Default
- Now upload the file to CUCM>Bulk Admin>Upload files as Insert UDP - Specific Details
- Next Select Bulk Admin>User Device Profiles> Insert UDP, select Insert Specific details and select the file that you just uploaded and use the appropriate template for your phone. My template looks as below. Once you run this job you should have a list of users dev profiles as in the file.
Wednesday, 24 January 2018
How to remove ospf route from HP switch
HP 2950's
Let's say you enter a wrong ip route on a switch and you want to remove it.
Of course first thing you would try will be the no ip route command and job done,but what if it doesn't work. Well it took me a while to click that it doesn't because I'm trying to do it on the wrong switch.
Let's say you enter a wrong ip route on a switch and you want to remove it.
Of course first thing you would try will be the no ip route command and job done,but what if it doesn't work. Well it took me a while to click that it doesn't because I'm trying to do it on the wrong switch.
Destination Gateway VLAN Type Sub-Type Metric Dist
XXX.27.0.161/32 XXX.28.248.38 100 ospf External2 10 110
The sub-type of the route is showing as External2 so based on that work out from which switch is the route coming from.
#show ip ospf external-link-state
This command will give you the router id IP
#show ip ospf link-state router-id ip addr
This will show you all the associated networks with that particular router-id
You can then login to all the switches on the list and check which one has the static route you trying to remove . Once you got the route just use the standard command
#no ip route ..... and the rest
Now it works
Now it works
Thursday, 5 October 2017
Fortigate Policy based IPSEC
How to NAT traffic over policy based IPSEC VPN
http://kb.fortinet.com/kb/viewContent.do?externalId=FD33638
Env:PC>>HQ Fortigate 1000C>>IPSEC VPN>>Site 1Fortigate300C>>Some service
It has been one of those weeks where I've been scratching my head for a week to set some new service on the corporate firewall.
On first glance it looks straight forward but the traffic is supposed to exit on different to the default Internet traffic interface.
Step1
- Set up the VPN between the HQ and Site 1 and add P2 ranges
- Ensure that Policy has : #set inbound en | #set outbound en
Result: I could see the traffic from Site1 fortigate entering the IPSEC VPN to HQ FG
diagnose debug disable
diagnose debug reset
diagnose debug flow show console enable
diagnose debug flow filter addr 10.10.10.10
diagnose debug flow trace start 100
diagnose debug console timestamp enable
diagnose debug enable
Step 2
- now the issue here was the interesting traffic from the vpn was being drop by policy 0( no match)
To get around this I created new policy for all traffic that is coming from the remote destination to the Site1 remote network and set it to use the IPSEC tunnel to the remote site I set up earlier.
Traffic is allowed to be initiated from the remote end on the tunnel.
Now the crucial part here was to make sure that NAT is enabled for that particular policy:
#conf fir pol
#edit 1234
#set natinbound en
#set outbound dis
#set natip 90.90.90.90 255.255.55.255 (IP of the gw the traffic will be coming from the remote party)
.. and that did the trick
No ringback tone on H323 Voice Gateway
Env:
CUCM 8.6
Cisco 2921
Issue: No ring back tone on outbound calls
Solution:
- Find the outbound dial-peer and add:
#tone ringback alert-no-PI
CUCM 8.6
Cisco 2921
Issue: No ring back tone on outbound calls
Solution:
- Find the outbound dial-peer and add:
#tone ringback alert-no-PI
Monday, 3 July 2017
ISDN error codes
ISDN error codes
000 0010 2 No route to specified transit network
000 0011 3 No route to destination
000 0110 6 Channel Unacceptable
000 0111 7 Call awarded and being delivered in
an established channel
001 0000 16 Normal call clearing
001 0001 17 User busy
001 0010 18 No user responding
001 0011 19 No answer from user (user alerted)
001 0101 21 Call Rejected
001 0110 22 Number changed
001 1010 26 Non selected user clearing
001 1011 27 Destination out of order
001 1100 28 Invalid number format
001 1101 29 facility rejected
001 1110 30 Response to status enquiry
001 1111 31 Normal, unspecified
010 0010 34 No circuit/channel available
010 0110 38 Network out of order
010 1001 41 Temporary failure
010 1010 42 Switching equipment congestion
010 1011 43 Access information discarded
010 1100 44 Requested circuit/channel not available
010 1101 45 Pre-empted
010 1111 47 Resources unavailable, unspecified
011 0001 49 Quality of service unavailable
011 0010 50 Requested facility not subscribed
011 0100 52 Outgoing calls barred
011 0110 54 Incoming calls barred
011 1001 57 Bearer capability not authorised
011 1010 58 Bearer capability not presently available
011 1111 63 Service or option not available, unspecified
100 0001 65 Bearer capability not implemented
100 0010 66 Channel type not implemented
100 0101 69 Requested facility not implemented
100 0110 70 Only restricted digital information
bearer capability is available
100 1111 79 Service or option not implemented, unspecified
101 0001 81 Invalid call reference value
101 0010 82 Identified channel does not exist
101 0011 83 A suspended call exists, but this call identity does not
101 0100 84 Call identity in use
101 0101 85 No call suspended
101 0110 86 Call having the requested call identity has been cleared
101 1000 88 Incompatible destination
101 1011 91 Invalid transit network selection
101 1111 95 Invalid message, unspecified
110 0000 96 Mandatory information element is missing
110 0001 97 Message type nonexistent or not implemented
110 0010 98 Message not compatible with call state or
message type nonexistent or not implemented
110 0011 99 Information element nonexistent or not implemented
110 0100 100 Invalid information element contents
110 0101 101 Message not compatible with call state
110 0110 102 Recovery on timer expiry
110 1111 111 Protocol error, unspecified
111 1111 127 Interworking, unspecified
Thursday, 25 May 2017
Change Telnet to SSH on Cisco rouer
p domain name yourdomain.co.uk
crypto key generate rsa modulus 2048
line vty 0 4
transport input ssh
crypto key generate rsa modulus 2048
line vty 0 4
transport input ssh
Subscribe to:
Posts (Atom)