vpn overflow with node in czech rep

alexeik
Member
Posts: 255
Joined: 26 Apr 2007 10:47
Location: Bad Oeynhausen, germany

vpn overflow with node in czech rep

Post by alexeik » 20 May 2016 05:05

Hi

i have the following problem, i have installed an OXE 11.2 in czech republic, and set up a vpn overflow the the main node in germany. The network contains already several nodes in different countries in europe. But now i have an sip line from vodafone with an audiocodes which provide 4 bri ports to oxe. If i do an outside call only extensions with a correct calling number are working, all other call are discarded. so far so good... But vpn calls are made without a calling number, so these calls are also discarded. Did anyone hab a similar problem?

Then i tried to use ip trunks, but these doesn´t work either. But maybe this is release problem, all other nodes are R10, and this new one is R11.2

greeting Alex

User avatar
tot3nkopf
Alcatel Unleashed Certified Guru
Alcatel Unleashed Certified Guru
Posts: 4020
Joined: 02 Feb 2006 10:41
Location: Germany & Romania
Contact:

Re: vpn overflow with node in czech rep

Post by tot3nkopf » 20 May 2016 05:32

We have a node also in CZ - no issues. (deployed with country tones and so on for CZ)

VPN calls you mean break out calls through the BRI trunks in CZ node? The provider should not drop but use the default DDI of the trunk. Otherwise you need to translate everything that does not match to the default DDI or hide numbers.

Can you show a trace of outgoing call discared?

alexeik
Member
Posts: 255
Joined: 26 Apr 2007 10:47
Location: Bad Oeynhausen, germany

Re: vpn overflow with node in czech rep

Post by alexeik » 20 May 2016 05:56

hi

no prob, heres a t3 from such a call...
(105)xa001005> t3
--> Cleaning mtracer...
--> Positionning t3 filters...
+--------+-------+--------+--------+---------+---------+----------+------+
| filter | desti | src_id | cr_nbr | cpl_nbr | us_term | term_nbr | type |
+--------+-------+--------+--------+---------+---------+----------+------+
| 0 | ** | ** | * | ** | * | *** | 165 |
| 1 | ** | ** | * | ** | * | *** | 166 |
| 2 | ** | ** | * | ** | * | *** | 167 |
| 3 | | | | | | | |
| 4 | | | | | | | |
| 5 | | | | | | | |
| 6 | | | | | | | |
| 7 | | | | | | | |
+--------+-------+--------+--------+---------+---------+----------+------+
Traces Analyser activated

mtracer started ...
(462770:000001) MTRACER host (192.168.130.180, xa001005), version: R11.2-l2.300-
25-c-cz-c82
(462770:000001) MTRACER num: 007, time: 2016/05/20 11:51:45, loss: 0%
______________________________________________________________________________
| (462861:000002) Concatenated-Physical-Event :
| long: 55 desti: 0 source: 0 cryst: 2 cpl: 9 us: 0 term: 0 type a5
| tei: 0 >>>> message received : SETUP [05] Call ref : 3c
|______________________________________________________________________________
|
| IE:[04] BEARER_CAPABILITY (l=3) 90 90 a3
| IE:[18] CHANNEL (l=1) 89 -> T0/S0 : B1 channel exclusive
| IE:[6c] CALLING_NUMBER (l=15) -> 00 80 Num : 0049xxxxxxxxxx
| IE:[70] CALLED_NUMBER (l=10) -> 80 Num : 38xxxxxxx
| [a1] Sending complete
|______________________________________________________________________________

______________________________________________________________________________
| (462861:000003) 1127: Send_IO1 (link-nbr=1, sapi=0, tei=0) :
| long: 20 desti: 0 source: 15 cryst: 2 cpl: 9 us: 8 term: 0 type a5
| tei: 0 <<<< message sent : CALL PROC (02) Call ref : bc
|______________________________________________________________________________
|
| IE:[18] CHANNEL (l=1) 89 -> T0/S0 : B1 channel exclusive
|______________________________________________________________________________

