IP TRUNKING ISSUE

[mrdelite29]

I've taken over all the mitel clients at my job recently. So I am playing catch up on a lot of systems. 1 client in particular have two 3300 (one in Carolina ver 8.0.5.12 and one in NYC ver 8.0.9.20)

In NYC the 3300 is used as a gateway to another pbx that they use there. If the ny employees extension is 321 the caller in sc dials 1321. But when he does it says "invalid extension".

I did a STATE XNET ALL in nyc and got this result. see attatched.

I need some guidance from this point. I just want to get a head start on resolving some issues.

 

[kwbMitel]

Try the maintenance command:

Rmess verify pbx x LAN (X = PBX Number)

Are All calls failing or just some? The fact that you dial a 1 then ext suggests that ARS is used and may not be fully configured.

Another thing to try is to turn on CCS trace on the destination system (command "CCS Trace Enable Cont")

Make the call and see if the call appears on the remote system. you need to determine which system is generating the error. The IP trunks could be OK but the remote system doesn't like the digits for example.



*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.

 

[IrwinMFletcher]

One quick confirmation is to ask if the Invalid Extension comes up after the '1' is dialed, or after all the digits. If it comes up right away after dialing the '1', then look at the SC system. Or '13' probably now that I think about it...the point is to see if the local system recognizes that it's invalid before the entire digit string has been entered.

 

[mrdelite29]

Try the maintenance command:

Rmess verify pbx x LAN (X = PBX Number)"

ON SC 3300 ICP
RMESSAGE: Connected to PBX 1
RMESSAGE: Verification successful to PBX 1
RMESSAGE: Disconnected to PBX 1
RMESSAGE: Connected to PBX 2
RMESSAGE: Verification successful to PBX 2
RMESSAGE: Disconnected to PBX 2

ON NYC 3300 ICP

RMESSAGE: Connected to PBX 1
RMESSAGE: Verification successful to PBX 1
RMESSAGE: Disconnected to PBX 1
RMESSAGE: Connected to PBX 2
RMESSAGE: Verification successful to PBX 2
RMESSAGE: Disconnected to PBX 2

 

[kwbMitel]

Rmess test indicates that all the IP parameters are set and working as required.

It is the digits being sent that are causing the call to fail.

CCS trace will help determine if the digits are being sent and/or received.

IrwinFletchers suggestion is valid. At what point in the sequence does the call fail?

Is the problem only with one user or all?

Is the problem one direction or both?

I have asked most of these questions before.



*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.

 

[Mitelmatt]

Sounds like a Digit Mod issue in the ARS Route to the remote site.

You either need to absorb the "1" in the originating PBX through the Digit Mod in the Route or Abosob the 1 in the Trunk Service assignment in the recieving PBX

Keeps getting me caught out all the time!

 

[mrdelite29]

Update from system log.


Log Type: Software
Log Number: 2480
Severity: Warning
Date: 2009/Jan/23
Time: 11:53:44
Source: Call Control - Software
Description: HANDLER_ERR, OFFSET 2:$DBE, PC: $520584 LOG_ID: xnetdh_#100, PROCEDURE: virtual_call_term_pbx_handling, SEVERITY: cp_inform PID: ($7, $606) SWID: xnet_trunk 8, DAM: idle_device XNETDH_: Call in on outgoing only trk. Xnet Sync State: unknown.
Module: Main
File Name and Line Number:

 

[mrdelite29]

The above error was from the NYC 3300

 

[mrdelite29]

A bit of history, the NYC3300 has a NSU that connects a T-1 to an Avaya PBX somewhere else in the building. I asked an IT guy up in NYC to see where the NSU is plugged into and he said a Dell Switch. We are getting in contact with the owners on the building running the phone system up there to verify the wiring for this setup. A damn shame we deal in communications and nobody talks to one another.

But I ran a STATE 4 1 1 1 1 on that T-1 and it does say IDLE

 

[LoopyLou]

What kind of 3300. If it had imbedded analog I would program up a single line port on the gateway in NY. If SC can call it then IP trunks are not the problem. As someone else suggested it is most likely an ARS issue and this is one way to prove it.

In SC you dial 1321 but what is sent to NY? As suggested you should absorg the 1 in SC via the Digit Mod programming and only send 321 to NY.

At some point you need to strip that one off the extension number and only send 321 to the Avaya. Everthing else appears good from all your testing.

 

[mrdelite29]

They 1 is absorbed in SC and 321 would only be sent to nyc switch(mx) which has a NSU with a t1 that is supposed to connect to the Avaya. There are no devices programmed on the NYC because it's only acting as a gateway. Like I said the IT guy up there says the NSU T-1 is connected to a network switch.

 

[mrdelite29]

*Update from Client*

Rings busy and says Out of Service. Happens after the last digit (x1377).

 

[Mitelmatt]

Sounds like the IP Trunking isn't configured correcly.

Make sure you have Local profile and remote profile set correctly to corraspond with each other. This is normally what gives Out of Service

Ip/Xnet Trunk Profile Assignment. Use the Help if necessary

Has it ever been working?

 

[mrdelite29]

Yes, they have comfirmed that it has been working at one time.

 

[mrdelite29]

SC 3300

this is the order for each profile:
Local Profile Number>Trunk Service Number>Interconnect Number>Remote Profile Number>

1>7>1>1
2>7>1>1


NYC 3300

1>5>1>1

 

[Mitelmatt]

and in Trunk Service Assignment 7, have you got Digits to absorb "0"?

 

[mrdelite29]

Okay guys, after all the OTHER troubleshooting I was doing it finally did boil down to the ASR Digits Modification Table.

The person who worked on this earlier did not program them correctly. When someone in sc dials 1 it is absorbed at the sc switch, at the nyc switch an 0 is inserted because at the new york avaya switch they dial 0364 for example for an extension. So thanks to all who spotted that way in the beginning. It was a great learning experience working with you guys.

 

[mrdelite29]

New Update, almost done.

I just now got the info I needed from the client in regards to what the Avaya users dial to reach south carolina.

Quote from client

"I think we have them dialing the 411 area code then our number. So, 1-411-573-2555. Then that routes out through that T1 connection."

Now I have to find out what is exactly sent to the NYC3300 and pass it towards SC.