[cisco-voip] Local call send out from SRST gatewayr when not inSRST mode

Sun Jul 22 09:40:38 EDT 2007

H323 definately has some advantages for number translations, but with 
partitions and calling search spaced you can accomplish the same thing for 
outbound calls.

----- Original Message ----- 
From: "Manoj Kalpage" <manoj.kalpage at gmail.com>
To: "Lelio Fulgenzi" <lelio at uoguelph.ca>
Cc: <cisco-voip at puck.nether.net>
Sent: Saturday, July 21, 2007 11:16 PM
Subject: Re: [cisco-voip] Local call send out from SRST gatewayr when not 
inSRST mode

>I have to use number translation at branch office as local numbers
> send out through SRST gateway. Because uses at remote office has main
> office area numbers so, when they call to their local numbers calling
> party phone should display branch office area number which allocated
> to SRST ISDN BRI lines. I think with H323 I can easily do this using
> translation at SRST gateway level. Are you agree with me?
>
>
> On 7/22/07, Lelio Fulgenzi <lelio at uoguelph.ca> wrote:
>> Yes, you still have to add the gateway either way. There are various
>> benefits for each one. I'm sure it's a little like MAC vs Windows. ;)
>>
>> The one benefit to H323 that I just came across after re-reading some 
>> CIPTUG
>> notes is that an MGCP gateway is controlled by one and only one cluster.
>> With an H323 gateway, anything can use it.
>>
>> ----- Original Message -----
>> From: "Manoj Kalpage" <manoj.kalpage at gmail.com>
>> To: "Lelio Fulgenzi" <lelio at uoguelph.ca>
>> Cc: <cisco-voip at puck.nether.net>
>> Sent: Saturday, July 21, 2007 9:42 PM
>> Subject: Re: [cisco-voip] Local call send out from SRST gatewayr when not
>> inSRST mode
>>
>>
>> > What would be the recommended MGCP or H323? In either way, I think I
>> > have to add gateway in to CCM under Device-> Gateway-> Add new
>> > Gateway. Isn't it?
>> >
>> > Regards,
>> > manoj
>> >
>> >
>> > On 7/22/07, Lelio Fulgenzi <lelio at uoguelph.ca> wrote:
>> >>
>> >>
>> >> When doing MGCP with config download, you will need to configure the 
>> >> MGCP
>> >> gateway on the router with the exact same name as the hostname on the
>> >> router. If you have a domain name configured, you must add this in the
>> >> MGCP
>> >> config.
>> >>
>> >> Here are the basic commands you need to download the MGCP config to 
>> >> the
>> >> router:
>> >>
>> >> ccm-manager fallback-mgcp (to make MGCP go to H323/SRST)
>> >> ccm-manager redundant-host <ipaddr of secondary callmanager>
>> >> ccm-manager mgcp
>> >> ccm-manager music-on-hold
>> >> ccm-manager config server <ipaddr of tftp server>
>> >> ccm-manager config            <-------- this is what initiates the
>> >> download
>> >> and the config statement others have removed once the download is
>> >> complete
>> >>
>> >> the config will then download a whole bunch of commands, including:
>> >>
>> >> mgcp
>> >> mgcp call-agent <ipaddr of primary callmanager> 2427 service-type mgcp
>> >> version 0.1
>> >> mgcp dtmf-relay voip codec all mode out-of-band
>> >> mgcp rtp unreachable timeout 1000 action notify
>> >> mgcp modem passthrough voip mode nse
>> >> mgcp package-capability rtp-package
>> >> no mgcp package-capability res-package
>> >> mgcp package-capability sst-package
>> >> no mgcp package-capability fxr-package
>> >> mgcp package-capability pre-package
>> >> no mgcp timer receive-rtcp
>> >> mgcp sdp simple
>> >> mgcp rtp payload-type g726r16 static
>> >> !
>> >> mgcp profile default
>> >> !
>> >>
>> >> It will also overwrite whatever you have configured in your T1/E1
>> >> controller
>> >> with something similar to:
>> >>
>> >> controller T1 0/0/0
>> >>  framing esf
>> >>  linecode b8zs
>> >>  pri-group timeslots 1-24 service mgcp
>> >> !
>> >> controller T1 0/1/0
>> >>  framing esf
>> >>  linecode b8zs
>> >>  pri-group timeslots 1-24 service mgcp
>> >>
>> >> It will use whatever settings you have on your config page here I
>> >> believe.
>> >>
>> >>
>> >>
>> >> ----- Original Message -----
>> >> From: "Manoj Kalpage" <manoj.kalpage at gmail.com>
>> >> To: "Lelio Fulgenzi" <lelio at uoguelph.ca>
>> >> Cc: <cisco-voip at puck.nether.net>
>> >>
>> >> Sent: Saturday, July 21, 2007 9:26 PM
>> >> Subject: Re: [cisco-voip] Local call send out from SRST gatewayr when 
>> >> not
>> >> inSRST mode
>> >>
>> >>
>> >> > Thanks Lelio, I will test this on my lab and let you know.
>> >> >
>> >> > Regards,
>> >> > Manoj
>> >> >
>> >> >
>> >> > On 7/21/07, Lelio Fulgenzi <lelio at uoguelph.ca> wrote:
>> >> >> Exactly. If you are configuring it as an H323 gateway I don't think
>> >> >> any
>> >> >> other extra configuration is required. Others on the list can 
>> >> >> comment
>> >> >> on
>> >> >> that.
>> >> >>
>> >> >> If you configure as an MGCP gateway, then you definately need some
>> >> >> additional config statements, in actuality, you might be losing 
>> >> >> some
>> >> >> of
>> >> your
>> >> >> H323 config statements if you go with autoloading your MGCP config
>> >> through
>> >> >> TFTP to CallManager.
>> >> >>
>> >> >> ----- Original Message -----
>> >> >> From: "Manoj Kalpage" <manoj.kalpage at gmail.com>
>> >> >> To: "Lelio Fulgenzi" <lelio at uoguelph.ca>
>> >> >> Cc: <cisco-voip at puck.nether.net>
>> >> >> Sent: Saturday, July 21, 2007 12:05 AM
>> >> >> Subject: Re: [cisco-voip] Local call send out from SRST gatewayr 
>> >> >> when
>> >> >> not
>> >> >> inSRST mode
>> >> >>
>> >> >>
>> >> >> > Lelio,
>> >> >> > Thank you very much for your reply, Do you mean register branch
>> >> >> > office
>> >> >> > SRST gateway on call manager as a second voice gateway? if so, do 
>> >> >> > I
>> >> >> > need any special settings on SRST ?
>> >> >> > Bellow is my current SRST configuration.
>> >> >> >
>> >> >> > Regards,
>> >> >> > Manoj
>> >> >> >
>> >> >> > !
>> >> >> > version 12.4
>> >> >> > service timestamps debug datetime msec
>> >> >> > service timestamps log datetime msec
>> >> >> > no service password-encryption
>> >> >> > !
>> >> >> > hostname TEST01
>> >> >> > !
>> >> >> > boot-start-marker
>> >> >> > boot-end-marker
>> >> >> > !
>> >> >> > enable password xxxxxxxxx
>> >> >> > !
>> >> >> > aaa new-model
>> >> >> > !
>> >> >> > !
>> >> >> > aaa authentication login userauth local
>> >> >> > !
>> >> >> > !
>> >> >> > aaa session-id common
>> >> >> > clock timezone jst 9
>> >> >> > network-clock-participate wic 0
>> >> >> > ip cef
>> >> >> > !
>> >> >> > !
>> >> >> > no ip dhcp use vrf connected
>> >> >> > ip dhcp excluded-address 192.168.9.200 192.168.9.254
>> >> >> > ip dhcp excluded-address 192.168.9.1 192.168.9.99
>> >> >> > ip dhcp excluded-address 192.168.7.151 192.168.7.254
>> >> >> > ip dhcp excluded-address 192.168.7.1 192.168.7.99
>> >> >> > !
>> >> >> > ip dhcp pool DATA
>> >> >> >   network 192.168.9.0 255.255.255.0
>> >> >> >   default-router 192.168.9.1
>> >> >> >   dns-server 61.122.112.97
>> >> >> >   lease 14
>> >> >> > !
>> >> >> > ip dhcp pool VOICE
>> >> >> >   network 192.168.7.0 255.255.255.0
>> >> >> >   domain-name write
>> >> >> >   dns-server 172.16.0.10
>> >> >> >   default-router 192.168.7.1
>> >> >> >   option 150 ip 172.16.0.10
>> >> >> >   lease 14
>> >> >> > !
>> >> >> > !
>> >> >> > ip domain name xxx.com
>> >> >> > !
>> >> >> > multilink bundle-name authenticated
>> >> >> > !
>> >> >> > isdn switch-type ntt
>> >> >> > !
>> >> >> > voice-card 0
>> >> >> > !
>> >> >> > !
>> >> >> > !
>> >> >> > voice translation-rule 1
>> >> >> > rule 1 /1602/ /0335119981/
>> >> >> > rule 2 /1607/ /0335119982/
>> >> >> > rule 3 /1609/ /0335119983/
>> >> >> > !
>> >> >> > voice translation-rule 2
>> >> >> > rule 1 /35119981/ /1602/
>> >> >> > rule 2 /35119982/ /1607/
>> >> >> > rule 3 /35119983/ /1609/
>> >> >> > !
>> >> >> > !
>> >> >> > voice translation-profile ANI
>> >> >> > translate calling 1
>> >> >> > !
>> >> >> > voice translation-profile DNIS
>> >> >> > translate called 2
>> >> >> > !
>> >> >> > !
>> >> >> > !
>> >> >> > policy-map AutoQoS-Policy-Trust
>> >> >> > class class-default
>> >> >> >  fair-queue
>> >> >> > policy-map Shape-20MB
>> >> >> > class class-default
>> >> >> >  shape average 20000000
>> >> >> >  service-policy AutoQoS-Policy-Trust
>> >> >> > !
>> >> >> > !
>> >> >> > crypto isakmp policy 10
>> >> >> > encr 3des
>> >> >> > hash md5
>> >> >> > authentication pre-share
>> >> >> > group 2
>> >> >> > crypto isakmp key 6 xxxxxx address 210.210.210.210 no-xauth
>> >> >> > !
>> >> >> > !
>> >> >> > crypto ipsec transform-set KAM esp-3des esp-md5-hmac
>> >> >> > !
>> >> >> > crypto ipsec profile GREPRO
>> >> >> > set transform-set KAM
>> >> >> > !
>> >> >> > !
>> >> >> > interface Tunnel0
>> >> >> > description ******* Tunnel to Main Office *********
>> >> >> > bandwidth 2000
>> >> >> > ip address 10.0.22.2 255.255.255.0
>> >> >> > ip nbar protocol-discovery
>> >> >> > tunnel source FastEthernet0/1
>> >> >> > tunnel destination 210.81.12.194
>> >> >> > tunnel mode ipsec ipv4
>> >> >> > tunnel protection ipsec profile GREPRO
>> >> >> > service-policy output Shape-20MB
>> >> >> > !
>> >> >> > interface FastEthernet0/0
>> >> >> > no ip address
>> >> >> > ip nat inside
>> >> >> > no ip virtual-reassembly
>> >> >> > duplex auto
>> >> >> > speed auto
>> >> >> > !
>> >> >> > interface FastEthernet0/0.10
>> >> >> > encapsulation dot1Q 10 native
>> >> >> > ip address 192.168.9.1 255.255.255.0
>> >> >> > ip nat inside
>> >> >> > ip virtual-reassembly
>> >> >> > ip tcp adjust-mss 1400
>> >> >> > !
>> >> >> > interface FastEthernet0/0.20
>> >> >> > encapsulation dot1Q 20
>> >> >> > ip address 192.168.7.1 255.255.255.0
>> >> >> > ip nat inside
>> >> >> > ip virtual-reassembly
>> >> >> > ip tcp adjust-mss 1400
>> >> >> > !
>> >> >> > interface FastEthernet0/1
>> >> >> > description ****** INTERNET **********
>> >> >> > bandwidth 2000
>> >> >> > ip address 124.124.124.124 255.255.255.248
>> >> >> > ip nat outside
>> >> >> > no ip virtual-reassembly
>> >> >> > ip route-cache flow
>> >> >> > ip tcp adjust-mss 1400
>> >> >> > speed 100
>> >> >> > full-duplex
>> >> >> > !
>> >> >> > interface BRI0/0/0
>> >> >> > no ip address
>> >> >> > isdn switch-type ntt
>> >> >> > isdn point-to-point-setup
>> >> >> > isdn incoming-voice voice
>> >> >> > isdn map address .* plan unknown type unknown
>> >> >> > !
>> >> >> > interface BRI0/0/1
>> >> >> > no ip address
>> >> >> > isdn switch-type ntt
>> >> >> > isdn point-to-point-setup
>> >> >> > isdn incoming-voice voice
>> >> >> > isdn map address .* plan unknown type unknown
>> >> >> > !
>> >> >> > interface Dialer0
>> >> >> > no ip address
>> >> >> > !
>> >> >> > ip route 0.0.0.0 0.0.0.0 124.39.174.233
>> >> >> > ip route 10.0.0.0 255.255.255.0 Tunnel0
>> >> >> > ip route 172.20.0.0 255.255.0.0 Tunnel0
>> >> >> > !
>> >> >> > !
>> >> >> > ip http server
>> >> >> > no ip http secure-server
>> >> >> > ip nat inside source list 102 interface FastEthernet0/1 overload
>> >> >> > !
>> >> >> > access-list 102 permit ip 192.168.7.0 0.0.0.255 any
>> >> >> > access-list 102 permit ip 192.168.9.0 0.0.0.255 any
>> >> >> > !
>> >> >> > !!
>> >> >> > control-plane
>> >> >> > !
>> >> >> > !
>> >> >> > !
>> >> >> > voice-port 0/0/0
>> >> >> > !
>> >> >> > voice-port 0/0/1
>> >> >> > !
>> >> >> > !
>> >> >> > !
>> >> >> > dial-peer voice 1 pots
>> >> >> > destination-pattern 0110
>> >> >> > port 0/0/0
>> >> >> > forward-digits 3
>> >> >> > !
>> >> >> > dial-peer voice 2 pots
>> >> >> > destination-pattern 0T
>> >> >> > port 0/0/0
>> >> >> > !
>> >> >> > dial-peer voice 3 pots
>> >> >> > incoming called-number .
>> >> >> > direct-inward-dial
>> >> >> > port 0/0/0
>> >> >> > !
>> >> >> > !
>> >> >> > !
>> >> >> > !
>> >> >> > call-manager-fallback
>> >> >> > secondary-dialtone 0
>> >> >> > max-conferences 8 gain -6
>> >> >> > transfer-system full-consult
>> >> >> > timeouts interdigit 3
>> >> >> > ip source-address 192.168.7.1 port 2000
>> >> >> > max-ephones 24
>> >> >> > max-dn 48
>> >> >> > voicemail 00345501603
>> >> >> > moh music-on-hold.au
>> >> >> > time-format 24
>> >> >> > !
>> >> >> > !
>> >> >> > line con 0
>> >> >> > line aux 0
>> >> >> > line vty 0 4
>> >> >> > transport input telnet ssh
>> >> >> > !
>> >> >> > scheduler allocate 20000 1000
>> >> >> > ntp clock-period 17178208
>> >> >> > ntp update-calendar
>> >> >> > ntp server 202.202.202.222 prefer
>> >> >> > end
>> >> >> >
>> >> >> >
>> >> >> > On 7/21/07, Lelio Fulgenzi <lelio at uoguelph.ca> wrote:
>> >> >> >> Simply register the local ISDN BRI as a gateway (h323, mgcp,
>> >> >> >> whatever)
>> >> >> >> and
>> >> >> >> create route patterns accordingly to send calls out that 
>> >> >> >> gateway.
>> >> >> >>
>> >> >> >> Basically do the same thing you did for your main office route
>> >> >> >> patterns/gateways - just copy it for the branch office gateways.
>> >> >> >>
>> >> >> >>
>> >> >> >> ----- Original Message -----
>> >> >> >> From: "Manoj Kalpage" <manoj.kalpage at gmail.com>
>> >> >> >> To: <cisco-voip at puck.nether.net>
>> >> >> >> Sent: Friday, July 20, 2007 10:52 PM
>> >> >> >> Subject: [cisco-voip] Local call send out from SRST gatewayr 
>> >> >> >> when
>> >> >> >> not
>> >> >> >> inSRST
>> >> >> >> mode
>> >> >> >>
>> >> >> >>
>> >> >> >> > HI all,
>> >> >> >> > We have CM hosted in main office and branch office use SRST
>> >> >> >> > gateway
>> >> >> >> > with local ISDN BRI voice lines (Currently ISDN BRI only use 
>> >> >> >> > when
>> >> WAN
>> >> >> >> > fails) . Branch office located far away from main office. When
>> >> branch
>> >> >> >> > office make call to their local area numbers, it still go out 
>> >> >> >> > to
>> >> PSTN
>> >> >> >> > from main office voice gateway so, local call for branch 
>> >> >> >> > office
>> >> >> >> > becomes long distance call. I am looking for solution which I 
>> >> >> >> > can
>> >> send
>> >> >> >> > branch office local call out from SRST router using it's own 
>> >> >> >> > ISDN
>> >> BRI
>> >> >> >> > without send them to main office voice gateway. Is this 
>> >> >> >> > possible
>> >> >> >> > to
>> >> do
>> >> >> >> > with SRST or CME? any comments would be greatly appreciated.
>> >> >> >> >
>> >> >> >> > Best regards,
>> >> >> >> > PERE
>> >> >> >> > _______________________________________________
>> >> >> >> > cisco-voip mailing list
>> >> >> >> > cisco-voip at puck.nether.net
>> >> >> >> > https://puck.nether.net/mailman/listinfo/cisco-voip
>> >> >> >> >
>> >> >> >>
>> >> >> >>
>> >> >> >
>> >> >>
>> >> >>
>> >> >
>> >
>>
>>
> 