Running a PIAF installation:
FreePBX Version = 2.10.1.19
Running Asterisk Version = 1.8.28.0
Pin set module version is 2.11.0.9
When I dial out of the trunk that has the pin set assigned I get the message “call cannot be completed as dialed”.
== Using SIP RTP TOS bits 184
== Using SIP RTP CoS mark 5
-- Executing [<longdistnumber>@from-internal:1] ResetCDR("SIP/2311-0000087e", "") in new stack
-- Executing [<longdistnumber>@from-internal:2] NoCDR("SIP/2311-0000087e", "") in new stack
-- Executing [<longdistnumber>@from-internal:3] Progress("SIP/2311-0000087e", "") in new stack
-- Executing [<longdistnumber>@from-internal:4] Wait("SIP/2311-0000087e", "1") in new stack
-- Executing [<longdistnumber>@from-internal:5] Progress("SIP/2311-0000087e", "") in new stack
-- Executing [<longdistnumber>@from-internal:6] Playback("SIP/2311-0000087e", "silence/1&cannot-complete-as-dialed&check-number-dial-again,noanswer") in new stack
-- <SIP/2311-0000087e> Playing 'silence/1.gsm' (language 'en')
-- <SIP/2311-0000087e> Playing 'cannot-complete-as-dialed.gsm' (language 'en')
== Spawn extension (from-internal, <longdistnumber>, 6) exited non-zero on 'SIP/2311-0000087e'
-- Executing [h@from-internal:1] Hangup("SIP/2311-0000087e", "") in new stack
== Spawn extension (from-internal, h, 1) exited non-zero on 'SIP/2311-0000087e'
The trunk provider says they’re receiving the traffic. I placed a password for the outbound route in the Password field and removed the pin set; that’s working correctly. The pin set module, isn’t, however. I looked around, and the only forum posts that I could find do not have a solution, or stated that there was a fix in an earlier version of the pin set module.