IP dialing

Forums › VoIP › IP dialing

ballistyx

44 posts

Geek
+1 received by user: 1

#249165 28-Apr-2019 20:53

I can't, for the life of me, get IP dialing to work between two ATA on the same subnet.
I have read numerous pages offering information, but none seems to fix my issue.

I would like House B to be able to dial House A if the internet is down *, but all IP dialing info either assumes an internet connection, or that, as I don't have an internet connection, I am good to turn off "register" on the ATA.
Each ATA is on a separate SIP account, and data between the two houses goes through an Archer C7 router.

I've read pages that tell me to simply turn on "Make/Ans call without reg", turn on "IP dialing", maybe add a quickdial to the dialplan (e.g. 22S0<:@192.168.1.100:5060>, put URI in Speed Dial . . ..
The speed dial didn't even want to dial a normal number until I turned on the option Speed Dial Serv, which none of the pages even mentioned. However, various combinations of address in the speed dial field returned only beep..beep..beep..beep.

Is it unrealistic to expect one ATA to communicate with the other via LAN without the VSP? Am I missing something blindingly obvious?
Information on the relevant sites for the PAP2T and SPA2102 is woefully lacking on the functionality of IP dialing.

* incoming internet is at my house, and if that fails early in the morning, someone has to come over from the other house to wake me up and fix it!

Ah, the idyllic rural life . . .

no cellphone reception
no UHF TV reception
no ADSL

I'm surprised I still have my sanity!

speed

296 posts

Ultimate Geek
+1 received by user: 101

#2227042 28-Apr-2019 21:30

> Is it unrealistic to expect one ATA to communicate with the other via LAN without the VSP? Am I missing something blindingly obvious?

Nah, I think you've just got yourself a couple of sh|t ATAs ;-)

(they're both basically the same thing code-wise for the SIP stack)

I haven't specifically tried it, but I'd expect that a Yeastar ATA would work in this scenario.

You could try using a soft phone on a laptop to IP-dial one each ATA and make sure they do actually ring when they get an INVITE that isn't from their SIP registrar. Then, assuming they do, you could replace the remote end ATA with a Yeastar (or other suitable alternative).

ballistyx

44 posts

Geek
+1 received by user: 1

#2227058 28-Apr-2019 23:04

Sh|t they may be, but they were perfectly adequate until I tried to make someone else's life easier. Meh, let them walk over to get me - I still have to wake up anyway!

I looked at the Yeastar pages, and it does seem to imply this. But then, so would the SPA documentation if you weren't alert. I would only need one, as long as mine will receive (and that ticking "Ans. without reg" does anything). Might look at the softphone test. Cheers.

I could do it with a teamspeak or similar, but that would assume my own PC was awake and with speakers up. If I've been gaming until 3am, then at 8am my PC, like me, is powered down, and the headphones will still be plugged in where I left them, so teamspeak won't do it lol

Ah, the idyllic rural life . . .

no cellphone reception
no UHF TV reception
no ADSL

I'm surprised I still have my sanity!

sbiddle

30853 posts

Uber Geek
+1 received by user: 9996

Retired Mod

Trusted

Biddle Corp

Lifetime subscriber

#2227095 29-Apr-2019 08:36

Cisco SIP / URI calling works perfectly on the PAP2 / 2102 and later SPA112/122 units (which are actually a completely different device despite having the same provisioning and features). I've got plenty of units deployed that rely on this and they're still the best ATA ever built despite the fact they've been largely unsupported for 6 or 7 years now.

ballistyx

44 posts

Geek
+1 received by user: 1

#2227137 29-Apr-2019 10:29

sbiddle:

Cisco SIP / URI calling works perfectly on the PAP2 / 2102

Well, that was always the impression I got from reading, but implementing it . . different story!

I'll head over to the other house today and try a few things I couldn't from here. The PAP has a spare line, so I might fiddle with that to see if changing proxy etc will work :) I don't want to make any changes that will impact normal call dialling etc!

Ah, the idyllic rural life . . .

no cellphone reception
no UHF TV reception
no ADSL

I'm surprised I still have my sanity!

sbiddle

30853 posts

Uber Geek
+1 received by user: 9996

Retired Mod

Trusted

Biddle Corp

Lifetime subscriber

#2227360 29-Apr-2019 13:30

I can't really add anything to this as I don't know your setup. I can assure you it works just as described and I've had zero issues with the many deployments I have.

ballistyx

44 posts

Geek
+1 received by user: 1

#2227691 30-Apr-2019 02:41

