Alcatel Unleashed

hi
Im using OXE R9.1 with a SIP trunk configured to an Avaya PBX.

Avaya pbx = Sub A, Sub B
Alcatel OXE = Sub C
Im doing the following call:

Sub A rings Sub C
Sub C does Un-attended transfer to Sub B

Sub B answers and has voice in both directions to Sub A but after 20 seconds, OXE sends a BYE message to Sub A and the call is cleared down.

The Avaya pbx phones are shuffling the calls off their PBX but if i disable shuffling on Avaya PBX, then the BYE message from OXE is never sent.

Is there a timer on the OXE that controls SIP inactivity or the something similar ? i have looked at timers in the SIP Gateway and SIP EXT Gateway config but cant see anything

tommyphelan wrote:The Avaya pbx phones are shuffling the calls off their PBX but if i disable shuffling on Avaya PBX, then the BYE message from OXE is never sent.

What does that mean "shuffling"?

tommyphelan wrote:Is there a timer on the OXE that controls SIP inactivity or the something similar ? i have looked at timers in the SIP Gateway and SIP EXT Gateway config but cant see anything

Before you start tweaking something in OXE -why do you think it is going to help you in this case?
BYE is used to terminate an already established session. Why OXE decides to terminate it? - That's the question.

Shuffling is the term used to denote an if an rtp stream is using resources on the Avaya media processor board (similar in functionality to the GD board of the OXE) or not.

non-shuffled call : IP phone --> media processor/GD board --> ip phone

shuffled : IP phone --> IP phone


The OXE is trying to terminate a session it has already transferred which is strange to me. I would like to find out the timer
responsible for forcing a BYE message to be sent to understand what the function of this timer is.

tommyphelan wrote: shuffled : IP phone --> IP phone

That's good.

tommyphelan wrote:The OXE is trying to terminate a session it has already transferred which is strange to me. I would like to find out the timer responsible for forcing a BYE message to be sent to understand what the function of this timer is.

Traces?
I meant that if OXE needs to terminate the session then no timer would help.

I agree with you on the timer , just for my own knowledge to know which timer is responsible and how to find it in the OXE mgr.

Ive attached a wireshark trace, please use the following filter :

sip and ip.addr==10.10.9.34

network is ... avaya pbx <--> sip proxy server <--> alcatel OXE

some ip addresses :

10.10.9.34 = sip proxy server

Alcatel:
10.10.9.111 (OXE-CS) , 10.10.9.112 (OXE-GD)
Sub C = 36002 (10.10.99.201)

Avaya:
10.10.9.45 = Avaya pbx (GD board equivalent)
Sub A = 41000 (10.10.99.10)
Sub B = 42000 (10.10.99.22)

Checked traces. A hell lot of RE-INVITES, some from Avaya even with "P-Charging-Vector". Found just two independant calls: 41000->36002 and 36002->42000.
Have not found any REFER method sent - that means OXE did not try to make a transfer. Yes, OXE can make a transfer without REFER method but that depends on your SIP TG configuration - is it ABC-F or ISDN?
Can you make an attended transfer, i.e when 42000 answers to call from 36002?

the trunk is ABC-F and i can make an attended transfer successfully.

tommyphelan wrote: i can make an attended transfer successfully.

Great. That means it is not a problem of categories incompatability.
Now i would like to know whether SIP TG - SIP TG unattended transfer is supported by OXE It is supported by SIP extensions, I know.
Help from the audience?

Its supported allright - if i do an unattended transfer to another Alcatel phone it works.


Avaya pbx = Sub A, Sub B
Alcatel OXE = Sub C, Sub D

the following call works :

Sub A rings Sub C
Sub C does Un-attended transfer to Sub D

tommyphelan wrote:Sub A rings Sub C
Sub C does Un-attended transfer to Sub D

Just for fun - check traces with "motortrace 2; traced" and you will notice REFER method used for call transfer in this case.