Calling number modification?!

vad
Alcatel Unleashed Certified Guru
Alcatel Unleashed Certified Guru
Posts: 3851
Joined: 23 Sep 2004 06:47

Re: Calling number modification?!

Post by vad »

Show t3 trace (incoming and outgoing) - with 0+number and 9+number.
Check trace - may be you have additional message (like "progress" - you can disable in local TG param),
or in incoming setup you have "bearer cap=90 90 a3" but in route declared only quality "speach" (absent "fax")
Billy

Re: Calling number modification?!

Post by Billy »

Here's the output of t3... I deleted the "9" prefix and created "6" - ARS Prof TG with ovl, in case something's wrong with the old one.
Dialling 6,3800080 from the client's pbx thru TG 10:

Code: Select all

(873571:000001) MTRACER num: 024, time: 2011/04/01 18:16:09, loss: 0%
 ______________________________________________________________________________
| (873650:000002) Concatenated-Physical-Event :
| long: 42  desti: 0  source: 0  cryst: 1  cpl: 5  us: 0  term: 0  type a5
| tei: 0  >>>>  message received : SETUP [05]    Call ref :  58 6b
|______________________________________________________________________________
|
| IE:[04] BEARER_CAPABILITY (l=3) 90 90 a3
| IE:[18] CHANNEL (l=3)  a9 83 8f -> T2 : B channel 15 exclusive
| IE:[1e] PROGRESS_ID (l=2) 81 83
| IE:[6c] CALLING_NUMBER (l=8)  ->  c1  Num : 3803664
|______________________________________________________________________________

 ______________________________________________________________________________
| (873650:000003) 1097: Send_IO1 (link-nbr=1, sapi=0, tei=0) :
| long: 23  desti: 0  source: 15  cryst: 1  cpl: 5  us: 8  term: 0  type a5
| tei: 0  <<<<  message sent : SETUP ACK [0d]  Call ref :  d8 6b
|______________________________________________________________________________
|
| IE:[18] CHANNEL (l=3)  a9 83 8f -> T2 : B channel 15 exclusive
|______________________________________________________________________________

 ______________________________________________________________________________
| (873653:000004) Concatenated-Physical-Event :
| long: 22  desti: 0  source: 0  cryst: 1  cpl: 5  us: 0  term: 0  type a5
| tei: 0  >>>>  message received : INFORMATION [7b]  Call ref :  58 6b
|______________________________________________________________________________
|
| IE:[70] CALLED_NUMBER (l=2)  ->  81  Num : 6
|______________________________________________________________________________

 ______________________________________________________________________________
| (873654:000005) Concatenated-Physical-Event :
| long: 22  desti: 0  source: 0  cryst: 1  cpl: 5  us: 0  term: 0  type a5
| tei: 0  >>>>  message received : INFORMATION [7b]  Call ref :  58 6b
|______________________________________________________________________________
|
| IE:[70] CALLED_NUMBER (l=2)  ->  81  Num : 3
|______________________________________________________________________________

 ______________________________________________________________________________
| (873655:000006) Concatenated-Physical-Event :
| long: 22  desti: 0  source: 0  cryst: 1  cpl: 5  us: 0  term: 0  type a5
| tei: 0  >>>>  message received : INFORMATION [7b]  Call ref :  58 6b
|______________________________________________________________________________
|
| IE:[70] CALLED_NUMBER (l=2)  ->  81  Num : 8
|______________________________________________________________________________

 ______________________________________________________________________________
| (873657:000007) Concatenated-Physical-Event :
| long: 22  desti: 0  source: 0  cryst: 1  cpl: 5  us: 0  term: 0  type a5
| tei: 0  >>>>  message received : INFORMATION [7b]  Call ref :  58 6b
|______________________________________________________________________________
|
| IE:[70] CALLED_NUMBER (l=2)  ->  81  Num : 0
|______________________________________________________________________________

 ______________________________________________________________________________
| (873659:000008) Concatenated-Physical-Event :
| long: 22  desti: 0  source: 0  cryst: 1  cpl: 5  us: 0  term: 0  type a5
| tei: 0  >>>>  message received : INFORMATION [7b]  Call ref :  58 6b
|______________________________________________________________________________
|
| IE:[70] CALLED_NUMBER (l=2)  ->  81  Num : 0
|______________________________________________________________________________

 ______________________________________________________________________________
| (873662:000009) Concatenated-Physical-Event :
| long: 22  desti: 0  source: 0  cryst: 1  cpl: 5  us: 0  term: 0  type a5
| tei: 0  >>>>  message received : INFORMATION [7b]  Call ref :  58 6b
|______________________________________________________________________________
|
| IE:[70] CALLED_NUMBER (l=2)  ->  81  Num : 0
|______________________________________________________________________________

 ______________________________________________________________________________
