404 error when making voice call on skype

Ive managed to set up a skype connect account and Status in ignition says “Registered with VOIP Host”. How do you actually the call out? I see their is an option to test pipeline and alarm notifications, but I am not sure how you create a pipeline?

Ok, here’s the basic steps to get some alarms out:

  1. Have a user source with some users with the appropriate kind of contact info, assigned to schedules that are active (use the “Always” schedule to not worry about schedules)
  2. Create a call roster with your user(s) you want notified.
  3. Create an alarm notification profile.
  4. Create an alarm on a tag. (In the Designer)
  5. Create an alarm notification pipeline (in the Designer, under “Global”)
    5a. Make your pipeline valid. The most simple pipeline is simply a pipeline directly connecting the Start block to a Notification block. Select your call roster and notification profile in the notification block.
    5b. Make sure you alarm’s “Active Pipeline” setting is set to your new pipeline.
    5c. Save in the designer to send the pipeline to the gateway.

Ok - now trigger your alarm and it’ll go into the pipeline, then into the notification profile and notify everyone on your call roster whose schedule is currently active and has the correct kind of contact info on them.

Check out the pipelines section of the gateway status page to watch alarms go through your pipeline.

I am pretty sure I did everything I was suppose to, but when i trigger a test memory tag to alarm. I look at alarm pipeline in gateway and it looks like it’s trying to do something, but I when I look in the console in configure I see the following error.

[ERROR] 1:53:09 PM Agent cannot find invite client transaction for call EbXLnMer-1366401186142@Eric-PC.haarmeyer.local
[ERROR] 1:53:08 PM CallManager Error state received from call manager. Reason: Not Found [404]

Could you perhaps go to console>levels and search for “Agent”, turn it to debug, and try again? Maybe edit the notification profile and save it to restart it.

Afterwards, export the log and attach it (or better, just go find the “wrapper.log” file in “{installdir}\logs”, zip it, and attach it).


Here is the wrapper log file zipped up. I did notice under modules Active X says it’s faulted. I attempted to restart it, uninstall it and reinstall it, but it was still Faulted. Not sure if Active X has anything to do with it.
wrapper.zip (11.8 KB)

I forgot to mention I did try edit and save on notification profile to restart it and also just in case i did a debug on the Agent in Levels and exported the logs as well and attached them.
logs.bin.gz (34.9 KB)


Hope you don’t mind, but I split this off into its own topic as it should be, and moved it to the beta forum.

Ok, actually, I think the problem is simply that the phone number isn’t correct! You’re calling a number “575…”, try putting a 1 in front, so “1575…”.

If this turns out to be true, we’ll have to make the error message a little more helpful…


Wow…this whole time. Just needed to add the 1 for long distance. We usually do not have to do that with traditional call out boxes. But yes it did call me with the 1 in front over number. Thanks

No problem, don’t feel too bad. Many phone systems account for this (if you were tying into an office asterisk system, for example, you might not have had a problem). The difficult side for us is that given the flexibility of voip, we can’t really do a lot of phone number validation. Or, we could, but it might limit the range of possible uses. For example, inside our office here, I can put in a number like “335” and call that extension.

Anyhow, this is what beta periods are for, we definitely should simply change the error to say “Unknown or Invalid phone number: 555-555-5555”. It would be nice to do something else, because I know you won’t be the only person to fall into this, but we’ll have to see.


Glad you got it working. Creating “dial patterns” is a big part of telephony including VoIP that you usually don’t have to think about. It’s more applicable when using phone numbers of various lengths, such as 4 direct digit extensions within your organization, international calls, etc.

1 is actually the country code for the US, although sometimes you might have to dial “00” or “01” first to designate an international call, depending on where you’re calling from. It sounds like Skype is trying to “be international”, although you’d think that they would adjust your dial plan based on your country profile.