Hi Dave,
Thank you for understanding what I needed help with and offering great
suggestions.
I have basic config I have attached, just wondering if I have missed anything
or need to add or move anything?
I really appreciate everyone help.
Thanks
hamu
________________________________
From: cisco-voip <cisco-voip-boun...@puck.nether.net> on behalf of Dave Goodwin
<dave.good...@december.net>
Sent: Thursday, July 27, 2017 9:24 PM
To: Scott Voll
Cc: cisco-voip voyp list
Subject: Re: [cisco-voip] Configure 3845 router for 911 calls.
There are several ways to accomplish this on the UCM side. I would consider
creating a RG for Site A GW and a RG for Site B GW, have one 911 route pattern
accessible via the main CSS that is routed to a RL with Standard Local Route
Group. Then use the Device Pool configurations for Site A and Site B to assign
the Local Route Group. In any case, all of the UCM configurations are valid and
meet the stated goals.
What I think the OP is asking for is help configuring the actual IOS GW with
FXO ports to route the calls. Hamu, configuration options for an IOS voice
gateway are quite extensive. Everyone has their opinion on which of the
available options are "best," and I'm not going to try to convince you which
approach (H.323, MGCP, SIP protocols) is best. I would say you might consider
calling Cisco TAC and asking for help with this very basic initial
configuration of a voice gateway... but I doubt you'll get help on your 3845
since that model's end of support date has passed. Instead, I'll just give you
a link I saw from a simple Google search that will get you started down one of
those roads (SIP). Hopefully this will give you what you need to modify it for
your specific scenario and get it working. Good luck!
http://ucpros.net/cisco-sip-gateway-configuration/
Cisco SIP Gateway configuration: The Ultimate Guide -
UCPros<http://ucpros.net/cisco-sip-gateway-configuration/>
ucpros.net
SIP is Cisco's recommended protocol for Voice Gateway & CUCM interconnection.
This is the most comprehensive guide for Cisco SIP Gateway configuration.
On Thu, Jul 27, 2017 at 6:29 PM, Scott Voll
<svoll.v...@gmail.com<mailto:svoll.v...@gmail.com>> wrote:
I agree with Neal,
but I would use one partition for each site for 911, then a third partition for
everything else, then, put the correct 911 partition in the site CSS and use
the third partition in both CSS. Save a lot of time recreating RP for the
other stuff.... Guess it depends on how many RP you have..... we have hundreds.
Scott
On Thu, Jul 27, 2017 at 3:13 PM, Haas, Neal
<nh...@co.fresno.ca.us<mailto:nh...@co.fresno.ca.us>> wrote:
Everything is done in the CUCM.
Pots are configured with MGCP.
Create New Partition. (site Name)
Assign 911 Route for site A to Site Partition 1
Assign 911 Route for Site B to Site Partition 1
Assign all other Routes to both Partitions.
Only 911 calls are treated different per site – if you do not take phones
between sites, you won’t have a problem. Two POTS lines per site is correct.
I don’t think I missed anything, it’s not hard to accomplish the separate 911
calls between PSAPS.
Neal
From: cisco-voip
[mailto:cisco-voip-boun...@puck.nether.net<mailto:cisco-voip-boun...@puck.nether.net>]
On Behalf Of Hamu Ebiso
Sent: Thursday, July 27, 2017 2:40 PM
To: Norton, Mike <mikenor...@pwsd76.ab.ca<mailto:mikenor...@pwsd76.ab.ca>>;
Subject: Re: [cisco-voip] Configure 3845 router for 911 calls.
Let me rephrase the questions with more understanding update after I talk to
Mike and few other people.
We have 2 locations. one is main building were everything reside and the second
building is remote building shared with someone else.
About 50 people reside at the secondary remote location. This people use main
locations CUCM over the WAN for calling. Remote location is about 25 minutes
from main building.
So if these people at remote location call 911, emergency responder will see
main building location not remote location where the call is residing.
Therefore we are tasked to put together plan to give users option to be able to
call 911 and show their true locations.
We are forced to find spare 3845 router to configure for this users for 911
call. below is what we have.
ordered 2 POT Lines,
have 3845 router
We have both FOX and FXS modules for POT Lines.
Amphenol Cable to connect to FOX and 110 block.
CUCM version: 11.0
The reason we ordered 2 POT lines instead of circuit is because they are cheap.
Circuit cost about $500 a month while POT line cost about $40 a line. Since
this router is only used for 911 call we don't want to spend that much money.
The question, has any one configured router for 911 and have basic config that
I can use for my config. Since I haven't done voice gateway configuration
before, I just need help with this.
Any help is greatly appreciated.
Thanks
Hamu
________________________________
From: Norton, Mike <mikenor...@pwsd76.ab.ca<mailto:mikenor...@pwsd76.ab.ca>>
Sent: Monday, July 24, 2017 3:58 PM
To: Hamu Ebiso
Subject: RE: Configure 3845 router for 911 call.
For the IP phones to be usable during WAN outage, you need something they can
register to. E.g. SRST or CME on the router, or else a CUCM server on-site.
The config you posted shows that this router already has T1 lines. You can send
911 calls to T1 lines, I don’t understand why you want to add analog POTS lines
if you already have T1s.
If you want more suggestions then perhaps take this conversation back on to the
mailing list, others besides me might be able to give you ideas.
-mn
From: Hamu Ebiso [mailto:hebiso2...@hotmail.com]
Sent: July 24, 2017 2:45 PM
To: Norton, Mike <mikenor...@pwsd76.ab.ca<mailto:mikenor...@pwsd76.ab.ca>>
Subject: Re: Configure 3845 router for 911 call.
Thank you Mike for following up!!
I Just clarified with person who gave me that project to put it together. That
person was not really familiar with voice staff just mentioned analog phones.
There is no analog phones here. These users have 7942 IP phones and the idea
was to user POT lines to call out to 911 if WAN connect down at the site. The
idea was, since these users are in some else's building, we need to find out
how to make them call out to 911 if WAN connection is down. Since I am not 100%
sure of how we can achieve this. I am ok with your suggestion how to achieve
this.
ordered 2 POT Lines,
have 3845 router
We have both FOX and FXS modules
Amphenol Cable.
thanks
Hamu
________________________________
From: Norton, Mike <mikenor...@pwsd76.ab.ca<mailto:mikenor...@pwsd76.ab.ca>>
Sent: Monday, July 24, 2017 3:26 PM
To: Hamu Ebiso
Subject: RE: Configure 3845 router for 911 call.
Hi Hamu, I don’t fully understand your call flow. POTS lines would normally
connect to an FXO card. In that case, the easiest way to handle incoming calls
is to do “connection plar xxxx” on the voice-port, where xxxx is the extension
number where you want to send the calls. But since you mention analog phones
then it is not clear to me exactly what you are trying to do.
Maybe take the conversation back to the mail list and give more explanation of
the call flow, might be able to get more help that way.
-mn
From: Hamu Ebiso [mailto:hebiso2...@hotmail.com]
Sent: July 21, 2017 5:49 PM
To: Norton, Mike <mikenor...@pwsd76.ab.ca<mailto:mikenor...@pwsd76.ab.ca>>
Subject: Re: Configure 3845 router for 911 call.
Thank you very much Mike. I really appreciate your help.
As I mentioned it before, These employees are residing in someone else's
building and using CUCM across WAN. The reason behind trying to use POT Lines
is, If WAN is done these employee will be able to use POT Lines from Analog
phones to call out.
One question is, if you can share command to setting how to send 911 calls to
reception or security desk.
I really appreciate your input and advise.
Thanks
Hamu
________________________________
From: Norton, Mike <mikenor...@pwsd76.ab.ca<mailto:mikenor...@pwsd76.ab.ca>>
Sent: Friday, July 21, 2017 5:43 PM
To: Hamu Ebiso; cisco-voip voyp list
Subject: RE: Configure 3845 router for 911 call.
Currently your config will send the 911 calls out the “Local” T1. Once you have
the POTS lines added, you will need to put your POTS ports into their own trunk
group and direct your outgoing dial-peers to the new trunk group instead of
“Local.”
You should do something with inbound calls that come in on the POTS lines. E.g.
if 911 calls you back, at bare minimum you should send the call to reception or
security desk.
For POTS lines you need an FXO card, not an FXS card. FXO is for connecting to
telco Offices, FXS is for connecting to analog telephone Sets. So FXS will not
do what you need.
You don’t have any SRST configured. Is your CUCM on-site? If CUCM is across the
WAN then you need to have something on-site that phones can register to when
the WAN is down (e.g. SRST, CME).
I don’t understand why you need the POTS lines? Why not send 911 calls out one
of the T1s that this router already has?
-mn
From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of Hamu
Ebiso
Sent: July 20, 2017 1:03 PM
To: cisco-voip voyp list
<cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>>
Subject: [cisco-voip] Configure 3845 router for 911 call.
Hi Everyone,
I need help with this configuration for 911 only.
back ground history, our company bought another company few years back. After
about 6 months, the deal fail apart. Within that 6 months employees moved
around to different building mixed. When separation started, leaders negotiated
so that we still provide professional service to the company that is separating
from us for 3 years. In that 2 years, all the assets and employees need to be
separated. There are about 50 employee of ours located in the building of the
company that is in the process of separating from us. We are in the process of
separated them from this company system but in the same building. We had done
all separation form phones to email server and etc. while in the process of
separating this employee we have run into issue with 911 if the site loose WAN
connection. I was tasked to figure out this. I am just wondering if anyone has
done this and help me.
below is the router I am try to configure.
3845 with EVM-HD-8FXS/DID module
ordered Amphenol cable to connect to 110 block
ordered 2 POT Lines
I need help configuring this router for 911 call. I have attached the config I
have and I am just wondering if I am missing anything. I haven't don't this
kind of configuration before and I need guidance.
Thank you very much!!
_______________________________________________
cisco-voip mailing list
cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip
_______________________________________________
cisco-voip mailing list
cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip
q7005voicegw01#sh inv
NAME: "3845 chassis", DESCR: "3845 chassis"
PID: CISCO3845 , VID: V01 , SN: xxxxxxxx
NAME: "c3845 Motherboard with Gigabit Ethernet on Slot 0", DESCR: "c3845
Motherboard with Gigabit Ethernet"
PID: CISCO3845-MB , VID: V06 , SN: FOC123128V4
NAME: "VWIC2-1MFT-T1/E1 - 1-Port RJ-48 Multiflex Trunk - T1/E1 on Slot 0
SubSlot 0", DESCR: "VWIC2-1MFT-T1/E1 - 1-Port RJ-48 Multiflex Trunk - T1/E1"
PID: VWIC2-1MFT-T1/E1 , VID: V01 , SN: FOC142038K1
NAME: "VWIC2-1MFT-T1/E1 - 1-Port RJ-48 Multiflex Trunk - T1/E1 on Slot 0
SubSlot 1", DESCR: "VWIC2-1MFT-T1/E1 - 1-Port RJ-48 Multiflex Trunk - T1/E1"
PID: VWIC2-1MFT-T1/E1 , VID: V01 , SN: FOC142039DQ
NAME: "PVDMII DSP SIMM with four DSPs on Slot 0 SubSlot 4", DESCR: "PVDMII DSP
SIMM with four DSPs"
PID: PVDM2-64 , VID: V01 , SN: FOC122929P9
NAME: "PVDMII DSP SIMM with four DSPs on Slot 0 SubSlot 5", DESCR: "PVDMII DSP
SIMM with four DSPs"
PID: PVDM2-64 , VID: V01 , SN: FOC122929GS
EVM-HD-8FXS/DID will be installed on this router.
q7005voicegw01#sh run
Building configuration...
Current configuration : 4421 bytes
!
version 15.1
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname q7007voipgw1
!
boot-start-marker
boot-end-marker
!
!
card type t1 0 0
card type t1 0 1
!
no aaa new-model
clock timezone MNT -7 0
clock summer-time MDT recurring
network-clock-participate wic 0
network-clock-participate wic 1
network-clock-select 1 T1 0/0/0
!
dot11 syslog
ip source-route
!
ip cef
!
!
!
!
ip domain name xxxx
ip name-server x.x.x.x
ip name-server x.x.x.x
no ipv6 cef
multilink bundle-name authenticated
!
!
!
isdn switch-type primary-ni
!
!
trunk group ANALOG
hunt-scheme sequential
translation-profile outgoing outbound
!
!
trunk group Local
hunt-scheme sequential
translation-profile outgoing outbound
!
!
trunk group LD
translation-profile outgoing outbound
!
voice-card 0
dspfarm
dsp services dspfarm
!
!
voice rtp send-recv
!
voice service voip
no ip address trusted authenticate
allow-connections sip to sip
sip
midcall-signaling passthru
!
voice class codec 1
codec preference 1 g711ulaw
!
!
!
!
voice translation-rule 1
rule 1 /\(.*\)/ /1\1/
!
voice translation-rule 10
rule 1 /^1\(.*\)/ /\1/
!
voice translation-rule 15
!
voice translation-rule 30
rule 1 /^911/ /911/
rule 2 /^9911/ /911/
rule 4 /^9\(011.*\)/ /\1/
rule 9 /^9\(.*\)/ /\1/
!
!
voice translation-profile Inbound
translate called 1
!
voice translation-profile Strip9
translate called 30
!
voice translation-profile block_profile
translate calling 15
!
voice translation-profile outbound
translate calling 10
!
!
crypto pki token default removal timeout 0
!
!
!
!
license udi pid CISCO3845-MB sn FOC123128V4
license accept end user agreement
archive
log config
hidekeys
!
!
controller T1 0/0/0
cablelength long 0db
pri-group timeslots 1-24
!
controller T1 0/1/0
cablelength long 0db
pri-group timeslots 1-24
!
ip ssh version 2
!
!
!
!
!
interface Loopback0
ip address 1.x.x.x 255.255.255.252
no shutdown
!
interface GigabitEthernet0/0
ip address x.x.x.x 255.255.255.252
no shutdown
duplex auto
speed auto
media-type rj45
!
interface GigabitEthernet0/1
ip address x.x.x.x 255.255.255.252
no shutdown
duplex auto
speed auto
media-type rj45
!
interface Serial0/0/0:23
no ip address
encapsulation hdlc
isdn switch-type primary-ni
isdn incoming-voice voice
trunk-group Local
no cdp enable
!
interface Serial0/1/0:23
no ip address
encapsulation hdlc
isdn switch-type primary-ni
isdn incoming-voice voice
trunk-group LD
no cdp enable
!
ip forward-protocol nd
!
!
no ip http server
no ip http secure-server
!
!
!
!
control-plane
!
!
voice-port 0/0/0:23
!
voice-port 0/1/0:23
!
!
!
mgcp profile default
!
!
dial-peer voice 1 pots
translation-profile incoming Inbound
call-block translation-profile incoming block_profile
call-block disconnect-cause incoming call-reject
incoming called-number .
direct-inward-dial
!
!
dial-peer voice 911 pots
trunkgroup ANALOG
description Services
translation-profile outgoing Strip9
destination-pattern 911
!
dial-peer voice 9911 pots
trunkgroup ANALOG
description Services
translation-profile outgoing Strip9
destination-pattern 9911
!
!
!
!
line con 0
line aux 0
line vty 0 4
login
transport preferred none
transport input ssh
transport output ssh
line vty 5 15
login
transport preferred none
transport input ssh
transport output ssh
!
scheduler allocate 20000 1000
end
_______________________________________________
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