______________________________________________________________________________
| (462861:000004) 1127: Send_IO1 (link-nbr=1, sapi=0, tei=0) :
| long: 50 desti: 0 source: 15 cryst: 2 cpl: 9 us: 8 term: 0 type a5
| tei: 0 <<<< message sent : SETUP [05] Call ref : 01
|______________________________________________________________________________
|
| IE:[04] BEARER_CAPABILITY (l=3) 90 90 a3
| IE:[18] CHANNEL (l=1) 8a -> T0/S0 : B2 channel exclusive
| IE:[6c] CALLING_NUMBER (l=1) -> 81 Num :
| IE:[70] CALLED_NUMBER (l=15) -> 81 Num : 0049xxxxxxx297
| IE:[7d] HLC (l=2) 91 81
| [a1] Sending complete
|______________________________________________________________________________

______________________________________________________________________________
| (462862:000005) Concatenated-Physical-Event :
| long: 20 desti: 0 source: 0 cryst: 2 cpl: 9 us: 0 term: 0 type a5
| tei: 0 >>>> message received : CALL PROC (02) Call ref : 81
|______________________________________________________________________________
|
| IE:[18] CHANNEL (l=1) 8a -> T0/S0 : B2 channel exclusive
|______________________________________________________________________________

______________________________________________________________________________
| (462863:000006) Concatenated-Physical-Event :
| long: 21 desti: 0 source: 0 cryst: 2 cpl: 9 us: 0 term: 0 type a5
| tei: 0 >>>> message received : DISCONNECT [45] Call ref : 81
|______________________________________________________________________________
|
| IE:[08] CAUSE (l=2) 80 81 -> [81] UNALLOCATED NUMBER
|______________________________________________________________________________

______________________________________________________________________________
| (462863:000007) 1127: Send_IO1 (link-nbr=1, sapi=0, tei=0) :
| long: 21 desti: 0 source: 15 cryst: 2 cpl: 9 us: 8 term: 0 type a5
| tei: 0 <<<< message sent : RELEASE [4d] Call ref : 01
|______________________________________________________________________________
|
| IE:[08] CAUSE (l=2) 85 90 -> [90] NORMAL CALL CLEARING
|______________________________________________________________________________

______________________________________________________________________________
| (462863:000008) 1127: Send_IO1 (link-nbr=1, sapi=0, tei=0) :
| long: 21 desti: 0 source: 15 cryst: 2 cpl: 9 us: 8 term: 0 type a5
| tei: 0 <<<< message sent : DISCONNECT [45] Call ref : bc
|______________________________________________________________________________
|
| IE:[08] CAUSE (l=2) 85 9b -> [9b] DESTINATION OUT OF ORDER
|______________________________________________________________________________

______________________________________________________________________________
| (462864:000009) Concatenated-Physical-Event :
| long: 17 desti: 0 source: 0 cryst: 2 cpl: 9 us: 0 term: 0 type a5
| tei: 0 >>>> message received : REL COMP [5a] Call ref : 81
|______________________________________________________________________________

______________________________________________________________________________
| (462864:000010) Concatenated-Physical-Event :
| long: 17 desti: 0 source: 0 cryst: 2 cpl: 9 us: 0 term: 0 type a5
| tei: 0 >>>> message received : RELEASE [4d] Call ref : 3c
|______________________________________________________________________________

______________________________________________________________________________
| (462864:000011) 1127: Send_IO1 (link-nbr=1, sapi=0, tei=0) :
| long: 21 desti: 0 source: 15 cryst: 2 cpl: 9 us: 8 term: 0 type a5
| tei: 0 <<<< message sent : REL COMP [5a] Call ref : bc
|______________________________________________________________________________
|
| IE:[08] CAUSE (l=2) 85 90 -> [90] NORMAL CALL CLEARING
|______________________________________________________________________________


(105)xa001005>

the first entry is my incoming call to a set in czech, which is forwarded to a set in the node in germany, so i can generate a vpn call from here.
The entry with 297 at the end is the vpn call