| (873663:000010) Concatenated-Physical-Event :
| long: 22  desti: 0  source: 0  cryst: 1  cpl: 5  us: 0  term: 0  type a5
| tei: 0  >>>>  message received : INFORMATION [7b]  Call ref :  58 6b
|______________________________________________________________________________
|
| IE:[70] CALLED_NUMBER (l=2)  ->  81  Num : 8
|______________________________________________________________________________

 ______________________________________________________________________________
| (873665:000011) Concatenated-Physical-Event :
| long: 22  desti: 0  source: 0  cryst: 1  cpl: 5  us: 0  term: 0  type a5
| tei: 0  >>>>  message received : INFORMATION [7b]  Call ref :  58 6b
|______________________________________________________________________________
|
| IE:[70] CALLED_NUMBER (l=2)  ->  81  Num : 0
|______________________________________________________________________________

 ______________________________________________________________________________
| (873765:000012) 1097: Send_IO1 (link-nbr=1, sapi=0, tei=0) :
| long: 22  desti: 0  source: 15  cryst: 1  cpl: 5  us: 8  term: 0  type a5
| tei: 0  <<<<  message sent : DISCONNECT [45]  Call ref :  d8 6b
|______________________________________________________________________________
|
| IE:[08] CAUSE (l=2) 81 90 -> [90] NORMAL CALL CLEARING
|______________________________________________________________________________

 ______________________________________________________________________________
| (873767:000013) Concatenated-Physical-Event :
| long: 22  desti: 0  source: 0  cryst: 1  cpl: 5  us: 0  term: 0  type a5
| tei: 0  >>>>  message received : RELEASE [4d]   Call ref :  58 6b
|______________________________________________________________________________
|
| IE:[08] CAUSE (l=2) 81 90 -> [90] NORMAL CALL CLEARING
|______________________________________________________________________________

 ______________________________________________________________________________
| (873767:000014) 1097: Send_IO1 (link-nbr=1, sapi=0, tei=0) :
| long: 22  desti: 0  source: 15  cryst: 1  cpl: 5  us: 8  term: 0  type a5
| tei: 0  <<<<  message sent : REL COMP [5a]  Call ref :  d8 6b
|______________________________________________________________________________
|
| IE:[08] CAUSE (l=2) 81 90 -> [90] NORMAL CALL CLEARING
|______________________________________________________________________________
See no error...
Billy

Re: Calling number modification?!

Post by Billy »

Fax, speech - it helped, vad you're genius!!!!
The only thing - the installation number is not PREpended, it REPLACES the calling number if I set the TG as Private. If the TG is Public, no number is changed...
Billy

Re: Calling number modification?!

Post by Billy »

UPDATE.
If I set the user's TG as Private, no calling number is seen, even in traces. What am I doing wrong?
vad
Alcatel Unleashed Certified Guru
Alcatel Unleashed Certified Guru
Posts: 3851
Joined: 23 Sep 2004 06:47

Re: Calling number modification?!

Post by vad »

If ISDN TG private and network mode=yes
Outgoing calling number for transit calls will be like for own user with number=calling number (recieved from incoming TG) and Entity=Entity in local parameters for incoming TG).
Or some problem with "Send caller ID" in incoming TG entity or incoming Calling number absent in DID rules (for outgoing TG) but default number not declared.
Billy

Re: Calling number modification?!

Post by Billy »

vad, thank you very much with bearing my prob!
The issue is that NO CALLING NUM is received from this TG if I declare it Private. If it's Public, I see it in t3 (three comments above). Entity is the same.
Did rules are empty - should I set up something in there? Default calling number is not declared either - I need to catch calling numbers from the caller.
Billy

Re: Calling number modification?!

Post by Billy »

Here is the trace when I set the TG as Private. As you can see, NO caller ID is received...

Code: Select all

 ______________________________________________________________________________
| (235212:000002) 1096: Send_IO1 (link-nbr=1, sapi=0, tei=0) :
| long: 42  desti: 0  source: 15  cryst: 1  cpl: 4  us: 8  term: 0  type a5
| tei: 0  <<<<  message sent : SETUP [05]    Call ref :  2e 66
|______________________________________________________________________________
|
| IE:[04] BEARER_CAPABILITY (l=3) 90 90 a3
| IE:[1e] PROGRESS_ID (l=2) 80 83
| IE:[6c] CALLING_NUMBER (l=2)  ->  41  81  Num :
| IE:[70] CALLED_NUMBER (l=8)  ->  81  Num : 3800080
| [a1] Sending complete
|______________________________________________________________________________

 ______________________________________________________________________________
| (235213:000003) Concatenated-Physical-Event :
| long: 23  desti: 0  source: 0  cryst: 1  cpl: 4  us: 0  term: 0  type a5
| tei: 0  >>>>  message received : CALL PROC (02)  Call ref :  ae 66
|______________________________________________________________________________
|
| IE:[18] CHANNEL (l=3)  a9 83 98 -> T2 : B channel 24 exclusive
|______________________________________________________________________________

 ______________________________________________________________________________
