Posted: 23 Jul 2006 12:29
This is the error from my first post.
READ !
READ !
Alcatel Unleashed
The #1 Worldwide board for technical support on Alcatel-Lucent Voice & Data gear.
https://alcatelunleashed.com/
[VALIDATED] - eyeBeam
Page 2 of 3
Posted: 23 Jul 2006 16:09
Hey Frank, have you been able to perform transfer with eyeBeam? My button is greyed out.
Posted: 23 Jul 2006 22:55
Yes... But you have to make a call on the 2nd line.
Are you trying to transfer within the PBX or outside ?
Incoming or outgoing calls ?
Are you trying to transfer within the PBX or outside ?
Incoming or outgoing calls ?
Posted: 23 Jul 2006 23:02
Hello Frank,
"Dial ***7469, filter for "session", and set system:sdp:include_x_rtp_session_id to 0. "
Can you explain more detail what we need to do.
"Dial ***7469, filter for "session", and set system:sdp:include_x_rtp_session_id to 0. "
Can you explain more detail what we need to do.
Posted: 24 Jul 2006 00:05
Just dial ***7469 on the phone ...
You will have a setup menu showing up ...
In the filter, look for "session" (without the " " )
Then look for the line "system:sdp:include_x_rtp_session_id" and replace the 1 by 0.
If you can't find this option, then it's because it's not implemented in your x-lite release (it was not for me, I had to get eyeBeam) .
The programmers told me that they would add it in the next release for x-lite
You will have a setup menu showing up ...
In the filter, look for "session" (without the " " )
Then look for the line "system:sdp:include_x_rtp_session_id" and replace the 1 by 0.
If you can't find this option, then it's because it's not implemented in your x-lite release (it was not for me, I had to get eyeBeam) .
The programmers told me that they would add it in the next release for x-lite
Posted: 24 Jul 2006 02:58
I have message like "SIP/2.0 400 Bad Request
Warning: 399 192.168.127.11 "Malformed Media : a=x-rtp-session-id:7C11DE23ACBB46
A8A1C51A0DC8C27AEE"
But I use X-lite ver. 3.0 build 29712 where "system:sdp:include_x_rtp_session_id" absent
Warning: 399 192.168.127.11 "Malformed Media : a=x-rtp-session-id:7C11DE23ACBB46
A8A1C51A0DC8C27AEE"
But I use X-lite ver. 3.0 build 29712 where "system:sdp:include_x_rtp_session_id" absent
Posted: 24 Jul 2006 21:41
Yes, this is the error I had also, and I sent an email to the technical support with the error, and they sent me a temporary link to eyeBeam trial version.. Maybe if you send them an email, they can finally try to fix this issue 
Posted: 26 Jul 2006 02:41
CounterPath support solve my problem. Us I uderstend them, this correction (exist in eyeBeam) will be present in next version of X-Lite soon.
Posted: 28 Jul 2006 05:22
Some results of my investigations.
I have two versions of X-Lite 2.0 and 3.0 on different computers.
With OXE SW R6.2-f3.301-10 two clients work fine - both with digest authorisation and without authorisation. I upgraded OXE to SW 7.1 (f4.401.13) and checked (so both clients do not know with which SW version of switch they work
So both do not work! But with different behaviour.
X-Lite 2.0 logged OK. But when dialling any number (internal or external)- message "Temporarily not available" is displayed.
X-Lite 3.0 logged OK. But when dialling a number - message "Bad request"
Logs are available for these calls.
X-Lite 2.0 - release 1105
X-Lite 3.0 - release 1002tx stamp 29712 (CounterPath eyeBeam)
I have two versions of X-Lite 2.0 and 3.0 on different computers.
With OXE SW R6.2-f3.301-10 two clients work fine - both with digest authorisation and without authorisation. I upgraded OXE to SW 7.1 (f4.401.13) and checked (so both clients do not know with which SW version of switch they work
So both do not work! But with different behaviour.
X-Lite 2.0 logged OK. But when dialling any number (internal or external)- message "Temporarily not available" is displayed.
X-Lite 3.0 logged OK. But when dialling a number - message "Bad request"
Logs are available for these calls.
X-Lite 2.0 - release 1105
X-Lite 3.0 - release 1002tx stamp 29712 (CounterPath eyeBeam)
Posted: 28 Jul 2006 06:25
I have the problem also, but....
The other way around!
On release 7 (F440116) the phone works fine, but on a relase 6.2 (F330122) I receive a 'bad request' message if I dial from X-Lite to OXE, and if I call from OXE to X-Lite I can answer the call, but the OXE set keeps calling.
I have already changed the suggested parameter, but this will not help.
I hope to find a difference in both systems that can explain the problems.
The other way around!
On release 7 (F440116) the phone works fine, but on a relase 6.2 (F330122) I receive a 'bad request' message if I dial from X-Lite to OXE, and if I call from OXE to X-Lite I can answer the call, but the OXE set keeps calling.
I have already changed the suggested parameter, but this will not help.
I hope to find a difference in both systems that can explain the problems.