CME 4.2 call park issue

Unanswered Question
Dec 21st, 2007
User Badges:

When a user puts a call on park, goes to another phone, picks the park up via speaker phone, we get one way communication. The Person that is parked can hear the person, but the person who picked up the park cannot hear the person who was parked. Any ideas?


Thanks,

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
paolo bevilacqua Fri, 12/21/2007 - 11:41
User Badges:
  • Super Gold, 25000 points or more
  • Hall of Fame,

    Founding Member

Hi,


Which exact router and IOS image are you using ?

atomike10 Fri, 12/21/2007 - 11:43
User Badges:

DN Configs:


ephone-dn 52

number 30700

park-slot timeout 90 limit 15

description 30700 park DN

!

!

ephone-dn 53

number 30701

park-slot timeout 90 limit 15

description 30701 park DN

!

!

ephone-dn 54

number 30702

park-slot timeout 90 limit 15

description 30702 park DN

!

!

ephone-dn 55

number 30703

park-slot timeout 90 limit 15

description 30703 park DN

!

!

ephone-dn 56

number 30704

park-slot timeout 90 limit 15

description 30704 park DN

paolo bevilacqua Fri, 12/21/2007 - 11:43
User Badges:
  • Super Gold, 25000 points or more
  • Hall of Fame,

    Founding Member

Hi, can you upgrade to 12.4(11)XW5 and try again ? Also need to check phone model and firmware used.



paolo bevilacqua Fri, 12/21/2007 - 12:05
User Badges:
  • Super Gold, 25000 points or more
  • Hall of Fame,

    Founding Member

Hi, the XW buglist is of such an impressive size (check release notes) that unless you are running latest IOS and phone FW, you cannot receive TAC assistance if needed.


As workaround, have you tried answering with the headphone button and then press speakerphone (I assume pulling handset is not an option).

atomike10 Fri, 12/21/2007 - 12:06
User Badges:

I have asked my customer to try with the handset, have not received a reply yet.

atomike10 Fri, 12/21/2007 - 12:03
User Badges:

telephony-service

load 7914 S00104000100

load 7941 SCCP41.8-2-2SR2S

load 7961 SCCP41.8-2-2SR2S

load 7936 cmterm_7936.3-3-13-0

load 7911 SCCP11.8-2-2SR2S


41's, 61's were used for the test.

paolo bevilacqua Fri, 12/21/2007 - 12:19
User Badges:
  • Super Gold, 25000 points or more
  • Hall of Fame,

    Founding Member

Hi, unrelated to the issue, cisco recommends S00105000200 for the 7914.

atomike10 Fri, 12/21/2007 - 12:23
User Badges:

Will I stay with those phone loads with the new code? I cannot find any newer FW than that.


Thanks,

atomike10 Thu, 12/27/2007 - 11:52
User Badges:

I upgraded to the 12.4(11)XW5 and this is still an issue. It works when you pick the handset up, just not with the speaker phone.

paolo bevilacqua Thu, 12/27/2007 - 11:59
User Badges:
  • Super Gold, 25000 points or more
  • Hall of Fame,

    Founding Member

At this point your only choice is to work with the TAC to have this worked as a bug.


Be prepared to provide abundant "proof" of the problem, persistent to insist that a new bug is filed (ie that is NOT working as designed, nor documented anywhere that speakerphone cannot be used), and patient enough waiting a fix to be made available to you. Unfortunately the full process can take months.



atomike10 Thu, 12/27/2007 - 12:00
User Badges:

I upgraded to the 12.4(11)XW5 and this is still an issue. It works when you pick the handset up, just not with the speaker phone.

mgischernsnw Thu, 12/27/2007 - 19:57
User Badges:

That is a bug in the phone firmware, see bug ID CSCsk10873. Try upgrading to 8.3.2 or a later load and you should be alright. You might find all kinds of other bugs, but this one should be fixed at least :)

paolo bevilacqua Fri, 12/28/2007 - 01:32
User Badges:
  • Super Gold, 25000 points or more
  • Hall of Fame,

    Founding Member

Hi,


certainly is worth to give new FW a try, however from the bug description "happens randomly" it is not a 100% match for the problem exposed (cannot hear only when picking up from parked call).

mgischernsnw Fri, 12/28/2007 - 09:10
User Badges:

I experienced the same "feature" that the poster described, TAC pointed me to that case, and after 2 months, the problem hasn't recurred with the new firmware.

atomike10 Fri, 12/28/2007 - 09:12
User Badges:

Thanks for the responses, that is definately something I am going to try. So far 8.3.2 seems to be working relatively bug free for everyone?


Thanks,

Actions

This Discussion