Voxalot / SIP Broker Support Forums

Voxalot / SIP Broker Support Forums (https://forum.sipbroker.com/index.php)
-   Voxalot Support (https://forum.sipbroker.com/forumdisplay.php?f=4)
-   -   can't check voicemail (https://forum.sipbroker.com/showthread.php?t=1899)

rbrewer 07-18-2007 07:51 AM

can't check voicemail
 
I'm a SunRocket refugee. I unlocked my AC-211 "gizmo" ATA and am using it with voxalot. My ATA is behind my router. I was able to dial into my ATA via a Sip Broker access number and both talk and leave voice mail. However, when I dial *500 from the ATA to check voice mail, I get a busy signal. I have also tried dialing 500 and 500#. I also found *600 mentioned as an audio path test in the forums and that gives a busy signal too. Thanks for any suggestions. I have no VSPs or other voxalot settings configured... just a basic account.

martin 07-18-2007 08:06 AM

Quote:

Originally Posted by rbrewer (Post 10593)
I have also tried dialing 500

If dialing 500 does not work and you have no smart call(dial plan) entries then I would suspect the calls are not even reaching Voxalot or your credentials are incorrect.

Try and get *600 or 600 (echo test) working first, then the other stuff should fall into place.
.

rbrewer 07-19-2007 04:18 AM

Seems my ATA dialplan string was at fault. Now I can access the echo service and voicemail, but I must dial *600# and *500#.
Original (nonworking) dialplan: [x*][x*].
working dialplan: >#|[x*][x*].

I tried using >#|[x*][x*].T which I thought would allow me to avoid
entering the # symbol at the end of the numbers but it didn't help.
Any thoughts? Thanks for a nifty service.

stebie 07-19-2007 07:22 AM

Try encapsulating your dial plan in rounded brackets, so it looks something like:

(>#|[x*][x*].T)

rbrewer 07-24-2007 02:59 AM

The parens on either side didn't seem to make a difference for my dialplan. I did a bit more fooling around and either of these seem to work fine for my purposes right now:
(>#|[*x]x.T)
(>#|*xx.T|xx.T)

For now I'm using the first since it's shorter. I can dial *500 or *500# and get the voice mail. Since I don't have an outbound service provider configured I can't check normal numbers. For some reason the AC-211-SR doesn't seem to like [*x][*x]. or [x*][x*].

Webski 08-04-2007 01:29 AM

:mad: :mad:

it's never easy is it
I can't seem to register my AC-211 with Voxalot.. I've tried using your dial plan and follow settings from Voxalot, but no luck.
The ATA is behind the router just like yours and before everything was working perfectly with SIPDiscount, but no such luck with Voxalot. I've tried using the STUN server stun.voxalot.com.au and tried without it, no luck, no registration. What do you have for "NAT IP Address:"? Any pointers at all?

Webski 08-05-2007 05:18 PM

OK, more questions! The next day my AC-211 ATA did get registered and for a while everything was fine, that is I could access the voice mail by dialing *500# and make outbound calls. However, as of yesterday, while I still can call out using a SIP Discount VSP, I am getting busy signal when trying to access my voice mail... The same is true for the echo test number *600# (or*600, or 600, or 600#).

Any ideas?

My ATA dial plan is:
(>#|[*x]x.T)

The dial plan in Voxalot is:
_00.

The only VSP is "SIP Discount" which is not registered and only used for outbound calling (without any problems by dialing 00-country code-city code-local phone#).

martin 08-05-2007 11:00 PM

Quote:

Originally Posted by Webski (Post 11354)
*500# and make outbound calls. However, as of yesterday, while I still can call out using a SIP Discount VSP, I am getting busy signal when trying to access my voice mail.

Any ideas?

Sounds like your device is not letting * prefixed numbers get out the front door. You can confirm this by dialing a few others like:

*393612
*266300

If your Voxalot dial plan rules do not intercept the following numbers:

500
600

(no leading *) then you should also be able to get to VM and echo test respectively.
.

rbrewer 08-06-2007 04:19 AM

At the moment I'm not using voxalot, mainly because my requirements aren't
sophisticated enough to warrant it. I think I did settle on the following dialplan:
(>#|*x.T|xx.T)
Maybe give that a try... I don't think the AC-211 was liking the [*x] syntax.

My NAT IP field is blank. I'm running the latest firmware, 4.6.22, from this page:
AC-211/AC-211-SR/AC-211-N VoIP Consumer Device Firmware

Webski 08-10-2007 01:21 AM

Quote:

Originally Posted by martin (Post 11362)
Sounds like your device is not letting * prefixed numbers get out the front door.

Okay, here's the resolution. Martin was correct. I forgot to mention that my AC-211N ATA was not only behind a regular router with NAT, but also behind a (locked) Lingo ATA (another router with NAT, which was the first device after the cable-modem), so to make it all work I had to:

1) Put my router in the DMZ of the Lingo ATA
2) Put AC-211N in the router's DMZ
3) Change a SIP port on the AC-211N from 5060 to 5061
4) Forward the 5061 port on the router to the ATA's IP
5) Change the RTP port from 16346 to RTP 16347
6) Forward the 16347 port on the router to the ATA's IP.

The AC-211N ATA registered with the Voxalot server the moment I finished step 4 (I was also able to call in my ATA using a local access PSTN + Voxalot phone number). Also, after step 6 I was able to hear incoming caller's voice. No problem accessing the voice mail and the echo test.

Now, I haven't had time to leave current port forwarding in place and remove both DMZs, but I'm going to test it at some point.

I'm also using a STUN server in the AC-211N SIP configuration.


All times are GMT. The time now is 03:28 PM.

Powered by vBulletin® Version 3.7.2
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.