We are marine vessel and we have an issue with certain DECT handsets not being able to dial out externally.
We have tried using our usual remote support but the VSAT signal has not been great (insufficient bandwidth & high lag coupled with slow response from the unit when Telnetting in). I have been handed this as I help out with all the IT on board.
My issue is:
Most phones can dial out (this includes some DECT hand sets), these all dial out with the same calling number.
Some desk phones with their own dedicated numbers can dial out ok.
DECT handsets with the same dedicated numbers cannot dial out (don't know if it is do with the additional part of the calling number being concatenated - in red).
t3 trace for failed number:
mtracer started ... (326010:000001) MTRACER host (192.168.130.50, cpu_a), version: R9.1-i1.605-21-e-no-c82 (326010:000001) MTRACER num: 008, time: 2020/06/08 11:17:52, loss: 0% ______________________________________________________________________________ | (326297:000002) 1260: Send_IO1 (link-nbr=1, sapi=0, tei=0) : | long: 66 desti: 0 source: 15 cryst: 2 cpl: 6 us: 8 term: 0 type a5 | tei: 0 <<<< message sent : SETUP [05] Call ref : 01 29 |______________________________________________________________________________ | | IE:[04] BEARER_CAPABILITY (l=3) 80 90 a3 | IE:[6c] CALLING_NUMBER (l=18) -> 21 81 Num : 4723671813671813 | IE:[70] CALLED_NUMBER (l=16) -> 81 Num : 000447710741063 | IE:[7d] HLC (l=2) 91 81 | [a1] Sending complete |______________________________________________________________________________ ______________________________________________________________________________ | (326298:000004) Concatenated-Physical-Event : | long: 23 desti: 0 source: 0 cryst: 2 cpl: 6 us: 0 term: 0 type a5 | tei: 0 >>>> message received : CALL PROC (02) Call ref : 81 29 |______________________________________________________________________________ | | IE:[18] CHANNEL (l=3) a9 83 82 -> T2 : B channel 2 exclusive |______________________________________________________________________________ ______________________________________________________________________________ | (326324:000005) Concatenated-Physical-Event : | long: 22 desti: 0 source: 0 cryst: 2 cpl: 6 us: 0 term: 0 type a5 | tei: 0 >>>> message received : DISCONNECT [45] Call ref : 81 29 |______________________________________________________________________________ | | IE:[08] CAUSE (l=2) 82 b9 -> [b9] BEARER CAPABILITY NOT AUTHORIZED |______________________________________________________________________________
(sorry not sure how to sort the formatting)
t3 trace for successful:
(327285:000016) Concatenated-Physical-Event : | long: 18 desti: 0 source: 0 cryst: 2 cpl: 6 us: 0 term: 0 type a5 | tei: 0 >>>> message received : REL COMP [5a] Call ref : 81 2a |______________________________________________________________________________ ______________________________________________________________________________ | (328301:000017) 1262: Send_IO1 (link-nbr=1, sapi=0, tei=0) : | long: 60 desti: 0 source: 15 cryst: 2 cpl: 6 us: 8 term: 0 type a5 | tei: 0 <<<< message sent : SETUP [05] Call ref : 01 2b |______________________________________________________________________________ | | IE:[04] BEARER_CAPABILITY (l=3) 80 90 a3 | IE:[6c] CALLING_NUMBER (l=12) -> 21 81 Num : 4723671809 | IE:[70] CALLED_NUMBER (l=16) -> 81 Num : 000447710741063 | IE:[7d] HLC (l=2) 91 81 | [a1] Sending complete |______________________________________________________________________________ ______________________________________________________________________________ | (328302:000019) Concatenated-Physical-Event : | long: 23 desti: 0 source: 0 cryst: 2 cpl: 6 us: 0 term: 0 type a5 | tei: 0 >>>> message received : CALL PROC (02) Call ref : 81 2b |______________________________________________________________________________ | | IE:[18] CHANNEL (l=3) a9 83 81 -> T2 : B channel 1 exclusive |______________________________________________________________________________ ______________________________________________________________________________ | (328334:000020) Concatenated-Physical-Event : | long: 18 desti: 0 source: 0 cryst: 2 cpl: 6 us: 0 term: 0 type a5 | tei: 0 >>>> message received : ALERT (01) Call ref : 81 2b |______________________________________________________________________________ ______________________________________________________________________________ | (328337:000021) Concatenated-Physical-Event : | long: 18 desti: 0 source: 0 cryst: 2 cpl: 6 us: 0 term: 0 type a5 | tei: 0 >>>> message received : CONNECT (07) Call ref : 81 2b |______________________________________________________________________________ ______________________________________________________________________________ | (328337:000022) 1262: Send_IO1 (link-nbr=1, sapi=0, tei=0) : | long: 18 desti: 0 source: 15 cryst: 2 cpl: 6 us: 8 term: 0 type a5 | tei: 0 <<<< message sent : CONNECT ACK (0f) Call ref : 01 2b |______________________________________________________________________________ ______________________________________________________________________________ | (328365:000023) 1262: Send_IO1 (link-nbr=1, sapi=0, tei=0) : | long: 22 desti: 0 source: 15 cryst: 2 cpl: 6 us: 8 term: 0 type a5 | tei: 0 <<<< message sent : DISCONNECT [45] Call ref : 01 2b |______________________________________________________________________________ | | IE:[08] CAUSE (l=2) 81 90 -> [90] NORMAL CALL CLEARING |______________________________________________________________________________
Please let me know if anyone can help and the cost.
Thank you in advance
Alec
OmniPCX OXE Dialling out issues - Help needed
- frank
- Alcatel Unleashed Certified Guru
- Posts: 3169
- Joined: 06 Jul 2004 00:18
- Location: New York
- Contact:
Re: OmniPCX OXE Dialling out issues - Help needed
Hi Alec,
Do they use the same prefix?
It looks like in your working case, 10 digits are sent to the carrier, while the non working case sends 16 digits.
Do they use the same prefix?
It looks like in your working case, 10 digits are sent to the carrier, while the non working case sends 16 digits.
Code Free Or Die
Re: OmniPCX OXE Dialling out issues - Help needed
Hi Frank
Thanks for taking the time to reply. I'm not sure on the prefix for the calling number, can you point me in the right direction to check please?
Think I have more of an idea now, it appears that the calling number is Country Code + Entity + DID for the mis-formed calling numbers
DID table:
DID Mode : 0 , nb :9 DID slice 1 : start ext : 671809 start int : 100 sort : 1 size 1, unique int.:NO, in range:0, thin sector:0 DID slice 8 : start ext : 671816 start int : 307 sort : 6 size 1, unique int.:NO, in range:0, thin sector:0 DID slice 2 : start ext : 671810 start int : 900 sort : 8 size 1, unique int.:NO, in range:0, thin sector:0 DID slice 3 : start ext : 671811 start int : 902 sort : 2 size 1, unique int.:NO, in range:0, thin sector:0 DID slice 4 : start ext : 671812 start int : 913 sort : 3 size 1, unique int.:NO, in range:0, thin sector:0 DID slice 5 : start ext : 671813 start int : 914 sort : 4 size 1, unique int.:NO, in range:0, thin sector:0 DID slice 7 : start ext : 671815 start int : 915 sort : 7 size 1, unique int.:NO, in range:0, thin sector:0 DID slice 6 : start ext : 671814 start int : 916 sort : 5 size 1, unique int.:NO, in range:0, thin sector:0
Our users are: 101-880 are wired handsets 900-924 are wireless DECT handsets (It is the users listed DID Slices 2-6)
(Finally got the docs to download, it has taken a number of attempts to get them (our VSAT connection), having a read through the external callback translator section at the moment.)
I hope this info is of help
Kind regards
Alec
Thanks for taking the time to reply. I'm not sure on the prefix for the calling number, can you point me in the right direction to check please?
Think I have more of an idea now, it appears that the calling number is Country Code + Entity + DID for the mis-formed calling numbers
DID table:
DID Mode : 0 , nb :9 DID slice 1 : start ext : 671809 start int : 100 sort : 1 size 1, unique int.:NO, in range:0, thin sector:0 DID slice 8 : start ext : 671816 start int : 307 sort : 6 size 1, unique int.:NO, in range:0, thin sector:0 DID slice 2 : start ext : 671810 start int : 900 sort : 8 size 1, unique int.:NO, in range:0, thin sector:0 DID slice 3 : start ext : 671811 start int : 902 sort : 2 size 1, unique int.:NO, in range:0, thin sector:0 DID slice 4 : start ext : 671812 start int : 913 sort : 3 size 1, unique int.:NO, in range:0, thin sector:0 DID slice 5 : start ext : 671813 start int : 914 sort : 4 size 1, unique int.:NO, in range:0, thin sector:0 DID slice 7 : start ext : 671815 start int : 915 sort : 7 size 1, unique int.:NO, in range:0, thin sector:0 DID slice 6 : start ext : 671814 start int : 916 sort : 5 size 1, unique int.:NO, in range:0, thin sector:0
Our users are: 101-880 are wired handsets 900-924 are wireless DECT handsets (It is the users listed DID Slices 2-6)
(Finally got the docs to download, it has taken a number of attempts to get them (our VSAT connection), having a read through the external callback translator section at the moment.)
I hope this info is of help
Kind regards
Alec
Last edited by Alec on 11 Jun 2020 02:26, edited 2 times in total.
- frank
- Alcatel Unleashed Certified Guru
- Posts: 3169
- Joined: 06 Jul 2004 00:18
- Location: New York
- Contact:
Re: OmniPCX OXE Dialling out issues - Help needed
In both case, what does a user which work dial exactly, and what does a user which doesn't work dials?
No need to enter the full number in here, just show the prefix, and XXXXXX for number dialed.
No need to enter the full number in here, just show the prefix, and XXXXXX for number dialed.
Code Free Or Die
Re: OmniPCX OXE Dialling out issues - Help needed
Hi Frank,
0 for outside line then full international eg:
0 0044 xxxxxxxxxx
(the same for both cases)
Update: 12-06-20
Hi Frank,
Managed a workaround, as it was sending entity (as full international)+ DID as (as local) calling_number I just edited the local part out of the entity giving me a usable number that our VSAT providers equipment accepts for the DID listed users. I can now take the time to read through the documentation properly. On the plus side our company has agreed to send two members of the crew on a course, shame I won't get one of the places.
Thanks for your help.
0 for outside line then full international eg:
0 0044 xxxxxxxxxx
(the same for both cases)
Update: 12-06-20
Hi Frank,
Managed a workaround, as it was sending entity (as full international)+ DID as (as local) calling_number I just edited the local part out of the entity giving me a usable number that our VSAT providers equipment accepts for the DID listed users. I can now take the time to read through the documentation properly. On the plus side our company has agreed to send two members of the crew on a course, shame I won't get one of the places.
Thanks for your help.
Last edited by Alec on 12 Jun 2020 08:29, edited 1 time in total.
Re: OmniPCX OXE Dialling out issues - Help needed
what if u set the installation number& supl inst number Under npd (as npd source)
eview/Modify: Numbering_Plan_Descriptor (NPD)qqqqqqqqqqqqqqqqqqqqqqqk
x x
x Node Number (reserved) : 1 x
x Instance (reserved) : 1 x
x Instance (reserved) : 1 x
x Description identifier : 35 x
x x
x Name : Algerie_Telcom x
x Calling Numbering plan ident. + NPI/TON Isdn National x
x Called numbering plan ident. + NPI/TON Isdn National x
x Authorize personal calling num use + True x
x Install. number source + NPD source x
x Default number source + NPD source x
x Called DID identifier : 2 x
x Calling/Connected DID identifier : 2 x
x Installation number : 0XXXX x
x Default number( num. inst. sup.) : 2020
DID SAMPLE
Node Number (reserved) : 1 x
x Instance (reserved) : 1 x
x Instance (reserved) : 1 x
x DDI num. transl. identifier : 2 x
x First External Number : 2000 x
x x
x First Internal Number : 51009 x
x Range Size : 1 x
x Unique Internal Number + YES
BTW those dect are Tandem set for wired lines orare them free line ?
eview/Modify: Numbering_Plan_Descriptor (NPD)qqqqqqqqqqqqqqqqqqqqqqqk
x x
x Node Number (reserved) : 1 x
x Instance (reserved) : 1 x
x Instance (reserved) : 1 x
x Description identifier : 35 x
x x
x Name : Algerie_Telcom x
x Calling Numbering plan ident. + NPI/TON Isdn National x
x Called numbering plan ident. + NPI/TON Isdn National x
x Authorize personal calling num use + True x
x Install. number source + NPD source x
x Default number source + NPD source x
x Called DID identifier : 2 x
x Calling/Connected DID identifier : 2 x
x Installation number : 0XXXX x
x Default number( num. inst. sup.) : 2020
DID SAMPLE
Node Number (reserved) : 1 x
x Instance (reserved) : 1 x
x Instance (reserved) : 1 x
x DDI num. transl. identifier : 2 x
x First External Number : 2000 x
x x
x First Internal Number : 51009 x
x Range Size : 1 x
x Unique Internal Number + YES
BTW those dect are Tandem set for wired lines orare them free line ?
Re: OmniPCX OXE Dialling out issues - Help needed
ALSO manage did selection Under Trunkgroup