[cisco-voip] VG224 Issue / propable misunderstanding

[Kevin Thorngren]

Hi Bernhard,

I doubt it is cabling too.  For the polycom I would expect the user of 
that phone to hang up at the end of the call.  For the other devices 
that aren't human controlled they are probably expecting some sort of 
disconnect procedure so they know to go on hook.

I just tried it with a SCCP VG224 connected to CME and I hear reorder 
for awhile then dead air.  No annunciator in this case, obviously :-)

Kevin

On May 4, 2006, at 5:00 PM, Bernhard Albler wrote:

> Hi Kevin,
> thank you for your help.
> well, the truth is that I am not sure what the devices expect for 
> disconnect supervision. One of the devices is a polycom conference 
> station, maybe someone has experience with that one?
> The other devices are a door openers and analog dect phones.
> What is strange to me is, that no reorder or busy tone is played after 
> the disconnect (and you can see the onhook with debug vpm signal). 
> It's just dead air until the annunciator kicks in.
> I tried both power denial as well as polarity reversal, still no luck.
> Could this be a cableing issue (i would believe not, since everything 
> else, e.g. calling and audio path is ok)?
>  
> many thanks again
> bernhard
>
> Von: Kevin Thorngren [mailto:kthorngr at cisco.com]
> Gesendet: Do 04.05.2006 21:40
> An: Bernhard Albler
> Cc: cisco-voip at puck.nether.net
> Betreff: Re: [cisco-voip] VG224 Issue / propable misunderstanding
>
> Hi Bernhard,
>
> The behavior you describe is pretty much what I would expect. The busy 
> tone you hear should be fast busy (reorder) and not slow busy (user 
> busy).
>
> The CCM is signaling the voice port to go on hook when the call is 
> disconnected. The FXS device is expected to hang up. If it does not 
> then one of the GW timers will expire and reoder tone will be played. 
> Since the voice port is still off hook another timer will then expire 
> and the GW will take the voice port off hook. You are probably hearing 
> the annunciator because CCM is waiting for digits and does not receive 
> any.
>
> What does your device expect for disconnect supervision?
>
> Kevin
> On May 4, 2006, at 1:39 PM, Bernhard Albler wrote:
>
>> Hi everyone,
>> maybe someone can shed some light on this, because I'm banging my 
>> head against the wall.
>> It's probably a misunderstanding of how analog sccp ports work on my 
>> side, but maybe someone still can help:
>> I have a vg224 which has connected diverse analog devices connected 
>> to it.
>> When someone places a call from one of the analog devices to a ip 
>> phone, and the ip phone hangs up, the analog devices doesn't get 
>> anything (now busy tone played) on the sccp version. After some time, 
>> the vg goes offhook again (according to tac this is normal behavior 
>> because of a timer) and so we have dead air until the annunicator 
>> kicks in.
>> Now:
>> what would be the "correct" behavior for a analog devices here. On a 
>> FXS port, is there even some way to indicate the device, that the 
>> remote site has hung up? Is there some way to get the vg to play busy 
>> tone after the other side went onhook?
>> If someone from cisco wants to look into the case i have open, the 
>> number is 603254525
>> I'm completely stumped here, can someone help?
>> many thanks in advance
>> bernhard
>>  _______________________________________________
>> cisco-voip mailing list
>> cisco-voip at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/cisco-voip
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: text/enriched
Size: 5338 bytes
Desc: not available
Url : https://puck.nether.net/pipermail/cisco-voip/attachments/20060504/1d8af2c0/attachment-0001.bin