CallListen: Dead air. What am I missing? 1

[jonnyGURU]

I'm pretty sure I have it set up right, but when I listen, I get dead air.

There's a CSR group.

Let's say the person that is listening is x210.

In Telephony, I have the Monitor Group set to "CSR"

I created a shortcode: *90*N#.

x220 is a member of CSR. She gets a call and I dial "*90*220#" from x210.

I'm getting dead air. Not an error message like, "Unobtainable" or "Restricted," but dead air.

I'm using a 403 with 2.1(17) installed.

Is there a check box I'm missing somewhere?

Dispensing quality rants and mishaps since 1999:

http://www.jonnyguru.com

 

[juandebobo]

There is a box in the User form and system for under the Telephony tab.

John

 

[jonnyGURU]

Thanks John.

Under user: telephony, I think you mean the Monitor Group box where you put in the group you're monitoring the members of. As I said, I've got that set to the "CSR" group. I don't see anything else pertaining to the listening. I even unchecked the "Cannot Be Intruded."

Now in System, under Telephony, I don't see anything that pertains to CallListen. There's "beep on listen" under the System tab, but I don't see anything else.

Am I blind? What am I missing?

Dispensing quality rants and mishaps since 1999:

http://www.jonnyguru.com

 

[jonnyGURU]

Hmm.... I'm wondering if my module is buggy or my config is corrupt. Check this.... I set another user to Monitor Group "CSR" because it was a phone closer to the phone system that I could use for testing. On this phone, when I do the CallListen shortcode, the CSR hears the beep, I hear about a split second of the CSR's voice and then... get this... I GET A DIAL TONE!!!

I have NEVER seen anything like that.

Dispensing quality rants and mishaps since 1999:

http://www.jonnyguru.com

 

[VOiDDude]

Try a double # at the end of your shortcode. This is a known bug under 2.1(27).

 

[big70]

What phone,s do you use 64xx.
It won,t work in 2.1 (27)
I Tried ## at the end and it wont,t work.

Greets peter

 

[jslewis]

Hitting # # after the extension works with a 406 using 2.1.27, but not with a 403. You need version 2.1.276905, it is just the ip403.bin file

 

[jonnyGURU]

I'm dialing the shortcode. I don't have a button programmed because the user wants to be able to punch in the extension of whomever he wants to monitor in that group.

Also, I can't do two #'s if I dial it because the listening kicks in immediately after the first pound is dialed. IOW: There's no "time" to get in a second pound sign before the shortcode kicks in.

Dispensing quality rants and mishaps since 1999:

http://www.jonnyguru.com

 

[jonnyGURU]

And it is 2.1(27) BTW.

Dispensing quality rants and mishaps since 1999:

http://www.jonnyguru.com

 

[jonnyGURU]

big70: 4412D+

jslewis: We must have both posted at the same time. I just now saw yor post.

It IS a 403. You've tried that version? So they figured out the bug? I told the customer that an update would fix the issue. Glad to see I wasn't lying. ;-)

Dispensing quality rants and mishaps since 1999:

http://www.jonnyguru.com

 

[Morrack]

Folks be carefull with this bug. ## can reboot a 412 (!!)

Peter

 

[jslewis]

Yes I am using version 2.1.276905 on 2 sites with 403s, and it fixed the call listen problem at both sites. And I think it might have helped with some random auto recording problems I was having at one site also.

 

[jasonmorrison]

This is a bug with 2.1(27)
On a 403 ... it won't work !!!!
On a 406 & 412 ... enter the entire short code twice and it works.
Example: if the shortcode is : *9*N# and extension to monitor is 208 ...
Dial *9*208#*9*208#
it will work !!!!!
Temporary fix until AVAYA Fixes

 

[jonnyGURU]

Bump!

I've gone 10 rounds with Avaya and this is what I get....

Can't get 2.1(276905) as it's been superceeded by 2.1(30).

Can't get 2.1(30) because it has too many bugs.



Dispensing quality rants and mishaps since 1999:

http://www.jonnyguru.com

 

[jonnyGURU]

Hmm... I apparently posted a no no by asking someone to please send the bin files to me via electronic mail. I can understand how this would attract spam, so my apologies to the site admin.

Perhaps this will float....

Click on my URL and see what domain that resolves to (that URL is just a forward.) Can someone please send the bin to my name at that domain?

I know it's asking a lot, but Call Listen is a big deal and Avaya is being as useless as tits on a fish.

I mean, they should leave something up on the FTP, but they took down 2.1(30) in favor of a 2.1(31) that's not even complete! Come on Avaya! Gimme a break!

Dispensing quality rants and mishaps since 1999:

http://www.jonnyguru.com

 

[sizbut]

?Still haven't said what phones you are using. Monitoring IP devices that are on 'direct media path' doesn't always work.

 

[jonnyGURU]

I did say what phone I am using. I'm using the 4412D+.

Everyone is saying this is a known issue with the 403 and 2.1(27,) so now all I'm looking for is the new bin file and Avaya doesn't have it.

Thanks for your help.




Dispensing quality rants and mishaps since 1999:

http://www.jonnyguru.com

 

[sizbut]

whoops, your right, new glasses methinks.

 

[kristiandg]

I've got the patched version of 2.1.27 that fixes this if someone needs it "kguntzelman at rlcarriers dot com

 

[jslewis]

you can download the 403 patch here.

http://www dot

whothunkit dot com