alexeik
Member
Posts: 255
Joined: 26 Apr 2007 10:47
Location: Bad Oeynhausen, germany

Re: vpn overflow with node in czech rep

Post by alexeik » 20 May 2016 05:57

i created the node with cz insatallation and database...

i know that the provider drops the call because i already created the numbers which are not transfered to the new location yet. but they got 10 new numbers, and these are working. the vpn overflow is one of the new numbers and is transcoded correctly...

User avatar
tot3nkopf
Alcatel Unleashed Certified Guru
Alcatel Unleashed Certified Guru
Posts: 4020
Joined: 02 Feb 2006 10:41
Location: Germany & Romania
Contact:

Re: vpn overflow with node in czech rep

Post by tot3nkopf » 20 May 2016 06:00

They complain about the dialed number not about the user number.

alexeik
Member
Posts: 255
Joined: 26 Apr 2007 10:47
Location: Bad Oeynhausen, germany

Re: vpn overflow with node in czech rep

Post by alexeik » 20 May 2016 06:09

i know, but how can i change the calling number for a vpn call? I already use a vpn prefix which is transcoded to a working external number.(see quote)

i don´t know any other way...


The forwarding is only for testing because there is nobody at the new side to make a vpn testcall..

(105)xa001005> lookvpn -test

Fri May 20 12:03:34 CEST 2016



***************************************************************************

VPN is ALLOWED

* nodes 1 -- 2 (netw 15 -- netw 15) cost 1 mandatory q0 : Y q1 : Y
* nodes 1 -- 3 (netw 15 -- netw 15) cost 1 mandatory q0 : Y q1 : Y
* nodes 1 -- 4 (netw 15 -- netw 15) cost 1 mandatory q0 : Y q1 : Y
* nodes 1 -- 5 (netw 15 -- netw 15) cost 1 mandatory q0 : Y q1 : Y
* nodes 1 -- 6 (netw 15 -- netw 15) cost 1 mandatory q0 : Y q1 : Y
* nodes 1 -- 7 (netw 15 -- netw 15) cost 1 mandatory q0 : Y q1 : Y
* nodes 1 -- 8 (netw 15 -- netw 15) cost 1 mandatory q0 : Y q1 : Y

Checking trunk groups corresponding to local hop to node 1 ( 1 -- 5)

+ Trunk group 50 : name = Amt CZ state : FREE
trk_type T0 next_trk_grp = -1 variant ISDN
nb_chif_uti = 0
x25 ok. vpnRate = 50 immTrkForVpn = 1
Public NPD 50 Incoming DID 5
Private NPD 0 Incoming DID -1

+ Trunk group 51 : name = IP state : FREE
trk_type T2 next_trk_grp = -1 variant ISDN
nb_chif_uti = 0 specificity : IP
x25 ok. vpnRate = 100 immTrkForVpn = 0
Public NPD 9 Incoming DID -1
Private NPD 0 Incoming DID -1

WARNING : another NPD can be used (depends on the byte3 of the called number)
Verify which NPD is used on arrival with looknumin


***************************************************************************

Table of vpn numbers for the local node

Index | State | Eqt<-> | NPD | VPN Local Nber | Ext.Transl. | VPN DDI Nber |SDA
trad.
_____ | _____ | ______ | ___ | _______________|_____________|______________|____
_____
0 | Free | None | 51 | 8380 | 3xxxxx380 | 004203xxxxx380
| 5
_____ | _____ | ______ | ___ | _______________|_____________|______________|____
_____


***************************************************************************

External Call Back Translator Tables

1) beginning_of_number = A nb_digits_to_suppr = 1 number_to_add = 00
2) beginning_of_number = DEF nb_digits_to_suppr = 0 number_to_add = 0



***************************************************************************

Table of distant vpn numbers

297 Tsl_Distant_VPN_Number RLN 51
---------------------------------------
Rout List ARS 51

1) trk_grp=50 nb_deleted_digits=0 inserted_digits = 0049xxxxxxx vpnCostL
imit=0 (ie. 0049xxxxxx297)

