Incoming call from an spa400

[carloscd]

I installed VicidialNOW CE 1.3 and I followed vicidial manager manual on "C. Create an inbound-group, point a DID at it, and take calls" but I cannot receive inbound calls, for testing purposes I have a linksys spa400 which I used from another asterisk server without problems.

What the logs says is:

SIP/2.0 404 Not Found

when incoming call, any hint or resource where to read?

Thanks in advance!

[williamconley]

1) Please post your entire setup (although vicidalnow ce 1.3 is helpful) you need to post your vicidial version with build and your asterisk version. You did post your installation method, which is helpful, and indicated your hardware extra, but the rest is a requirement to post.

2) I am seriously impressed that you quoted the line you died on from the manual! that's enough to qualify for an answer no matter what, in my book.

so: when you "pointed the DID at it" what context is the inbound DID set to?

when a call arrives, through any protocol (IAX/SIP/ZAP, whatever) it arrives at the context for the protocol and is told within that context which context inbound calls should be sent to. for instance, if you have a sip context named "binfone" and a call arrives from binfone's sip account, asterisk will check the binfone sip context to see if there is a "context=" line, and will send the call to that context. many providers and hardware manufacturers plug a "default" value in there (i mean that literally, some actually list "context=default" as a line entry). Unfortunately, that will NOT get the call to a place where vicidial's agi scripting can control it.

so: context=trunkinbound

that line should be included in the protocol context for this inbound call to route the call to vicidial's "trunkinbound" context, which will handle most inbound call types quite efficiently from that point.

if you aren't sure, you can look for the trunkinbound context and see what is in it and then watch your CLI to verify that the call is being properly handled when it gets there (compare what you are seeing on the CLI to the contents of trunkinbound to see if there is a conflict). Ordinarily, however, once you get the call to the trunkinbound context, the agi script that resides there takes over and vicidial manages the call correctly.

PS: I apologize for the "context,context" references above, but please remember that there is a context for the call to arrive on (sip,zap,iax) and then there is a context in extensions.conf or one of its included configuration files such as extensions-vicidial.conf.

still confused: the sip,zap,iax context is there to capture the call, authenticate it, and then send it to extensions.conf for call handling. when the call arrives at extensions.conf, it once again arrives at a place called a context, but this time the context is in extensions.conf (call handling) instead of somewhere like sip.conf (protocol and auth decisions). i did not make up the naming semantics for this software, i am just giving directions in it. LOL