| (235215:000004) Concatenated-Physical-Event :
| long: 26  desti: 0  source: 0  cryst: 1  cpl: 4  us: 0  term: 0  type a5
| tei: 0  >>>>  message received : ALERT (01)  Call ref :  ae 66
|______________________________________________________________________________
|
| IE:[1e] PROGRESS_ID (l=2) 84 88
| IE:[1e] PROGRESS_ID (l=2) 81 88
|______________________________________________________________________________

 ______________________________________________________________________________
| (235216:000005) Concatenated-Physical-Event :
| long: 25  desti: 0  source: 0  cryst: 1  cpl: 4  us: 0  term: 0  type a5
| tei: 0  >>>>  message received : CONNECT (07)  Call ref :  ae 66
|______________________________________________________________________________
|
| IE:[29] DATE (l=5)  ->  date :  06 / 04 / 11   18:56
|______________________________________________________________________________

 ______________________________________________________________________________
| (235216:000006) 1096: Send_IO1 (link-nbr=1, sapi=0, tei=0) :
| long: 18  desti: 0  source: 15  cryst: 1  cpl: 4  us: 8  term: 0  type a5
| tei: 0  <<<<  message sent : CONNECT ACK (0f)  Call ref :  2e 66
|______________________________________________________________________________

 ______________________________________________________________________________
| (235278:000007) 1096: Send_IO1 (link-nbr=1, sapi=0, tei=0) :
| long: 26  desti: 0  source: 15  cryst: 1  cpl: 4  us: 8  term: 0  type a5
| tei: 0  <<<<  message sent : DISCONNECT [45]  Call ref :  2e 66
|______________________________________________________________________________
|
| IE:[08] CAUSE (l=2) 81 90 -> [90] NORMAL CALL CLEARING
| IE:[1e] PROGRESS_ID (l=2) 81 88
|______________________________________________________________________________

 ______________________________________________________________________________
| (235278:000008) Concatenated-Physical-Event :
| long: 18  desti: 0  source: 0  cryst: 1  cpl: 4  us: 0  term: 0  type a5
| tei: 0  >>>>  message received : RELEASE [4d]   Call ref :  ae 66
|______________________________________________________________________________

 ______________________________________________________________________________
| (235278:000009) 1096: Send_IO1 (link-nbr=1, sapi=0, tei=0) :
| long: 22  desti: 0  source: 15  cryst: 1  cpl: 4  us: 8  term: 0  type a5
| tei: 0  <<<<  message sent : REL COMP [5a]  Call ref :  2e 66
|______________________________________________________________________________
|
| IE:[08] CAUSE (l=2) 81 90 -> [90] NORMAL CALL CLEARING
|______________________________________________________________________________
vad
Alcatel Unleashed Certified Guru
Alcatel Unleashed Certified Guru
Posts: 3851
Joined: 23 Sep 2004 06:47

Re: Calling number modification?!

Post by vad »

If for incoming SETUP you have Calling number 3803664 and TG private.
For outgoing calls - you will send modified Calling number but -

F.e. NPD for Outgoing TG (or ARS route):
DID Id=0
Installation number source=Entity
Default number source = Entity

If in DID 0 rules number 3803664 absent (in internal number range)
If in incoming TG Entity (0 by default) not declared Installation and Suppl. installation number - you will send empty calling number (absent installation number and nothing from DID).

In another words - for this transit call (f.e. like described here example) - Calling number - the same like for internal user with Dir number 3803664 belong to the same entity that Incoming TG.
You can just create internal OXE user with Dir. number=Incoming calling number and entity like from incoming TG local parameters and check.
Billy

Re: Calling number modification?!

Post by Billy »

Thank you vad, trying to create a DID now. Shall I set DID transcoding for this group=yes? I don't need to transcode INCOMING caller ID's from PSTN to the client.

UPD. Not working.
For ARS route=0 - NPD ID=40. In this NPD, Calling DID identifier=0. In DID num translator Public=4953803664 Internal=3803664.
For ARS route 3 - NPD ID is 43, same DID, same result...
vad
Alcatel Unleashed Certified Guru
Alcatel Unleashed Certified Guru
Posts: 3851
Joined: 23 Sep 2004 06:47

Re: Calling number modification?!

Post by vad »

Used DID rules from outgoing TG.
F.e. for PTT connection you use DID rules 1234567 - 1000 - 1
Incoming call with called number 1234567 will be routed to user 1000.
When user 1000 make outgoing call - calling number = 1234567 (DID in reverse mode)

If you have transit from private TG and receive Calling number 1000 - you will send for outgoing call Calling number 1234567.
Post Reply

Return to “Translator”