Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Wanet Telecoms Ltd on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Comcast PRI Port Not Going - Unassigned Number Error?

Status
Not open for further replies.

mikedphones

Vendor
Oct 11, 2005
467
US
I am on a site with a 4.2 going from a legacy T1 to a Comcast PRI.

I changed the PRI tab to PRI, put in service, etc.

I cannot place an outbound call. Inbound is not an issue during initial testing.

I have:

modified ARS with a 1NSI entry to send a valid caller ID. - NO LUCK

built an incoming DID and pointed it to the test phone - In fine, out no.

asked them to do BTN override - NO Luck.

I am thinking there needs to be a relationship between a valid DID and the extensions incoming call route even for outbound to work. However, I have done that.

ARS entries are pretty standard:

1N; N 3K1 0
N; N 3K1 0

Is this me or Comcast?

They say they are seeing "unassigned number"
Our Monitor shows: "unallocated number".

They say they are fine on their side.

Thanks
 
Did you try without the I on the 1N. you can try 1Nsxxxxxxxxxx with the X being the btn.

Kevin Wing
ACSS Small and Medium Enterprise (SME) Communications
ACS- Implement IP Office
ACA- Implement IP Office
Vive Communications
 
Make sure your pri is set to NI2 for national and use 1Nsi5555555555 to send out a valid 10 digit number that is ported on the pri. Use system monitor with isdn traces to verify you are sending out a valid 10 digit number.
 
Hi All,
We went back and forth on this, but it ended up being something in the way they had the digits set. I built the Incoming call route with the full 10 digit number instead of how the previous tech had done it years ago. The incoming number was "-xxx". Not sure what the "-" was.

Anyhow, the change to 10 digit, even though they were only sending 3 digits seems to have fixed it.

They are doing BTN override at the moment, so when I get to the point where we control the outbound caller ID, the issue may resurface.
It's two companies sharing a circuit so I need to create two ARS names each with it's own Nsi entry for their main numbers (they don't want to send their own DID). It will be interesting to see if once they give me back control of the caller ID, if it still works!

Thanks again.
 
Manager Help is helpful

– = Left-to-Right Exact Length Matching Using a - in front of the number causes a left-to-right match. When left-to-right matching is used, the number match must be the same length. For example -96XXX will match a DID of 96000 but not 9600 or 960000.



"Trying is the first step to failure..." - Homer
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top