[cisco-voip] cme/PRI newbie question

[Leslie Meade]

Yes that is correct
The dids are not being used. And the only number I am interested in is 1700 the pilot number that is not live. This issue is only happening on dids that are in the pri list that the client will not be using

Yes I have checked that multiframe established is there and I have seen the 2nd call hit the router for the debug q931 
Cheers 

Leslie Meade 
------------------------ 
Sent using a SIGNAL powered BlackBerry 


________________________________

From: Moataz Mamdouh 
To: Leslie Meade; Kelemen Zoltan 
Cc: cisco-voip at puck.nether.net 
Sent: Tue Jul 08 01:50:12 2008
Subject: Re: [cisco-voip] cme/PRI newbie question 


as he mentioned are they assigned to phones directly , i saw in the conf that u have assigned 1700 on line 2 , right ?

--- On Tue, 7/8/08, Kelemen Zoltan <keli at carocomp.ro> wrote:


	From: Kelemen Zoltan <keli at carocomp.ro>
	Subject: Re: [cisco-voip] cme/PRI newbie question
	To: "Leslie Meade" <lmeade at signal.ca>
	Cc: cisco-voip at puck.nether.net
	Date: Tuesday, July 8, 2008, 2:23 AM
	
	
	Are the incoming DiD numbers assigned to phones? Or transformed/routed 
	to them? Depending on how many digits you receive from the provider as 
	called number, you might need to do some number translations on the 
	called number to make sure the calls reach your phones.
	
	As Erick noted, once you know your ISDN line is
	 up (Layer 2 Status 
	should include: State = MULTIPLE_FRAME_ESTABLISHED )
	"debug isdn q931" is your friend ;-)  As far as I'm concerned,
	this 
	debug command has by far the most readable output of all Cisco IOS 
	debugs :-)
	
	regards,
	  Zoltan
	
	Erick Bergquist wrote:
	> If you do a 'show isdn stat' on the router with PRI, does it say
	MULTI
	> FRAME ESTABLISHED?
	>
	> If so, when you call the DIDs coming in on the new PRI, does 'debug
	> isdn q931' show the call coming in?
	>
	>
	> On Mon, Jul 7, 2008 at 11:44 PM, Leslie Meade <lmeade at signal.ca>
	wrote:
	>   
	>> 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
	>>>
	>>>
	>>>       
	>>
	 _______________________________________________
	>> cisco-voip mailing list
	>> cisco-voip at puck.nether.net
	>> https://puck.nether.net/mailman/listinfo/cisco-voip
	>>
	>>
	>>     
	> _______________________________________________
	> cisco-voip mailing list
	> cisco-voip at puck.nether.net
	> https://puck.nether.net/mailman/listinfo/cisco-voip
	>   
	
	_______________________________________________
	cisco-voip mailing list
	cisco-voip at puck.nether.net
	https://puck.nether.net/mailman/listinfo/cisco-voip


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20080708/685d5f9d/attachment.html>