ISDN "Connected number" sent by OXE - how can I manage it?

Are you having any trouble while you are configuring a 4400 on site ? Share it with us, maybe someone will have the solution !
mkrustev

ISDN "Connected number" sent by OXE - how can I manage it?

Post by mkrustev »

Hi Guys,
I have a strange problem with one client of mine:

I have an ISDN - T2 link towards the operator.
I have a DID translator routing 139 external number to 39 internal.

If I dial 139 I get connected to 39, but I see
the OXE return "connected number"(which is ISDN information element) different 139 (something much longer and incorrect) and I need to have either nothing returned or the exact number I dialled.

Any ideas on how can I manage/modify the "connected number" returned by OXE?

Regards,
Milen
mkrustev

Re: ISDN "Connected number" sent by OXE - how can I manage it?

Post by mkrustev »

As I understand this ISDN (so to say:)) feature is also called COLP: Presentation of the actual number reached
vad
Alcatel Unleashed Certified Guru
Alcatel Unleashed Certified Guru
Posts: 3852
Joined: 23 Sep 2004 06:47

Re: ISDN "Connected number" sent by OXE - how can I manage it?

Post by vad »

If you not use personal calling number (Authorize personal calling number use=true in NPD) - CONNECTED number will be the same like for outgoing call (installation number+DID number).
Show t3 trace, NPD from TG, DID rules.
mkrustev

Re: ISDN "Connected number" sent by OXE - how can I manage it?

Post by mkrustev »

I don't know where to look for the COLP (Connected Number) in the t3 trace.
Here is some t3 output:

Code: Select all

 ______________________________________________________________________________
| (993242:002506) Physical-Event :
| long: 52  desti: 0  source: 0  cryst: 2  cpl: 14  us: 0  term: 1  type a5
| tei: 0  >>>>  message received : SETUP [05]    Call ref :  16 fd
|                               SENDING COMPLETE
|______________________________________________________________________________
|
| IE:[04] BEARER_CAPABILITY (l=3) 90 90 a3
| IE:[18] CHANNEL (l=3)  a1 83 8f -> T2 : B channel 15 preferred
| IE:[1e] PROGRESS_ID (l=2) 82 83
| IE:[6c] CALLING_NUMBER (l=11)  ->  21  83  Num : 076670385
| IE:[70] CALLED_NUMBER (l=4)  ->  c1  Num : 123
|______________________________________________________________________________

 ______________________________________________________________________________
| (993242:002507) 1509: Send_IO1 (link-nbr=1, sapi=0, tei=0) :
| long: 23  desti: 0  source: 15  cryst: 2  cpl: 14  us: 8  term: 1  type a5
| tei: 0  <<<<  message sent : CALL PROC (02)  Call ref :  96 fd
|______________________________________________________________________________
|
| IE:[18] CHANNEL (l=3)  a9 83 8f -> T2 : B channel 15 exclusive
|______________________________________________________________________________

 ______________________________________________________________________________
| (993242:002508) 1509: Send_IO1 (link-nbr=1, sapi=0, tei=0) :
| long: 22  desti: 0  source: 15  cryst: 2  cpl: 14  us: 8  term: 1  type a5
| tei: 0  <<<<  message sent : ALERT (01)  Call ref :  96 fd
|______________________________________________________________________________
|
| IE:[1e] PROGRESS_ID (l=2) 81 88
|______________________________________________________________________________

 ______________________________________________________________________________
| (993243:002509) 1509: Send_IO1 (link-nbr=1, sapi=0, tei=0) :
| long: 18  desti: 0  source: 15  cryst: 2  cpl: 14  us: 8  term: 1  type a5
| tei: 0  <<<<  message sent : CONNECT (07)  Call ref :  96 fd
|______________________________________________________________________________

 ______________________________________________________________________________
| (993244:002510) Physical-Event :
| long: 22  desti: 0  source: 0  cryst: 2  cpl: 18  us: 0  term: 1  type a5
| tei: 0  >>>>  message received : DISCONNECT [45]  Call ref :  0a 81
|______________________________________________________________________________
|
| IE:[08] CAUSE (l=2) 82 90 -> [90] NORMAL CALL CLEARING
In the external callback translator I have DEF.
DID Rules are trivial, NPD:

Code: Select all


 ┌─Consult/Modify: Numbering Plan Description (NPD)─────────────────────┐
 │                                                                      │
 │             Node Number (reserved) : 1                               │
 │                Instance (reserved) : 1                               │
 │                Instance (reserved) : 1                               │
 │             Description identifier : 33                              │
 │                                                                      │
 │                               Name : OutgoingCLIP                    │
 │      Calling Numbering plan ident. + NPI/TON : Isdn Unknown          │
 │       Called numbering plan ident. + NPI/TON : Isdn Unknown          │
 │ Authorize personal calling num use + False                           │
 │             Install. number source + Entity source                   │
 │              Default number source + Entity source                   │
 │              Called DID identifier : 1                               │
 │   Calling/Connected DID identifier : 0                               │
 │                                                                      │
 └──────────────────────────────────────────────────────────────────────┘

mkrustev

Re: ISDN "Connected number" sent by OXE - how can I manage it?

Post by mkrustev »

The number I am getting is: 202892510000E000030, which is strange..
vad
Alcatel Unleashed Certified Guru
Alcatel Unleashed Certified Guru
Posts: 3852
Joined: 23 Sep 2004 06:47

Re: ISDN "Connected number" sent by OXE - how can I manage it?

Post by vad »

Why you use DID 1 for incoming and 0 for outgoing/connected number (NPD 33)?
In message CONNECT you have no connected number.
manage
Called DID identifier : 1
Calling/Connected DID identifier : 1 !!!
mkrustev

Re: ISDN "Connected number" sent by OXE - how can I manage it?

Post by mkrustev »

Even if I manage both calling and called to be the same DID 1, I still get that long and strange number in return..
Have you had such issue?
User avatar
tot3nkopf
Alcatel Unleashed Certified Guru
Alcatel Unleashed Certified Guru
Posts: 4058
Joined: 02 Feb 2006 10:41
Location: Germany & Romania
Contact:

Re: ISDN "Connected number" sent by OXE - how can I manage it?

Post by tot3nkopf »

mkrustev wrote:Even if I manage both calling and called to be the same DID 1, I still get that long and strange number in return..
Have you had such issue?
I have seen this once. I had no solution for it (the translation doesn't work --- made lots of tests with both automatic and normal translation).
knightr1der

Re: ISDN "Connected number" sent by OXE - how can I manage it?

Post by knightr1der »

can you export your TG config and show it to us here?

edit add:
also please show us how you managed which NPD the TG must use and the settings for that 'External Service' (under TG)
User avatar
alex
Senior Member
Posts: 1498
Joined: 06 Jul 2004 07:27
Contact:

Re: ISDN "Connected number" sent by OXE - how can I manage it?

Post by alex »

mkrustev wrote: I see
the OXE return "connected number"(which is ISDN information element) different 139 (something much longer and incorrect)
in traces you suppliied there is no CONNECTED NUMBER IE sent by OXE.
Where do you see "something much longer and incorrect" number? On mobile phone display? Then it is your operator/GSM provider who supplies this number.
If it looks like a duck, swims like a duck, and quacks like a duck, then it probably is a duck.
Post Reply

Return to “ON SITE TROUBLES”