298 Tsl_Distant_VPN_Number RLN 51
---------------------------------------
Rout List ARS 51

1) trk_grp=50 nb_deleted_digits=0 inserted_digits = 0049xxxxxxx vpnCostL
imit=0 (ie. 0049xxxxxxx298)

299 Tsl_Distant_VPN_Number RLN -1
---------------------------------------
NO ROUT LIST

6498 Tsl_Distant_VPN_Number RLN 58
---------------------------------------
Rout List ARS 58

1) trk_grp=50 nb_deleted_digits=1 inserted_digits = 0049xxxxxxxxxxx vpnCostL
imit=0 (ie. 004957xxxxxxxxxxxxxxx)

6499 Tsl_Distant_VPN_Number RLN 58
---------------------------------------
Rout List ARS 58

1) trk_grp=50 nb_deleted_digits=1 inserted_digits = 0049xxxxxxxx vpnCostL
imit=0 (ie. 0049xxxxxxxxxxx9)

8179 Tsl_Distant_VPN_Number RLN -1
---------------------------------------
NO ROUT LIST

8297 Tsl_Distant_VPN_Number RLN -1
---------------------------------------
NO ROUT LIST

8448 Tsl_Distant_VPN_Number RLN -1
---------------------------------------
NO ROUT LIST

8598 Tsl_Distant_VPN_Number RLN -1
---------------------------------------
NO ROUT LIST



***************************************************************************

Value of VPN synchronisation timer --> T_VPN_SYNCHRO = 300

***************************************************************************
(105)xa001005>

User avatar
tot3nkopf
Alcatel Unleashed Certified Guru
Alcatel Unleashed Certified Guru
Posts: 4020
Joined: 02 Feb 2006 10:41
Location: Germany & Romania
Contact:

Re: vpn overflow with node in czech rep

Post by tot3nkopf » 20 May 2016 06:19

Can you use t3 trace only in the T0 trunk group (e.g. t3 C=X c=y)?

Can you dial locally from CZ PBX same number and attach that trace also?

alexeik
Member
Posts: 255
Joined: 26 Apr 2007 10:47
Location: Bad Oeynhausen, germany

Re: vpn overflow with node in czech rep

Post by alexeik » 20 May 2016 06:28

Unfortunately not, because there is nobody at the new location at the moment, they move in two weeks.
The IP trunk is not used at the moment...

User avatar
tot3nkopf
Alcatel Unleashed Certified Guru
Alcatel Unleashed Certified Guru
Posts: 4020
Joined: 02 Feb 2006 10:41
Location: Germany & Romania
Contact:

Re: vpn overflow with node in czech rep

Post by tot3nkopf » 20 May 2016 06:34

I do not think the VPN calling is the problem. Have you truied to call a number from CZ?

alexeik
Member
Posts: 255
Joined: 26 Apr 2007 10:47
Location: Bad Oeynhausen, germany

Re: vpn overflow with node in czech rep

Post by alexeik » 20 May 2016 06:48

i was there last week and i could dial normally.

what i faced is the following. the customer got 10 new external numbers (38x xxx x80 - 89) which are already o nthe the pbx. The old external numbers willl be transfered to the new side when they move (383 xxx x20 - 29). I created all numbers and sets, and tried to call out with a set with an old number by accident. So the call failed because of unallocated number.

Code: Select all

| IE:[6c] CALLING_NUMBER (l=1) -> 81 Num : 383 xxx x29			(old number)
| IE:[70] CALLED_NUMBER (l=15) -> 81 Num : 705 xxx xxx
then i took a set with an new external number and all is working fine.

Code: Select all

| IE:[6c] CALLING_NUMBER (l=1) -> 81 Num : 380 xxx x81			(new number)
| IE:[70] CALLED_NUMBER (l=15) -> 81 Num : 705 xxx xxx
so i think is can only call out if the calling number is filled and correct

and in case of vpn the calling number is not filled... but how can i make the pbx fill it

Post Reply

Return to “Inter-Node Links”