|
Hi List, I’m having a bit of an odd problem with asterisk and
outgoing zap calls. Tzafrir has been kind enough to help me get the logging
sorted out so I have some idea of what’s going wrong, but I’m a
little flummoxed. Essentially the symptoms are as follows; Make a SIP call from Cisco 7960 or 7940 to asterisk, where
it is routed out on a ZAP (x100p) line. After exactly 2mins 40seconds (+- 1sec) the call is hung up,
“normal clearing” (although obviously it’s actually an analogue
line) The same symptoms are not experienced with incoming calls on
the same zap line, nor with internal SIPàSIP calls, or external SIPàSIP or SIPàIAX calls. With full logging enabled, just before the hang up, this is
written to the log: Oct
26 18:04:59 DEBUG[10822] chan_sip.c: = No match Their Call ID: 5907c40463e18
[EMAIL PROTECTED] Their Tag as6e46885a Our tag: as2b18a370 Oct
26 18:04:59 DEBUG[10822] chan_sip.c: = Found Their Call ID: 003094c4-4ea9000 [EMAIL PROTECTED]
Their Tag 003094c44ea90008745cabf1-6f4660c7 Our tag :
as56514c99 Oct
26 18:04:59 DEBUG[10822] chan_sip.c: **** Received CANCEL (14) - Command in SIP
CANCEL Oct 26 18:04:59 DEBUG[10865] channel.c: Hanging up channel 'Zap/2-1' Oct 26 18:04:59 DEBUG[10865] chan_zap.c:
zt_hangup(Zap/2-1) Oct 26 18:04:59 DEBUG[10865] chan_zap.c: Hangup: channel: 2
index = 0, normal = 21, callwait = -1, thirdcall = -1 Which seems to indicate that the phone actually
issued a cancel (of course, unless I’m reading it wrong). Has anyone seen this before? Or had any ideas of
what it could be? Or even just where to start looking… Very best regards,
|
_______________________________________________ --Bandwidth and Colocation provided by Easynews.com --
asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
