I just love posting problems! ... not .. heres another

[Nortelguy]

I was using PRI to place calls. But have since moved to a sip provider. As soon as the call is placed over the SIP trunk it says "Call was answered" when really it wasn't. Here is the output .. Any ideas?

== Manager 'sendcron' logged on from 127.0.0.1
-- Executing AGI("Local/913057815757@default-11ac,2", "agi://127.0.0.1:4577/call_log") in new stack
-- AGI Script agi://127.0.0.1:4577/call_log completed, returning 0
-- Executing Dial("Local/913057815757@default-11ac,2", "SIP/69.42.117.220/3057815757||To") in new stack
-- Called 69.42.117.220/3057815757
-- SIP/69.42.117.220-08201768 answered Local/913057815757@default-11ac,2
> Channel Local/913057815757@default-11ac,1 was answered.
-- Executing Playback("Local/913057815757@default-11ac,1", "sip-silence") in new stack
-- Playing 'sip-silence' (language 'en')
-- Executing AGI("Local/913057815757@default-11ac,1", "agi://127.0.0.1:4577/call_log") in new stack
-- AGI Script agi://127.0.0.1:4577/call_log completed, returning 0
-- Executing AMD("Local/913057815757@default-11ac,1", "4000|1500|1500|6000|120|50|3|256") in new stack
-- AMD: Local/913057815757@default-11ac,1 3058888205 (null) (Fmt: 64)
-- AMD: initialSilence [4000] greeting [1500] afterGreetingSilence [1500] totalAnalysisTime [6000] minimumWordLength [120] betweenWordsSilence [50] maximumNumberOfWords [3] silenceThreshold [256]
== Spawn extension (default, 913057815757, 2) exited non-zero on 'Local/913057815757@default-11ac,2'
-- Executing DeadAGI("Local/913057815757@default-11ac,2", "agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----16-----ANSWER-----2-----1") in new stack
-- AGI Script agi://127.0.0.1:4577/call_log--HVcauses ... ---2-----1 completed, returning 0
== Manager 'sendcron' logged off from 127.0.0.1
== Parsing '/etc/asterisk/manager.conf': Found
== Manager 'sendcron' logged on from 127.0.0.1
== Manager 'sendcron' logged off from 127.0.0.1
-- AMD: ANSWERING MACHINE: silenceDuration:4000 initialSilence:4000
-- Executing AGI("SIP/69.42.117.220-08201768", "VD_amd.agi|8369") in new stack
-- Launched AGI Script /var/lib/asterisk/agi-bin/VD_amd.agi
== Spawn extension (default, 8369, 4) exited non-zero on 'SIP/69.42.117.220-08201768'
-- Executing DeadAGI("SIP/69.42.117.220-08201768", "agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----0---------------") in new stack
-- AGI Script agi://127.0.0.1:4577/call_log--HVcauses ... ---------- completed, returning 0
== Manager 'sendcron' logged off from 127.0.0.1
dialer*CLI>

[Nortelguy]

hmm hangon a tick now that I read this output further I see its still treating it like a PRI call. Do I disable all the zaptel features in the rc.local ? What is going to be my timer source since the calls are being placed over SIP ? Or does SIP not need that ?

[mflorell]

Who is your SIP carrier?

[williamconley]

when you have a hardware card installed, it will provide timing for the system regardless of whether it is being used for a specific call or not (otherwise we would have issues using SIP / IAX / E1 / etc on the same box). Obviously many facilities mix these different technologies to suit their needs for each call. So, once you install Hardware that supplies your timing, the timing is supplied for the entire system.

Unless you take the card out.

So it is likely that your issue lies in the interaction between your system and your provider's system. Why does your box think the call was answered? Are you using a provider that many others have used/are using? Did you set your SIP trunk up in an odd fashion?

[Nortelguy]

Thanks William for your reply, that information wasn't explained in the doc files, Or least I couldnt find it. Anyways, the sip provider I am using is Univoice they gave me what I should enter in my sip.conf

[SIPtrunk]
host=******** (Deleted for security)
type=friend
canreinvite=no
allow=all
dtmf=rfc2833

I'll give them a call ..

[Nortelguy]

Ok got the problem solved, now its a new problem the calls are coming across as all 'Answered' and being sent to the AMD detection then being sent to an agent. However that is not the case, the calls come to the agent and they are still 'ringing' in their headsets. I don't think AMD detection is the problem since asterisk is reporting the call as answered when indeed its not. So I guess this is sorta like my original problem except now I can answer the call. What process in asterisk determines if the call is 'busy' or 'disconnected' or actually 'answered' ?

[mflorell]

Sounds like either you or your carrier are sending an Answer signal on the call being placed. This is a fairly common setup problem. Check in the Asterisk CLI when the channel says that it was answered and if it happens during manual dialing of a number you should see where the Answer signal is happening.

[Nortelguy]

Ok thanks Ill post back my findings. say my setup was triggering an answer signal, where would this sort of thing be adjusted? Just curious.

[williamconley]

Examples (from a box with FreePBX and Vicidial):

from [from-sip-external] in "extensions.conf" in /etc/asterisk:
exten => s,n,Answer

from [default] in "extensions.conf" in /etc/asterisk:
exten => 8301,1,Answer