Alcatel Unleashed

Our customer has the OXE system in Slovenia and lots of OXO systems all over Europe. OXE and OXO systems are connected via IP H323 link. On OXE system theIP trunk is confugured and also all the routes (in abbreviated numbers) to all the OXO systems (to all internal numbers on OXOs).

The problem is, that all the OXOs except one are working correct. The problem is, that when calling to that OXO from OXE, we do not get the ringback tone. When the called pick up the phone, the conversation is OK. So the problem is only ringbacktone when calling from OXO to OXE!

The configuration (the routing in abbreviated numbers) on OXE is the same for all the OXOs.

My question is, who generates the ringback tone? I am guessing, it is like this: When calling from Oxe to OXO, OXO sends the information packet to OXE to generate the ringback tone and OXE should handle this. So the prroblem could be, that OXE does not get the information packet or OXE even gets something but does not know how to interprete it.


Does anybody have any solution or suggestion what could be wrong here?

Best regards,

Miha

Hi,

There is one more important info.

If the call transfer is made on OXO to external line (like on mobile phone), the callback tone is OK!

Hopefully someone has any suggestion.

Best regards,
Miha

No callback tone but ringback tone .... sorry...

Release in OXE?
Direct RTP used or not?

Can you show t3 trace - call to OXO where no problem and call to OXO where problem? May be you have problem with some messages - Call proc or f.e. Alert signal absent?

Hi,

Oxe software release is 6.1.1

Attached here are traces where call is OK as well as when call NOK.

Best regards,

Miha

i've seen same problems: OXE R6.x plus a bunch of OXO connected with sip.
Solution recommended by eSR was: upgrade OXE to R8!
Well, at least it worked (not that is was cheap).
try to use same config in LAB and test it with R8.

externalgateway wrote: Oxe software release is 6.1.1

You'd better supply full SW version string, with static and dynamic patch.
There were some bugs fixed in 6.1.1 with wrong PROGRESS message handling by OXE.

Hello, I have just posted a similar question; but I am trying it over SIP on Oxe R6.1.1.

In my lab it worked perfectly, even the Oxe release were older than the machine of the client. (6.1.0). But now, the oxe users dont hear the ringback tone.

Tomorrow I will review all traces to see any diference between both systems. I´m not sure but I think the Oxe isn´t receiving the ACK about communication establishment necesary to generate the ringback tone.

Bye,

From readme (f2.502.19) - VoIP H323 Progress Id in Alert message not taken in account.
I think will be enough to install last approved patch from 6.1