[cisco-voip] cme/PRI newbie question

[Leslie Meade]

I might of explained it wrong. I have a 4 port FSO with 4 inbound lines
that are all 1700.
I have a fractional PRI that has a pilot number of 1700 that is not
live, however the DiD's (that no one will use) are live.

Once the go ahead is given the Telco will move the 1700 from the FXO to
the PRI as its pilot number. At this time I get fast busy on the PRI
DID's. Is this normal or is my config incorrect?



-----Original Message-----
From: Jonathan Charles [mailto:jonvoip at gmail.com] 
Sent: Monday, July 07, 2008 9:33 PM
To: Leslie Meade
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] cme/PRI newbie question

Well, they have made the pilot live, but it isn't hunting to the other
FXO ports... so, once it is busy, the other calls fail. Open a ticket
with telco and tell them they are broken.


Jonathan

On Mon, Jul 7, 2008 at 11:23 PM, Leslie Meade <lmeade at signal.ca> wrote:
> I have a four port FXO card and a new fractional pri. The FXO has a
four
> line over lay of XXX XXXX 1700 that is being ported to my pri as the
pilot
> number.
>
>
>
> My question, when I make an inbound call with one of the new DID's.
The
> phone rings and I get through. But if I try it again with another
phone to
> the same number, while till on the first call I get busy signals. I
have 15
> phones all with have the same config as the one below. I have been
told that
> when the pilot number has been made live I will not have this issue. I
this
> true or am I missing something in my config to allow multiple calls to
the
> same number?
>
> None of the DID's in the PRI will be used only the 1700 (pilot number)
is
> being used for incoming calls.
>
>
>
> Leslie
>
>
>
>
>
>
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: 2811.txt
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20080707/eaf394ee/attachment-0001.txt>