Forward Problem in T2 Link

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

Forward Problem in T2 Link

Post by jcalvillo »

Hi everybody i have a question about using NPRAE Link with a cisco callmanager, this is a link that works in both sides but when i make a forward in an alcatel station to other alcatel station and someone call the extension forwarded the call doesnt complete and finally releases, I put a trace to identify the issue but the only thing that i found is that the cisco calling number have 5 more digits inserted than the extension who initializated the call and i think it could be the cause of failure, but im not sure because the call can be completed if the set is not forwarded, someone have any idea?
Alcatel Rel 6.1.1 (f2.502.33.a)


this is the real case: Ext 4099 in cisco calls to Ext 8323 in alcatel that is forwarded to station 8335 and the trace show this:

Traces Analyser activated

mtracer started ...
______________________________________________________________________________
| (169505:007591) Physical-Event :
| long: 48 desti: 0 source: 0 cryst: 3 cpl: 3 us: 0 term: 0 type a5
| tei: 0 >>>> message received : SETUP [05] Call ref : 1a 09
|______________________________________________________________________________
|
| IE:[04] BEARER_CAPABILITY (l=3) 80 90 a3
| IE:[18] CHANNEL (l=3) a9 83 81 -> T2 : B channel 1 exclusive
| IE:[6c] CALLING_NUMBER (l=11) -> 00 81 Num : 854754099
| IE:[70] CALLED_NUMBER (l=5) -> 80 Num : 8323
|______________________________________________________________________________

______________________________________________________________________________
| (169505:007594) 1027: Send_IO1 (link-nbr=9, sapi=0, tei=0) :
| long: 23 desti: 0 source: 15 cryst: 3 cpl: 3 us: 8 term: 0 type a5
| tei: 0 <<<< message sent : CALL PROC (02) Call ref : 9a 09
|______________________________________________________________________________
|
| IE:[18] CHANNEL (l=3) a9 83 81 -> T2 : B channel 1 exclusive
|______________________________________________________________________________

______________________________________________________________________________
| (169505:007595) 1027: Send_IO1 (link-nbr=9, sapi=0, tei=0) :
| long: 113 desti: 0 source: 15 cryst: 3 cpl: 3 us: 8 term: 0 type a5
| tei: 0 <<<< message sent : FACILITY [62] Call ref : 9a 09
|______________________________________________________________________________
|
| IE:[1c] FACILITY (l=93)
| [9f] Discriminator of supplementary service applications
| [aa] NFE (l=6):
| [80] Source Entity (l=1) End_PTNX
| [82] Destination Entity (l=1) End_PTNX
| [a1] INVOKE (l=82):
| Invoke Ident. : 2ef3 (12019)
| OP: 0013 (19)
| [30] Sequence (l=73)
| [0a] Enumerated (l=1) 01
| [30] Sequence (l=6)
| [80] Context specific (l=4) 38 33 33 35
| [02] Integer (l=1) 01
| [40] Application (l=5) 04 03 80 90 a3
| [a1] Context specific (l=8)
| [a0] Context specific (l=6)
| [80] Context specific (l=4) 38 33 32 33
| [82] Context specific (l=1) 02
| [a4] Context specific (l=16)
| [a0] Context specific (l=14)
| [80] Context specific (l=9) 38 35 34 37 35 34 30 39 39
| [0a] Enumerated (l=1) 00
| [a5] Context specific (l=2)
| [84] Context specific (l=0)
| [a7] Context specific (l=15)
| [80] Context specific (l=13) 43 79 6e 74 68 69 61 20 54
| 72 65 74 6f
|______________________________________________________________________________

______________________________________________________________________________
| (169704:007602) 1029: Send_IO1 (link-nbr=9, sapi=0, tei=0) :
| long: 23 desti: 0 source: 15 cryst: 3 cpl: 3 us: 8 term: 0 type a5
| tei: 0 <<<< message sent : DISCONNECT [45] Call ref : 9a 09
|______________________________________________________________________________
|
| IE:[08] CAUSE (l=3) 80 90 80 -> [90] NORMAL CALL CLEARING
|______________________________________________________________________________

______________________________________________________________________________
| (169704:007605) Physical-Event :
| long: 18 desti: 0 source: 0 cryst: 3 cpl: 3 us: 0 term: 0 type a5
| tei: 0 >>>> message received : RELEASE [4d] Call ref : 1a 09
|______________________________________________________________________________

______________________________________________________________________________
| (169704:007606) 1029: Send_IO1 (link-nbr=9, sapi=0, tei=0) :
| long: 23 desti: 0 source: 15 cryst: 3 cpl: 3 us: 8 term: 0 type a5
| tei: 0 <<<< message sent : REL COMP [5a] Call ref : 9a 09
|______________________________________________________________________________
|
| IE:[08] CAUSE (l=3) 80 90 80 -> [90] NORMAL CALL CLEARING
|______________________________________________________________________________
root

Re: Forward Problem in T2 Link

Post by root »

from the trace it seems to be that you use QSIG and the CCM can not handle the diversion facility send
by OXE, you told him the set is forwarded unconditional to ext. 8335, what have the CCM to dial into
the OXE? Maybe you must add a prefix in the NPD for this network.

Or you switch from QSIG to ISDN than the OXE handle the forward localy or you upgrade the OXE
then you could disable the diversion facility.
jcalvillo

Re: Forward Problem in T2 Link

Post by jcalvillo »

Ok Thank you root i will try to contact CCM manager to check this
externalgateway_DUP

Re: Forward Problem in T2 Link

Post by externalgateway_DUP »

Hi,

It seems that you have qsig connection via PRA to Cisco. Could you please post yout OXE configuration here, because I have the problem, that Cisco in unable to disconnect its extension. Did you have any problem like this? I am also using R6.1.1.

Regards,

Miha
Post Reply

Return to “ON SITE TROUBLES”