Some telco's do, some telco's don't. The text Rarely used for PRI is
IMO a
location-centric and carrier-centric statement. As another poster
suggested,
PRI's are picky, and some carriers are super-picky so it's always best
to
dot your i's and cross your t's when
In the process of turning up a new pri. Zttool indicates the T1 is
ready with no alarms.
asterisk*CLI pri show span 1
Primary D-channel: 24
Status: Provisioned, Down, Active
Switchtype: National ISDN
Type: CPE
Window Length: 0/7
Sentrej: 0
SolicitFbit: 0
Retrans: 0
Busy: 0
Overlap Dial: 0
T200
On December 8, 2004 10:56 am, Rich Adamson wrote:
Status: Provisioned, Down, Active
What does the Down mean in the above status line?
It means that your D channel isn't up, this is normal if * isn't running (or
the telco hasn't turned up the D channel yet)
-A.
On December 8, 2004 10:56 am, Rich Adamson wrote:
Status: Provisioned, Down, Active
What does the Down mean in the above status line?
It means that your D channel isn't up, this is normal if * isn't running (or
the telco hasn't turned up the D channel yet)
Okay, the d-chan is now up.
On December 8, 2004 12:45 pm, Rich Adamson wrote:
It would appear the call failed due to Info. element nonexist or
Invalid number format.
is your pridialplan=unknown and do you know how your telco is expecting calls
from you? I've seen some telcos refuse calls if Caller ID Name was set too
Rich Adamson wrote:
On December 8, 2004 10:56 am, Rich Adamson wrote:
Status: Provisioned, Down, Active
What does the Down mean in the above status line?
It means that your D channel isn't up, this is normal if * isn't running (or
the telco hasn't turned up the D channel yet)
Okay, the d-chan
Cause (len= 5) [ Ext: 1 Coding: CCITT (ITU) standard (0) 0: 0 Location:
User (0)
Ext: 1 Cause: Info. element nonexist or not implemented
(99), class =
Looks like the switch on the telco end might be confused about the number
pattern; try adding:
pridialplan=unknown
to
Colin Anderson wrote:
Cause (len= 5) [ Ext: 1 Coding: CCITT (ITU) standard (0) 0: 0 Location:
User (0)
Ext: 1 Cause: Info. element nonexist or not implemented
(99), class =
Looks like the switch on the telco end might be confused about the number
pattern; try adding:
I don't really understand why do many people set their pridialplan. The
text PRI Dialplan: Only RARELY used for PRI. in zapata.conf.sample is
not there to just take up space in the file.
Some telco's do, some telco's don't. The text Rarely used for PRI is IMO a
location-centric and
Colin Anderson wrote:
Some telco's do, some telco's don't. The text Rarely used for PRI is IMO a
location-centric and carrier-centric statement. As another poster suggested,
PRI's are picky, and some carriers are super-picky so it's always best to
dot your i's and cross your t's when dealing with
Colin Anderson wrote:
Cause (len= 5) [ Ext: 1 Coding: CCITT (ITU) standard (0) 0: 0 Location:
User (0)
Ext: 1 Cause: Info. element nonexist or not implemented
(99), class =
Looks like the switch on the telco end might be confused about the number
pattern;
Colin Anderson wrote:
Some telco's do, some telco's don't. The text Rarely used for PRI is IMO a
location-centric and carrier-centric statement. As another poster suggested,
PRI's are picky, and some carriers are super-picky so it's always best to
dot your i's and cross your t's when
On Wed, 8 Dec 2004, Eric Wieling aka ManxPower wrote:
Colin Anderson wrote:
Some telco's do, some telco's don't. The text Rarely used for PRI is IMO a
location-centric and carrier-centric statement. As another poster suggested,
PRI's are picky, and some carriers are super-picky so it's
On Wed, 8 Dec 2004, Eric Wieling aka ManxPower wrote:
I don't really understand why do many people set their pridialplan. The
text PRI Dialplan: Only RARELY used for PRI. in zapata.conf.sample is
not there to just take up space in the file.
I'd change that comment to almost ALWAYS needed.
Some telco's do, some telco's don't. The text Rarely used for PRI is
IMO a
location-centric and carrier-centric statement. As another poster
suggested,
PRI's are picky, and some carriers are super-picky so it's always best to
dot your i's and cross your t's when dealing with
Is there something different that I should be dialing?
On my pri, I have dialplan=national. It is from Allstream/ATT co-lo with
Telus which pretty much behaves the same as most US carriers. We don't dial
international, so it's not an issue for us.
If I dial XXX-XXX- with local area code,
On Wed, 8 Dec 2004, Rich Adamson wrote:
Since this is my first * pri turnup, what should the dialing string look
like in the US? (All outgoing calls will either be local or national (US);
no need for international at this time).
Been using the following two numbers as examples:
449-1234 =
17 matches
Mail list logo
