VoicePulse & CommuniGate Pro

For VoicePulse, you will need to use the CG/PL "GatewayCaller" application included in the CGP release (starting in 5.0.8 I believe). The GatewayCaller application configures CGP to act as a B2BUA for gateway access, thereby correctly authenticating all calls when the gateway requires all SIP INVITES to be sent by a registered proxy.

Here are the basic instructions for setting it up:

1) I've still been adding the SIP Gateway to SETTINGS->SIP->Gateways, but truthfully I don't think it's necessary at all with the GatewayCaller setup, so authentication is Disabled in SIP Gateways in the below example. (This is how our VoicePulse account is setup, and works find.)

Gateway Name: VoicePulse
Domain: access1.voicepulse.com
Via: <blank>
Username: <your account>
Auth Name: <your account>
Password: <your password>
Authenticate: Disabled
Proxy: None
Substitute: [X] From [ ] To
Contact: pbx@<your.IP.address.X>
Register Every: never

2) Add new "Directory Integration" custom attributes [Domains->Directory Integration]. Add these attributes:

sipGatewayDomain
sipGatewayFrom
sipGatewayPassword
sipGatewayUsername
sipGatewayVia

3) Assign the appropriate authentication credentials to the domain or accounts. The GatewayCaller application authentication can be simply used by the entire server/cluster, or assigned to a particular domain, or even assigned granularly to every account (i.e., every account can use a different Gateway for calling). Here is an example for assigning the GatewayCaller authentication to an entire domain:

[Domains->(All Domains)->Account Defaults]
You should now see your custom attributes above, listed in the Settings. Fill these in with your account details:

sipGatewayDomain: access1.voicepulse.com
sipGatewayVia: <blank>
sipGatewayFrom: <your account> (example: "a01234567")
sipGatewayUserName: <your account> (example: "a01234567")
sipGatewayPassword: <your password>

4) Add the gatewaycaller application to your Router setup [SETTINGS->Router] according to your dial string. For example, the following would match all numbers over 7 digits, in the Default Domain:

; GatewayCaller setup - all accounts in domain
N:S:<(7+d)> = gatewaycaller--*#postmaster

This notation calls the GatewayCaller application with an argument of <phone-number-dialed> and run from the postmaster account. You could also setup a different gatewaycaller application for every account in your domain, for example:

; GatewayCaller setup - one account in domain (e.g., "myaccount")
N:S:<(7+d)> = gatewaycaller--*#myaccount

That should be it. Calls which match the Router dial string should be routed through the GatewayCaller application, and you will see entries like this in the logs (if logging levels are increased):

0:08:10.77 2 PBXLEG-81110 'gatewaycaller' created for postmaster@example.com
10:08:10.77 5 PBXLEG-81110 REQUEST posted
10:08:10.77 2 SIGNAL-30192 INVITE relayed to NODE-81110: sip:14155551212@example.com
10:08:10.77 5 SIGNAL(1) 330192: idling
10:08:10.77 5 NODE(2) 381110: processing REQUEST
10:08:10.77 4 PBXLEG-81110 INVITE request received

Please let me know if you have any problems setting this up. Sincerely,

-t