# sign at end of CFNA on BCM with PRI???

[cheeses]

We have moved from CallPilot to a external 3rd party voicemail. CFNA after 4 goes over PRI to external V-Mail like so. 91234567F78F785555#. It seems that the PRI interprets the # sign as the "end of the string" as the # is never sent. The 5555 is sent and I can manually dial the # to send the caller the right mailbox.
Is the parameters for # end of string programmable in the BCM or is it a Telco change?
The # is sent on another BCM that uses copper for outdialing.
Any thoughts?

 

[aragon]

PRI uses en-bloc signalling on Norstar.
A fixed number of digits are collected before the dialing string is presented.
Try increasing the public DN length by one digit for the specific dialing string required for the third party mail.

 

[cheeses]

Increased public DN for default prefix by 1, no difference. Made it 11 no difference.(other than a longer connect time). The seven digits are sent and the number is dialed, voicemail voice answers and the mailbox number is automatically dialed into the voicemail system. The # sign is not sent. Set up the same BCM up to use a copper line. (stole the fax line for testing) and when using the copper the # sign is sent. Is this strange or !!!

 

[aragon]

The call will take longer if you are unable to generate the # as the system will wait 4 seconds until it sees the required number of digits defined in the DN length.
This is normal.
I'm not sure how you would tag the # to the end of the dialing string on PRI.