CLIP ISDN "+"

[TMC]

The station OXE is connected GSM BRI ISDN gateway. Tracing a call -
mtracer started ...
(994337:000001) MTRACER host (192.168.1.51, alcatel), version: R7.1-f5.401-36-b-ru-c80s1
(994337:000001) MTRACER num: 035, time: 2011/07/27 12:26:59, loss: 0%
______________________________________________________________________________
| (994457:000002) Physical-Event :
| long: 48 desti: 0 source: 0 cryst: 1 cpl: 10 us: 0 term: 0 type a5
| tei: 0 >>>> message received : SETUP [05] Call ref : 40
|______________________________________________________________________________
|
| IE:[04] BEARER_CAPABILITY (l=3) 80 90 a3
| IE:[18] CHANNEL (l=1) 89 -> T0/S0 : B1 channel exclusive
| IE:[6c] CALLING_NUMBER (l=13) -> 80 Num : +79262125000
| IE:[70] CALLED_NUMBER (l=5) -> 80 Num : 2997
| [a1] Sending complete
|______________________________________________________________________________

______________________________________________________________________________
| (994458:000003) 1119: Send_IO1 (link-nbr=1, sapi=0, tei=0) :
| long: 25 desti: 0 source: 15 cryst: 1 cpl: 10 us: 8 term: 0 type a5
| tei: 0 <<<< message sent : STATUS [7d] Call ref : c0
|______________________________________________________________________________
|
| IE:[08] CAUSE (l=3) 81 e4 6c -> [e4] INVALID INFORMATION ELEMENT CONTENTS
| IE:[14] CALL_STATE (l=1) 06
|______________________________________________________________________________

The stations do not like CLIP "+..." and accordingly the number on the display is not visible.
In the problem was solved by changing OXO label IsdnTransp.
What should be done in OXE?

[tot3nkopf]

Did you tried to remove first digit in callback translation? (DEF number of digits to be removed-->1)

[TMC]

No fails. The process does not reach Ext. Callback Translation.

[tot3nkopf]

Remove + in your GSM gateway configuration. It may be the simplest way.
I didn't faced such configuration so I don't know if this is possible on ISDN on OXE. Usually + is in SIP canonical config.

[TMC]

Gateway TelecomFM is limited to the configuration.
A similar problem was solved in OmniPCX Office.