German or Italian Colleagues Please - National PSTN issue 1

[Nick44]

Hi,
if I have German or Italian colleagues out there, please can you assist me with signalling protocols on BRI trunks?

I seem to have a problem where some inbound calls are signalling overlap, while most are enbloc.
My trunks are set to be enbloc/enbloc and 90% of inbound calls ore OK. Some calls from some parts of the German network appear to be arriving as overlap signalling with only partial, or single, digits recieved from the PSTN.
Has anyone had this before, and do you have a model setup for German BRI trunks?
My system is located in southern Germany, near Stuttgart, and is on T-Systems trunks.


Speak softly and carry a big switch

 

[CHEEZUSCRAIZT]

Hello Nick,

we are located in Germany (northern part of Rhineland-Palatinate) and have also Telekom trunks.

We use overlap/enbloc for our trunk groups and have no problems.

Main Outgoing Trunk:

[b]Page Two[/b]  
Group Type: isdn

TRUNK PARAMETERS
         Codeset to Send Display: 0     Codeset to Send National IEs: 6
        Max Message Size to Send: 260   Charge Advice: automatic
  Supplementary Service Protocol: c     Digit Handling (in/out): overlap/enbloc
       Digit Treatment: insertion                              Digits: 00
            Trunk Hunt: cyclical
                                                   Digital Loss Group: 13
Incoming Calling Number - Delete:     Insert:                 Format:
              Bit Rate: 1200         Synchronization: async    Duplex: full
 Disconnect Supervision - In? y  Out? y
 Answer Supervision Timeout: 0
          Administer Timers? n        CONNECT Reliable When Call Leaves ISDN? n

[b]Page Three[/b]

TRUNK FEATURES
          ACA Assignment? n            Measured: both      Wideband Support? n
                                                          Maintenance Tests? y
                               Data Restriction? n     NCA-TSC Trunk Member:
                                      Send Name: n      Send Calling Number: y
            Used for DCS? n                            Send EMU Visitor CPN? n
   Suppress # Outpulsing? y    Format: public
 Outgoing Channel ID Encoding: preferred     UUI IE Treatment: service-provider
       Charge Conversion: 6
           Decimal Point: comma                  Replace Restricted Numbers? y
         Currency Symbol:                       Replace Unavailable Numbers? n
             Charge Type: EURO                        Send Connected Number: n
Network Call Redirection: none                    Hold/Unhold Notifications? n
             Send UUI IE? y                    Modify Tandem Calling Number? n
               Send UCID? n
 Send Codeset 6/7 LAI IE? y                         Ds1 Echo Cancellation? y

    Apply Local Ringback? n
 Show ANSWERED BY on Display? y
                             Network (Japan) Needs Connect Before Disconnect? n

Main Incoming Trunk:

[b]Page Two[/b]
      Group Type: isdn

TRUNK PARAMETERS
         Codeset to Send Display: 0     Codeset to Send National IEs: 6
        Max Message Size to Send: 260   Charge Advice: automatic
  Supplementary Service Protocol: c     Digit Handling (in/out): overlap/enbloc
       Digit Treatment: insertion                              Digits: 00
            Trunk Hunt: cyclical
                                                   Digital Loss Group: 13
Incoming Calling Number - Delete:     Insert:                 Format:
              Bit Rate: 1200         Synchronization: async    Duplex: full
 Disconnect Supervision - In? y
 Answer Supervision Timeout: 0
          Administer Timers? n        CONNECT Reliable When Call Leaves ISDN? n

[b]Page Three[/b]

TRUNK FEATURES
          ACA Assignment? n            Measured: both      Wideband Support? n
                                                          Maintenance Tests? y
                               Data Restriction? n     NCA-TSC Trunk Member:
                                      Send Name: n      Send Calling Number: y
            Used for DCS? n                            Send EMU Visitor CPN? n
   Suppress # Outpulsing? y    Format: public
 Outgoing Channel ID Encoding: preferred     UUI IE Treatment: service-provider
       Charge Conversion: 6
           Decimal Point: comma                  Replace Restricted Numbers? y
         Currency Symbol:                       Replace Unavailable Numbers? n
             Charge Type: EURO                        Send Connected Number: n
Network Call Redirection: none                    Hold/Unhold Notifications? n
             Send UUI IE? y
               Send UCID? n
 Send Codeset 6/7 LAI IE? y                         Ds1 Echo Cancellation? y

    Apply Local Ringback? n
 Show ANSWERED BY on Display? y
                             Network (Japan) Needs Connect Before Disconnect? n

Maybe this helps you.

Greetings
Jens

 

[Nick44]

Thanks Jens,
How are you steering inboud DDI calls? There are no permitted entries in the "ch inc-treat tru X" table for overlap.


Speak softly and carry a big switch

 

[CHEEZUSCRAIZT]

The logic for incoming calls to internal extensions is done with ars digit conversion.
For example is one of our Numbers 960. So the corresponding ARS digit conversion looks like this:

Matching Pattern     Min   Max   Del   Replacement String   Net  Conv ANI Req

960                  3     7     3                          ext   n       n

So all internal extensions can be called from outside.

Greets
Jens

 

[Nick44]

Brilliant!
Thank you.

Speak softly and carry a big switch

 

[CHEEZUSCRAIZT]

No Problem, I'm glad I could help

 

[ayavauser]

