shopcomputer

When I press 1 to connect call it does not detect the dtmf. ver 4.0.1.3452 , this worked in earlier versions. DTMF works otherwise, for both incoming and outgoing calls, e.g. i can call in from my cell phone, and place an outbound call.

What do you see in the log?

Extension numbers are supposed to start between a 2-7, see your setting on the domain page.

There must be something wrong with your dial plan, it usually will not autodial if the number starts with a 0.

We have those set, that does not affect incoming calls, it only affects utbound dial plan.

I added 17185551212 as an alias on a extension, the PBX changed it to718-555-1212 5] 2010/04/13 18:56:05: Identify trunk (IP address/port and domain match) 5 [5] 2010/04/13 18:56:05: Trunk Voip Innovation Global (global) sends call to 17185551212 in domain pbx.company.com [5] 2010/04/13 18:56:05: Trunk call: Could not identify user If I have the carrier send it without the 1 it works, however they prefer sending with the 1.

Set the amount of registrations at the domain level. In order to block a admin from changing a SIP password, you need to change this setting glovally, Allow domain admin to create or change accounts, it will affect all Admins on all domains.

You need to do it manually.

870 still very buggy, I ended up replacing the 870 for my customer with the 370, now DTMF works and all his other bugs went away, and he is a happy customer.

Fixed 4.0.1.3442

You don't need a seperate trunk for each DID, you only need multiple trunks for multiple carriers. remove the 300 from the send to field, On hunt group 300 put the 2 phone numbers after the extension number seperated by spaces. If it does not work look at the log to see what is going on.

just put it near the extension number as an alias.

in 4.0.1.3438 still no good, are you refering to the next release?

Why would someone in South America pick EDT? maybe a global setting 12 or 24 hour format.

anyone?

anyone?

Domain Time zone is best for domain cdr's, for extension CDR's it should use extension override time zone if it exists.

yes, never ran into a sip registration issue with fortinet.

We use Fortinet for our clients, we don't set routing lists, it works fine.

Did you try all the CID types on the trunk? P aasterted, No Indication, etc., we had this requirement a while back and were able to change the CID type on our inbound trunk to acomplish this, we did have 2 trunks though 1 for in and 1 for out.

Set the ANI on the extension, set the CID on the incoming trunk to no indication.

I have a prospect who needs to be able to set the ANI from his handset before each call. How can I set him up to be able to set the ANI on the fly from his handset.

Well I am coming from much earlier 4.0 beta, this my internal system, I am on 4.0 beta for many month's, it was very stable, my hosted system is still on 4.0.0.3217, very stable. No SOAP involved, see attached screenshot.

I am Running Windows, I updated to 4.0.1.3438, no change, I restarted the service, made 2 calls, first worked second did not, I attached the log. log.txt

What changed from earlier 4 versions, my IVR's stopped working. If I restart the PBXnSIP service it works for 1 call, the next once just hears silence.