OXE H323 O/G issue via ISDN

[sera544]

Hi All,

I have 2 OXE connected Via H323 IP, One OXE (R.10.0) connected to public calls ISDN other OXE users want to make calls they have to go thro this ISDN.

For testing i programmed Speed dial(28012801) in OXE call number(0+xxxxxxxx)where ISDN connected, when i acces from other OXE to this Speed dial number it send to local number. Strange issue is some numbers are working some not. Particular toll free numbers are not working.

Attached trace file t32.txt local number working.
t33.txt local number not working.

Tested with local digital phone call can go for toll free numbers with out any issues.

Any idea folks, thanks in advance.

Regards,
Pandian

[sera544]

Hi,

Any one can help me out on this issue..

[alex]

Why these two calls go out through different boards?

______________________________________________________________________________
| (229361:000122) 1078: Send_IO1 (link-nbr=4, sapi=0, tei=0) :
| long: 46 desti: 0 source: 15 cryst: 0 cpl: 4 us: 8 term: 0 type a5
| tei: 0 <<<< message sent : SETUP [05] Call ref : 00 1b
|______________________________________________________________________________
|
| IE:[04] BEARER_CAPABILITY (l=3) 80 90 a3
| IE:[6c] CALLING_NUMBER (l=10) -> 01 a1 Num : 25992423
| IE:[70] CALLED_NUMBER (l=9) -> 81 Num : 62408000
|______________________________________________________________________________

vs

______________________________________________________________________________
| (230124:000145) 1078: Send_IO1 (link-nbr=27, sapi=0, tei=0) :
| long: 46 desti: 0 source: 15 cryst: 0 cpl: 27 us: 8 term: 0 type a5
| tei: 0 <<<< message sent : SETUP [05] Call ref : 00 1b
|______________________________________________________________________________
|
| IE:[04] BEARER_CAPABILITY (l=3) 80 90 a3
| IE:[6c] CALLING_NUMBER (l=10) -> 01 a1 Num : 25992423
| IE:[70] CALLED_NUMBER (l=9) -> 81 Num : 64944164
|______________________________________________________________________________

[sera544]

Hi Alex,

Thanks for your reply, i have 4 ISDN in one trunk group total 120 channels. ofcourse i tried removing all other channels kept one by one cards still issue is same. I felt strange about this issue, never faced this kind of issue man both are same 6 series
number starting with but one is working another number not.

Regards,
Pandian.

[alex]

______________________________________________________________________________
| (230138:000154) Concatenated-Physical-Event :
| long: 22 desti: 0 source: 0 cryst: 0 cpl: 9 us: 0 term: 0 type a5
| tei: 0 >>>> message received : REL COMP [5a] Call ref : 00 25
|______________________________________________________________________________
|
| IE:[08] CAUSE (l=2) 81 90 -> [90] NORMAL CALL CLEARING
|______________________________________________________________________________

In your t33.txt file this RELEASE comes from H323 side although ISDN call seems to proceed OK (you see a couple of PROGRESS messages reveived).
So you'd better trace H.323 properly between the nodes.

[sera544]

Hi Alex,

Thanx for your reply, Am stuck in one place how come one number is working other number not, if H323 problem it should come on both numbers correct. what could be the possible reason for this, any idea.

[alex]

if H323 problem it should come on both numbers correct. what could be the possible reason for this, any idea.

Not exactly. From the traces it is clear that behaviour is different.
With VoIP it is not so easy - could be a codec problem etc.
Just run H.323 traces with wireshark for both users and compare the traces.

[sera544]

Hi Alex,

I did a mtracer for H323 i noticed this error below, any idea about this..

) Test_Compatibility_for_transit type1 0x63 type2 0x43 : incompatible

attached trace for your reference in case..

[alex]

Do you have H.323 between nodes or is it pure ABCF-IP?
With H.323 it is better to take tcpdump or wireshark trace.
There certain differences how succesfull and non-succesful calls are setup, that's clear. What is "type1 0x63 type2 0x43" I have no idea.

[sera544]

Hi Alex,

Issue is solved, problem in RBT for toll free numbers, so we have enabled No RBT for H323 calls = true then it started working. thanx for your support and reply man..

regards,
Pandian.