first off my apologies for jumping onto this post and the long winded post .......but CHEEZUSCRAIZT I seem to have the same issue in that most of my inbound calls are completing as well but depending upon where they are called from I get a different amount of total digits sent if that makes sense ?

I have a S8300 / BRI in Germany provided by Telekom as well.

just trying to wrap myself around this and understand your example you posted -

Matching Pattern Min Max Del Replacement-String Net Conv
ANI Req

960 3 7 3 ext n n


would this apply to digits 960 thru 960xxxx as defined in min / max entry ?

the delete 3 is for any number coming down the BRI ?

so if you see:

960 you strip 960 and nothing
960x you strip 960 and send x
960xx you strip 960 and send xx
960xxx you strip 960 and send xxx
960xxxx you strip 960 and send xxxx


in my case I tried using inc treatment method as well with enbloc / enbloc .....

the odd thing is the main number is 6 digits and all other numbers on the BRI are 8 digits.

when called from Mobile and outside of Germany it works fine if using inc call treatment except the lead number as we have to do a insert treatment to send to a 4 digit extension.

yet national calls are sent 6 digits for all calls including the main number.

noticed in the post that you are doing an insertion of digits 00 ( is this for AAR routing ? )

Digit Handling (in/out): overlap/enbloc
Digit Treatment: insertion Digits: 00



cheers

ayavauser

 

[CHEEZUSCRAIZT]

Hello avayauser,

first I would like to say, no problem for hijacking this thread ;-)

Then I would like to part your post for structurizing it.

So first part for me is the question regarding ars digit conversion.

You wrote:

would this apply to digits 960 thru 960xxxx as defined in min / max entry ?

the delete 3 is for any number coming down the BRI ?

so if you see:

960 you strip 960 and nothing
960x you strip 960 and send x
960xx you strip 960 and send xx
960xxx you strip 960 and send xxx
960xxxx you strip 960 and send xxxx

Think of the parts of the numbering format in Germany.
As Example:

[tt]
02634 = Area Code
960 = Main Telephone Number ( In german it is termed
"Kopfnummer"
1234 = 4-digit Extension
[/tt]

With the ARS Digit Conversion Rule following will happen:
[tt]
Someone will call 02634 960 1234.
From our Provider (Telekom) we get 960 1234.
The ARS Digit Conversion will now delete 960.
The Avaya will route the call to extension 1234.
[/tt]

We made this construct because of 3 main numbers (Kopfnummern). So we could get with 3 ARS-Rules all extension called. regardless of the called main number.

Your example is fully correct, if a customer would call 02634 960 123 the ARS will strip to 123.

Second part is your problem.
Have you tried to trace your incoming trunk?

list trace tac <number>

Your sentence:

the odd thing is the main number is 6 digits and all other numbers on the BRI are 8 digits.

Do you mean you got a 6-digit main-number (Kopfnummer) from your Provider?
All other numbers are your extensions? And they are 8-Digits long?
How long is your Area Code?

Sorry for quoting in german, but I think avayauser will understand it ;-)

Die Spezifikation E.164 begrenzt die Länge von Rufnummern im internationalen Verkehr auf höchstens 15 Ziffern, einschließlich Ländercode, ausschließlich Verkehrsausscheidungsziffern. Die Berliner Nummer +49 30 1234567 hat demnach 11 Ziffern.

http://de.wikipedia.org/wiki/Rufnummer#L.C3.A4nge_von_Rufnummern

I think you should first do a trace and post it here...
Maybe I'm overseeing something in your post, what will do the trick.

Greets
Jens

P.S. Digit insertion is done for AAR Routing!

 

[Nick44]

Hi Guys,
I was surprised when this thread re-surfaced!
Avayauser, the fix Cheezuscraitz gave me worked perfectly.
Just as he described it using the FAC for aar in the trunk plan.
Happy to post my aar table for you if you need it. This was applied in Germany and Italy and fixed all my inbound call problems.
I'm sure Cheezu won't mind me saying that the German PSTN numbering is a complete mess.


Speak softly and carry a big switch

 

[CHEEZUSCRAIZT]

Nick you say a true word.

Although the NANP is not that brilliant.

I'm really happy that the provided solution is working for you.
It's good to hear that it helped.

Greets
Jens

 

[ayavauser]

first off thank you gentleman for the replies -

extensions are 4 digits and they match up 1 for 1 except for the Main Number>

main number :

country code 49

221 + 95270 x

all others

country code 49

221 + 95270 xxx



dialed as local :

main number :

95270 x

all others

95270 xxx


in my traces I see main line as 6 digits no matter where its called from for the others I see as 8 digits when dialed outside of Germany and between 6 & 7 when called from national numbers .

cheers : )

ayavauser

 

[ayavauser]

many thanks as that did the trick !!!


cheers: )

ayavauser

 

[CHEEZUSCRAIZT]

Hi avayauser,

what did the trick?

Did you edit the ARS & AAR?

Greets
Jens

 

[Nick44]

Hi avayauser,
I would like to know too.
I had the same issue with the main number being a shorter lenght, and thought that maybe I needed to create a virtual extension with a cover path as a work-around, but it wasn't needed. It just worked anyway, but with a slightly longer routing time (milliseconds)
I think that unlike enbloc, it just waits and then goes, huh! no more digits, then routes accoring to what's recived.
N.


Speak softly and carry a big switch