OBI-100 Voice Gateway AccessNumber Syntax Bug

<< < (2/2)

Taoman:
Quote from: JaskHill on May 10, 2020, 10:02:09 am

So I assume it is the recommended way to do things, over the original way from the user manual.


Possibly, but I doubt it. I'd be surprised if there's anyone reading this forum who also uses Voice Gateways that configures their VGs in the same way you are doing it.

If memory serves, I think I remember playing around with that string syntax using Speed Dials and I ended up with a long ass string for something I was trying. The result got truncated as you are experiencing. My guess is there is a character limit that you are bumping up against.

Do International calls work ok thru VoIP.ms using a VG when just using the provided AuthUserID and AuthPassword fields? As I'm sure you're aware, VoIP.ms implemented new Caller ID regulations as of 1-1-2020.
Quote

In line with all the recent rulings in favor of protecting and empowering consumers, VoIP.ms will start enforcing valid Caller IDs as per the NANPA and ITU-T E.164 standards as of January 1st, 2020.
Therefore, calls displaying the following Caller ID information will be blocked by our platform:

   1.International calls with Caller ID containing less than 7 digits and greater than 15 digits;

If you are passing your Caller ID from VoIP.ms customer portal, please review your Caller ID number to make sure it complies with these standards.

zapattack:
Quote from: JaskHill on May 10, 2020, 10:02:09 am

This new feature is mentioned in the release notes. So I assume it is the recommended way to do things, over the original way from the user manual.

It is under the heading Enhancements, which means another, optional way.
It does not say recommended, preferred, or supersedes the existing method.

arko12:
Have you specified a long enough string in correct format in Digit Map?
SP1 map not used

Navigation

[0] Message Index

[*] Previous page