Page 1 of 1

Network between OXE R9.1 and Aastra Businessphone

Posted: 06 Jul 2010 07:55
by OXO-Man
Dear specialists,
one of our costumer wants to connect an OXE R9.1 and a Aastra Businessphone via H323-Trunk.
The Businessphone can call into the OXE without an problem. If I call from OXE to the Businessphone the call can´t established. The 4039 shows "busy" on the display.

In the H323-Trace I can see that the call is rejected from the buisnessphone (call from 2000 (OXE) to 301 (businessphone) via H323-Trunk and speeddial):
_________________________________________________________
| (778016:000036) 1044: Send_IO1 (link-nbr=1, sapi=0, tei=
| long: 107 desti: 0 source: 15 cryst: 1 cpl: 0 us: 8
| tei: 0 <<<< message sent : SETUP [05] Call ref : 0
|_________________________________________________________
|
| [9f] Non-locking shift. codeset : 7
| [a2] EI_IP_TYPE_TERM
| [9f] Non-locking shift. codeset : 7
| IE:[05] EI_IP_INFOS (l=9) -> G723 Ece 1 Vad 0 Profil 2,
| [9f] Non-locking shift. codeset : 7
| IE:[07] EI_IP_QOS (l=3) b8 a0 00
| [9f] Non-locking shift. codeset : 7
| IE:[0a] EI_RTP_INFO (l=30)
| -> stop_packet=0 stop_rtp=0 h323=0 wc=0 rf=0 udp=1 rq
| -> Transm_Bande=1 detection_Q23=1 dtmf_payload=96
| -> Port RTP = 32514, IPv4 : 192. 168. 92.
| -> Port RTCP SR = 32515, IPv4 : 192. 168. 92.
| -> Port RTCP RR = 32515, IPv4 : 192. 168. 92.
| -> Port Fax = 0, IPv4 : 0. 0. 0. 0.
| IE:[04] BEARER_CAPABILITY (l=3) 80 90 a3
| IE:[18] CHANNEL (l=3) a8 83 81 -> T2 : No B channel
| IE:[6c] CALLING_NUMBER (l=13) -> 21 81 Num : 2000
| IE:[70] CALLED_NUMBER (l=4) -> 81 Num : 301
| IE:[7d] HLC (l=2) 91 81
| [a1] Sending complete
|_________________________________________________________

_________________________________________________________
| (778017:000038) Concatenated-Physical-Event :
| long: 21 desti: 0 source: 0 cryst: 1 cpl: 0 us: 0
| tei: 0 >>>> message received : CALL PROC (02) Call re
|_________________________________________________________
|
| IE:[18] CHANNEL (l=1) a8 -> T2 : No B channel
|_________________________________________________________

_________________________________________________________
| (778018:000039) Concatenated-Physical-Event :
| long: 22 desti: 0 source: 0 cryst: 1 cpl: 0 us: 0
| tei: 0 >>>> message received : REL COMP [5a] Call ref
|_________________________________________________________
|
| IE:[08] CAUSE (l=2) 81 95 -> [95] CALL REJECTED
|_________________________________________________________

The admin of the businessphone said that the OXE sends the flag "tunneling:on" so that the businessphone rejects the call.

Can I turn off the "tunneling" on the OXE?

Thank you for your answers!!!!
Best regards
OXO-Man

Posted: 07 Jul 2010 02:16
by alex
Hi
Probably they are talking about H.245 tunneling in H.225 connection.
Try to enable "Fast start" in IP/IP parameters.

PS. t3 trace is not enough for H.323 troubleshooting. You should take sniffer traces on GD/INT-IP.

Posted: 14 Jul 2010 02:55
by OXO-Man
Hi Alex,

I´ve just pointed out that the OXE sends an H323-ID to the BP. The ID is the same as the extension number in the OXE. This ID is used in the BP as an password to autorise this incoming call.

The question is:
Is there a feature or flag in the OXE in which I can turn off this H323-ID?

Thank you!

Posted: 14 Jul 2010 04:33
by alex
OXO-Man wrote: I´ve just pointed out that the OXE sends an H323-ID to the BP. The ID is the same as the extension number in the OXE. This ID is used in the BP as an password to autorise this incoming call.
The question is:
Is there a feature or flag in the OXE in which I can turn off this H323-ID?
Hmm. I did not get it.
You mean that BP acts as an external gatekeeper for OXE?