Caller ID issue => Betamax account in Voice Gateway

(1/3) > >>

Momo:
Hi,

I need your help to get the caller ID working with Rynga (Betamax account)

My rynga account is configured in Voice gateway 3. And the caller ID has been "verified" by rynga. If I use their software, caller ID is working.

I had the same issue before with PAP2. In order for outgoing CID to work, I had to put the desired and verified number in the "User ID" field, and enabled the "Use Auth ID" and entered my username in the AuthID field.

But I don't know how to configure with Obi. People are only getting unknown or private number.

Thanks for your help.

Stewart:
I don't know whether this will work with Rynga, but try e.g.
Voice Gateway3 -> AccessNumber -> SP2(sip.rynga.com;ui=3369950xxxx;op=ns)

Of course, substitute the actual value of the desired caller ID and the present settings for op= (if applicable).

If the above doesn't work, is it possible to move Rynga to an SPx and use a VGx for the provider currently there?

If that's not feasible, either, would Voxbeam or FlowRoute be an acceptable provider to send those calls?

Momo:
Hi Stewart,

Thanks for your reply. I am now in office. I'll try tonight. But what is "op=ns" ?

Stewart:
See description of enhancements to 1.2.1(2283) in http://www.obitalk.com/forum/index.php?topic=9.0

I'm very disappointed that Obihai doesn't include details like this when they update the Admin Guide.

Momo:
Thanks Stewart... But they say that

"Note that if userid or password is specified in VG1-8 AccessNumber, it overwrites the settings in AuthUserID, and AuthPassword in the VG."

If I understand, my username in AuthuserID will be overwritten with your settings...

Navigation

[0] Message Index

[#] Next page