04-24-2005 02:56 AM - edited 03-13-2019 08:51 AM
Today , my users complain that when they use the meet-me feature the second caller got a buzy signal
i checked the service parameters ,..every thing is okay
does any one see that problem before
thkx
Solved! Go to Solution.
04-24-2005 02:33 PM
If you are running 3.3.4sr2, have meetme numbers in a partition and are not using a range of numbers, then you maybe hitting this bug. CSCef89600: UPgrade to 3.3(4)SR2 causes meetme conference to fail. It is a dup of another bug, but you would never associate the two. This is fixed in CCM 3.3.5. Or, you could move the MeetMe Numbers to the none partition, or you could make it a range.
04-24-2005 08:33 AM
The meet-me conference needs to be opened up (established) from a IP Phone by pressing the meet me softkey. Once the meet me is open, people can call the meet me # directly and join the conference. The users/devices would need a CSS that allows them to call the partition the meet me number is in.
Are the users calling from other IP phones, or are they calling from outside (a DID, or being transferred)?
Slow busy or fast busy? reorder?
04-24-2005 02:33 PM
If you are running 3.3.4sr2, have meetme numbers in a partition and are not using a range of numbers, then you maybe hitting this bug. CSCef89600: UPgrade to 3.3(4)SR2 causes meetme conference to fail. It is a dup of another bug, but you would never associate the two. This is fixed in CCM 3.3.5. Or, you could move the MeetMe Numbers to the none partition, or you could make it a range.
04-25-2005 11:46 PM
Thats what i tried exactly , putting the number in range and it works ... I thought Cisco put it it so :)
Really my version is 3.3.4 with Es17 . but it seems that the bug applied too .
Thanks Steven , I will rate your post
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide