I looked deeper into the command issue and it seems that the commands were modified. Which is the reason why it wasn't sending out. So I worked on this one and attached it to the contact. Seems to work but I need a second pair of eyes.
notify-service-by-epager
/usr/bin/printf "%b" *Alert*\nNotification Type: $NOTIFICATIONTYPE$\nService: $SERVICEDESC$\nHost: $HOSTALIAS$\nAddress: $HOSTADDRESS$\nState: $SERVICESTATE$ \nInfo:$SERVICEOUTPUT$ | /bin/mail -s "* $NOTIFICATIONTYPE$ Service Alert: $HOSTALIAS$/$SERVICEDESC$ is $SERVICESTATE$ *" $CONTACTEMAIL$ $CONTACTPAGER$
notify-host-by-epager
/usr/bin/printf "%b" *Alert*\nNotification Type: $HOSTSTATE$ \nHost: $HOSTNAME$ \nAddress: $HOSTADDRESS$ \nInfo: $HOSTOUTPUT$ | /bin/mail -s "Alert" $CONTACTPAGER$ $CONTACTEMAIL$
I tested this by submitting passive check results for critical for the service and I received them without issue. However when NagiosXI was doing the paging.... I got this on the occasion:
[1427642733] wproc: host=servername; service=printqueue name; contact=billings
[1427642733] wproc: stderr line 02: /bin/sh: -c: line 0: `/usr/bin/printf "%b" *Alert*\nNotification Type: PROBLEM\nService: printqueue name\nHost: servername\nAddress: printerip\nState: CRITICAL \nInfo:CRITICAL: \\Print Queue\\Jobs: 13 critical | /bin/mail -s "* PROBLEM Service Alert: servername is CRITICAL *"
[email protected] '