Slash in recipient name or line name causes share writing to fail

If a slash (/) is used in an inbound routing recipient or line name, the routing to the share will fail because that is an invalid character in a filename.  The resolution is to use an alternate character such as a dash (-) or underscore (_) instead.

Example of failure in inbound fax log when a / is used:

No such file or directory - /smbfs/192.168.2.10_temp/fax_inbound_Line / 2 (ext RING)_20120510_135904_recv0004.pdf

Example of same routing except when a - is used instead and the file writing works:

Share  	//192.168.2.10/temp/fax_inbound_Line - 2 (ext RING)_20120510_140353_recv0005.pdf