Help With E1/PRI Configurations

[MineAlone]

Hello team

I am fairly to this platform and I need your help.

I have a customer with Avaya IP Office 500v2 R11. They have E1/PRI trunks connected like this: 1) PRI/E1 QSIGB for PSTN 2. PRI/E1 QSIGA for Matrix and Avaya Integration. The Avaya and Matrix integration are working fine, we even took the same cable from PSTN and put it onto Matrix E1/PRI port everthing works just fine outgoing and Inbound. However if we are to use it on Avaya only incoming is working however with no ringback tone you only hear the other person answering without being notified of the call being successful. Also if I dial the E1 number from PSTN the call continues to say sorry the called number is busy now please call again later, but if you check in System status there will be two calls incoming and outgoing where the same called number is trying to call it sell it actually picks a short code for dialing. What could be the challenge? I have additional Universal PRI licenses and it is a server edition setup with one Primary server and one control unit where the E1/PRI is terminating.

 

[IamaSherpa]

The PRI E1 connected to the PSTN has to be set as ETSI, not QSig that is a protocol used for internetworking multivendor trunks.

 

[MineAlone]

Thank you IamaSherpa for replying

However my main worry is I am able to make outgoing calls using the same E1 trunk. But incoming calls are giving a number busy error. We took the same cable from Service provider and connect it on a Matrix IPBX E1 port and everything worked with no issues both outgoing and incoming. We further engaged the service provider to check which errors are they getting from their end they said our Avaya IPBX is rejecting the incoming calls.

 

[IamaSherpa]

If outgoing calls from E1 are ok it means is not a problem of the wiring cable. Set a generic incoming call route to a single existing extension, no number mapping, just the E1 line id addressing and start monitoring, if the telco is correct you'll see arrive something, if not is a provider problem.

 

[MineAlone]

I have tried all combination of generic incoming call route, at times the call can actually be showing as incoming call on channel 1 and again showing as outgoing call on channel 30 thereby causing the number to be busy( Like it is calling itself). I read this article:

The line Short Code tab is shown for the following trunk types which are treated as internal or private trunks: QSIG (T1, E1, H.323), BRI S0, H.323, SCN, IP Office. Incoming calls on those types of trunk are not routed using Incoming Call Route settings. Instead the digits received with incoming calls are checked for a match as follows:

Extension number (including remote numbers in a multi-site network).

Line short codes (excluding ? short code).

System short codes (excluding ? short code).

Line ? short code.

System ? short code.

Short codes can be added and edited using the Add, Remove and Edit buttons. Alternatively you can right-click on the list of existing short code to add and edit short codes.

This confused me more as to how do I set the incoming using a short code setting on the E1 line.

 

[MineAlone]

Please see the attached image

 

[MineAlone]

These are my PRI settings

 

[IamaSherpa]

You don't have to use short codes on trunk but just set the incoming call route, is much more easy. Additionally ETSI E1 could be set as "ETSI" or "ETSI CHI" (channel handling indicator). Normally it doesn't matter which channel you use so just ETSI is the best setting, viceversa the ETSI CHI could be "dangerous" because you have to map exactly the channel will be used by the telco for incoming calls.
Have a look at the config, it works as it is

 

[MineAlone]

Only QsigB was able to sync all the other options were giving me out of service. I did not configure any short code on the trunk. I tried configuring just the Incoming call route with an existing extension but still with no joy. If I am to configure a short code like Short Code N Feature Dial Phone number N line group I put the E1 line group on the trunk that is when if I make an incoming it will show as incoming and outgoing at the same time. The service provider is saying everything is okay from their end also we tested using Matrix IPBX and indeed the line worked fine both incoming and outgoing.