Complicated setup!
Wireless broadband in > Archer C7 > NanostationM5 bridge > WR842 > PAP2 ATA

That's in its simplest version, as there are >25 different switches, radios & devices over the whole property.
One ATA (2102) is on the Archer, the other is across the road on the WR842. I don't doubt that it all works perfectly for you, but for some reason I just can't get it through my skull.

Does your own experience jibe with everything I've read i.e. turn on IP dialling, make/ans. w/o reg, put one additional string in dialplan and Bob's your Auntie? Any further suggestions for the clinically frustrated?

Ah, the idyllic rural life . . .

no cellphone reception
no UHF TV reception
no ADSL

I'm surprised I still have my sanity!

Geekzone

Want to support Geekzone and browse the site without the ads? Subscribe to Geekzone now (monthly, annual and lifetime options).

speed

296 posts

Ultimate Geek
+1 received by user: 101

#2227700 30-Apr-2019 07:13

You haven't described the exact mode of failure you're experiencing... What are the symptoms on the ATA when you try to straight out IP dial (not speed-dial tricks)? Is it that the calling end provides ringing tone but the called end doesn't ring? Or does the calling end provide some other tone? If you get tones, how far through the dial string do you get before you hear them?

Also, are you remembering to pad out each IP quadrant with leading zeros? Eg 010#001#001#020 (I can't remember whether it's * or # that is the dot-identifier).

ballistyx

44 posts

Geek
+1 received by user: 1

#2228044 30-Apr-2019 15:51

speed:

You haven't described the exact mode of failure you're experiencing... What are the symptoms on the ATA when you try to straight out IP dial (not speed-dial tricks)? Is it that the calling end provides ringing tone but the called end doesn't ring? Or does the calling end provide some other tone? If you get tones, how far through the dial string do you get before you hear them?

Also, are you remembering to pad out each IP quadrant with leading zeros? Eg 010#001#001#020 (I can't remember whether it's * or # that is the dot-identifier).

Good points. I've tried several variations with direct dialling (apparently * is dot and # is colon), and no matter how I try it, the result is that the calling handset give me beep..beep..beep..beep - the same tone as when you leave the handset off hook for too long. I don't have a sequence in my dial plan for that format, but I am given to understand that there are implicit dial rules applied in certain circumstances, like when IP Dialing is ticked.

I hadn't looked to see at what point the tone changes, as I was always looking at the keypad as I dialled! Having now checked, it fails when I dial the first special character. If I don't use * or #, it fails when the entire string is entered, and probably just due to timeout.

Ah, the idyllic rural life . . .

no cellphone reception
no UHF TV reception
no ADSL

I'm surprised I still have my sanity!

speed

296 posts

Ultimate Geek
+1 received by user: 101

#2228057 30-Apr-2019 16:09

ballistyx:

I hadn't looked to see at what point the tone changes, as I was always looking at the keypad as I dialled! Having now checked, it fails when I dial the first special character. If I don't use * or #, it fails when the entire string is entered, and probably just due to timeout.

What you describe sure does sound as if IP dialling were disabled. I wish I knew more about the PAP2T and it's inter-dependence between settings (eg outgoing proxy as you mentioned, or having an account registered etc). I've used a few PAP2T and SPA2102 in my time but don't recall the UI well enough to give any more useful info sorry :(

I actually just put a PAP2T to rest last week (it died in a mode where the LEDs were on but it didn't respond to IP over the LAN or any DTMF tones on the FXS port).

If the ATA at your end does answer direct-IP calls then I might be able to find you an el-cheapo (eg $10) old IP deskphone you could put at the other end. You could even set it in 'taxi phone' mode so that they simply lift the handset off hook to call your end (or trigger any manner of automated 'the internet is down!' warning bells and alarms at your 'NOC' :)

ballistyx

44 posts

Geek
+1 received by user: 1

#2228117 30-Apr-2019 18:25

speed:

If the ATA at your end does answer direct-IP calls then I might be able to find you an el-cheapo (eg $10) old IP deskphone you could put at the other end. You could even set it in 'taxi phone' mode so that they simply lift the handset off hook to call your end (or trigger any manner of automated 'the internet is down!' warning bells and alarms at your 'NOC' :)

lol - if I can ever determine that, I may well take you up on the offer! So far, I've mostly been trying it one way, but will have to sit down at the other end and dial a few numbers to see if it works. I had assumed that it would be pretty simple, and would work as well n one direction as the other, but there might be 'irreconcilable differences' between the ATAs.

Ah, the idyllic rural life . . .

no cellphone reception
no UHF TV reception
no ADSL

I'm surprised I still have my sanity!