From: Tony Edwards (tonyedwards.rs@gmail.com)
Date: Sat Oct 06 2007 - 09:52:44 ART
Hi GS,
A query on hunt group & Parallel ringing on analog trunk/FXO.
Recently one of my customers legacy key system has failed and a band aid
solution to get their business operations up & running quickly, I have
installed a 4 x port FXO analog trunk card on their 2801 ISR IOS gateway &
configured those 4 x ports as MGCP gateways on back end CCM 4.0.x . And then
we have rejumpered 4 x analog phones customer has directly on to FXO card ,
i.e bypassing the failed key system. Even though my customer has 4 x
independent DID ranges #s for each of these 4 x PSTN phones , they are
advertising ONE primary # to the external PSTN world. So entire world will
be calling that customer on primary # and then hunting was happening on a
busy & no answer situation on the primary #.
And when we successfully migrated all 4 x PSTN DID #ed lines on to
respective FXO interfaces , all required telephony functionality was
restored where all Inbound calls will be hitting FXO trunks in a Hunting
fashion and all out bound calls were egressing via Qos enaled IP WAN trunk.
Customer was happy and I went home and sat with few beers thinking that we
have successfully looked after our customer :-)
But next day morning he rang us up and said , he other business critical
feature of "Parallel ringing" is not working.
I knew straight away that , we got an issue at hand because all these 4 x
FXO trunks are configured as 4 x separate MGCP gateways & each line was
configured with a **different** extention # .
And for Parallel ringing to work with in IP Tel/CCM world , we got to
configure all 4 x PSTN lines with the **same** extention # , which
unfortunately I can not do in this case.
Second way , I tried to make it happen is , by deploying a hardware based
solution such as deploying 4 x external line Button capable IP Phones so
that we can create all 4 x separate extentions against each line button , so
that each of customers staff member can see incoming call on any of their 4
x DIDs and then can pick up the calls with out fail. In this HW based
solution , even though it does not parallel ring on all 4 x phones
simultaneously , at least since each phone can see every single incoming
call on their display screen , I can keep them happy.
Unfortunately , I could not manage require IP phone hand sets at that point
in time.
As a 3rd option , I am thinking to manipulate IOS gateway functionality with
some *numexp* rule base where I can "replace"
the whole incoming Fully qualified DID range in to ONE common internal
external #. So even though each of my Voice ports will be statically mapped
to 1 x Destination pattern of DID # , once the call hits the Ingress voice
port , the NUMEXP will kick in and then translate the number to a common
extn # before the call is delivered to end station.
In that situation , logically the Parallel ringing should work on all 4 x
phones whenever any one calls this HUNT group's Primary #.
But I am not sure whether CCM (version 4.0.x) will come to the party or not.
Or else , can any one suggest 4 x option which is easily deployable for my
customer's Parallel ringing(simultaneous ringing on all phones for every
incoming call) issue on 4 x port FXO trunk??
thanks
tony
This archive was generated by hypermail 2.1.4 : Fri Nov 16 2007 - 13:11:12 ART