asterisk users - Nov 2005 - Dial ZAP with group (g2) erroneously says call answered when it is still ringing

Hi Folks,

Took some effort to even realize what was happening and I did not find 
anything obvious in the archives or FAQs to explain it.

Simply put, if I have a dial plan that dials to a specific ZAP line (ie 
exten => _XXXX,n,Dial(Zap/2/${calling}&SIP/${calling}@${calling},15,tr)) 
then both the SIP and the ZAP are called and ZAP keeps reporting 
"ringing" until they are answered or a timeout occurs. This is the 
correct expectation as I understand it.

But... When I change the ZAP channel to use a group (ie exten => 
_XXXX,n,Dial(Zap/g2/${calling}&SIP/${calling}@${calling},15,tr)) then I 
always get something like :

    -- SIP/8438-37ca is ringing
    -- Zap/3-1 answered SIP/8438-be27

Even though the Zap channel is _not_ answered. The phone does keep 
ringing and I can complete the call if I pick up the phone.

So using single channels (either of the 2 I use) works, but together in 
a group gives me these results. I am using the latest CVS of everything.

Any explanation, workaround greatly appreciated :),
JES
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3684 bytes
Desc: S/MIME Cryptographic Signature
Url :
http://lists.digium.com/pipermail/asterisk-users/attachments/20051122/b01004b3/smime.bin

I'm going to guess here that the problem is *not* related to using the
g. It just happnes to be that on your asterisk system when you use g2
it rings to an FXO module while when using channel 2 on the zap
interface you are calling an FXS channel. Please correct me if I'm
wrong.
Zap FXO modules will consider themselfs answered as soon as it goes of
hook (as this is realy called answered, since all the signalling is
done inband), as will FXS modules, but FXOs are meant to call ppl
using in band signalling, and that is what tells you (the caller) if
the person answers or not, but because it uses in band signalling it
is actualy answred as soon as you pick up the phone (just like your
ananlog handset that is plugged into an FXS module *answers* the line
as soon as it goes off hook, even though it is just trying to make a
phone call). The only way to work this around is if you use c in the
dial command for the zap channel, but then the called person has to
press # to connect the call.
Hope this helps.

On 11/22/05, James B. MacLean <macleajb@ednet.ns.ca>
wrote:
> Hi Folks,
>
> Took some effort to even realize what was happening and I did not find
> anything obvious in the archives or FAQs to explain it.
>
> Simply put, if I have a dial plan that dials to a specific ZAP line (ie
> exten =>
_XXXX,n,Dial(Zap/2/${calling}&SIP/${calling}@${calling},15,tr))
> then both the SIP and the ZAP are called and ZAP keeps reporting
> "ringing" until they are answered or a timeout occurs. This is
the
> correct expectation as I understand it.
>
> But... When I change the ZAP channel to use a group (ie exten =>
> _XXXX,n,Dial(Zap/g2/${calling}&SIP/${calling}@${calling},15,tr)) then I
> always get something like :
>
>     -- SIP/8438-37ca is ringing
>     -- Zap/3-1 answered SIP/8438-be27
>
> Even though the Zap channel is _not_ answered. The phone does keep
> ringing and I can complete the call if I pick up the phone.
>
> So using single channels (either of the 2 I use) works, but together in
> a group gives me these results. I am using the latest CVS of everything.
>
> Any explanation, workaround greatly appreciated :),
> JES
>
>
> _______________________________________________
> --Bandwidth and Colocation sponsored by Easynews.com --
>
> Asterisk-Users mailing list
> Asterisk-Users@lists.digium.com
> http://lists.digium.com/mailman/listinfo/asterisk-users
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-users
>
>
>