• V20: 3CX Re-engineered. Get V20 for increased security, better call management, a new admin console and Windows softphone. Learn More.

SPA3102 Dial Plan help

Status
Not open for further replies.

Daniel Martin

Joined
May 22, 2018
Messages
7
Reaction score
0
Before I start, I know, I know the SPA3102 has been done to death on this forum. Trust me I've read all the posts. I'm still stuck.

My SPA3102 registers. I've had luck on occasion receiving calls. I've had luck on occasions making calls, usually with "wrong number" messages from the local carrier, more on that later. I've never had both inbound and outbound working at the same time and I've narrowed it down to the dialing rules. I'm on the other side of the world to this setup talking to a receptionist and anyone who has used a receptionist as "remote hands" knows what I'm going through right now.

I just can't find any decent documentation explaining the dialing rule "language" used by the SPA.
For my system I want all inbound calls and all outbound calls to go out over the FXO port on the 3102.

My carrier does not require any prefixes to "get an outside line" just dial the number.

Here is some example dialing rules I have tried (10000 is the 3CX analog trunk):

(xx<:10000>) what do the xx indicate?
(S0<:10000>) is this placing a 0 in front of the number?
(xx.) default, no idea
<:10000> stab in the dark

For the love of all things VOIP can someone explain to me what is happening with dialing rules?
If I use (S0<:10000>) the carrier replies with "you have dialed an incorrect number.
(xx.) gives me an error on the handset, makes sense there is no where for it to go.
(xx<:10000>) I can't even remember what this combo does.

The problem is I don't know or can;t find a resource to program the dialing rule options.

Can someone please dig back to when you actually worked this out in your SPA3102 days and help a brother out. I'm so close to pulling the trigger on a $500 Patton, but that's a lot of beer money wasted!

Cheers

Daniel
 
The 3102 is two devices in one. If you are using only the FXO (plugging into a PSTN phone line and using that to bring a trunk into 3CX), then there really are no complicated dial rules used as such. The (S0<:10000>) is used on incoming PSTN calls to route the call to 3CX. It works like call forwarding. It tells the 3102 the any incoming PSTN call is to be sent immediately to10000 on VoIP.

If you are using the FXS port to plug in a phone (as an extension), then you may want to use dial-plans to speed up the calls.

Be sure that the 3CX trunk settings have the correct IP and port of the 3102 FXO
Post a 3CX activity log of one of the outbound calls.
Post the Line Tab settings of the 3102.

https://www.cisco.com/c/en/us/suppo...spa901-1-line-ip-phone/108747-pqa-108747.html
 
Last edited:
Activity Log of me trying a few different dialing rules:
06/21/2018 10:55:15 PM - [Flow] Target endpoint for 43285071 can not be built!
06/21/2018 10:37:58 PM - [CM503003]: Call(C:135): Call to <sip:[email protected]:5060> has failed; Cause: 487 Request Terminated/INVITE from 127.0.0.1:5080
06/21/2018 10:37:57 PM - [CM503003]: Call(C:135): Call to <sip:[email protected]:5060> has failed; Cause: 487 Request Terminated/INVITE from 192.168.13.134:5060
06/21/2018 10:37:57 PM - [CM503003]: Call(C:135): Call to <sip:[email protected]:5060> has failed; Cause: 487 Request Terminated/INVITE from 192.168.13.136:5060
06/21/2018 10:12:58 PM - Call to T:Line:10000>>0554216310@[Dev:sip:[email protected]:5062] from L:131.1[Extn:2001] failed, cause: Cause: 403 Forbidden/INVITE from 192.168.13.251:5062
06/21/2018 10:12:58 PM - [CM503003]: Call(C:131): Call to <sip:[email protected]:5062> has failed; Cause: 403 Forbidden/INVITE from 192.168.13.251:5062
06/21/2018 10:12:42 PM - Call to T:Line:10000>>0554216310@[Dev:sip:[email protected]:5062] from L:130.1[Extn:2001] failed, cause: Cause: 403 Forbidden/INVITE from 192.168.13.251:5062
06/21/2018 10:12:42 PM - [CM503003]: Call(C:130): Call to <sip:[email protected]:5062> has failed; Cause: 403 Forbidden/INVITE from 192.168.13.251:5062
06/21/2018 10:12:36 PM - Call to T:Line:10000>>0554216310@[Dev:sip:[email protected]:5062] from L:129.1[Extn:2001] failed, cause: Cause: 403 Forbidden/INVITE from 192.168.13.251:5062
06/21/2018 10:12:36 PM - [CM503003]: Call(C:129): Call to <sip:[email protected]:5062> has failed; Cause: 403 Forbidden/INVITE from 192.168.13.251:5062
06/21/2018 10:07:52 PM - Call to T:Line:10000>>0554216310@[Dev:sip:[email protected]:5062] from L:128.1[Extn:2001] failed, cause: Cause: 403 Forbidden/INVITE from 192.168.13.251:5062
06/21/2018 10:07:52 PM - [CM503003]: Call(C:128): Call to <sip:[email protected]:5062> has failed; Cause: 403 Forbidden/INVITE from 192.168.13.251:5062
06/21/2018 10:04:45 PM - Call to T:Line:10000>>0554216310@[Dev:sip:[email protected]:5062] from L:127.1[Extn:2001] failed, cause: Cause: 403 Forbidden/INVITE from 192.168.13.251:5062
06/21/2018 10:04:45 PM - [CM503003]: Call(C:127): Call to <sip:[email protected]:5062> has failed; Cause: 403 Forbidden/INVITE from 192.168.13.251:5062
06/21/2018 10:04:28 PM - Call to T:Line:10000>>0554216310@[Dev:sip:[email protected]:5062] from L:126.1[Extn:2001] failed, cause: Cause: 403 Forbidden/INVITE from 192.168.13.251:5062
06/21/2018 10:04:28 PM - [CM503003]: Call(C:126): Call to <sip:[email protected]:5062> has failed; Cause: 403 Forbidden/INVITE from 192.168.13.251:5062
06/21/2018 10:04:09 PM - Call to T:Line:10000>>0554216310@[Dev:sip:[email protected]:5062] from L:125.1[Extn:2001] failed, cause: Cause: 403 Forbidden/INVITE from 192.168.13.251:5062
06/21/2018 10:04:09 PM - [CM503003]: Call(C:125): Call to <sip:[email protected]:5062> has failed; Cause: 403 Forbidden/INVITE from 192.168.13.251:5062
06/21/2018 10:03:52 PM - Call to T:Line:10000>>0554216310@[Dev:sip:[email protected]:5062] from L:124.1[Extn:2001] failed, cause: Cause: 403 Forbidden/INVITE from 192.168.13.251:5062
06/21/2018 10:03:52 PM - [CM503003]: Call(C:124): Call to <sip:[email protected]:5062> has failed; Cause: 403 Forbidden/INVITE from 192.168.13.251:5062
06/21/2018 9:46:49 PM - Call to T:Line:10000>>0554216310@[Dev:sip:[email protected]:5062] from L:113.1[Extn:2001] failed, cause: Cause: 503 Service Unavailable/INVITE from 192.168.13.251:5062
06/21/2018 9:46:49 PM - [CM503003]: Call(C:113): Call to <sip:[email protected]:5062> has failed; Cause: 503 Service Unavailable/INVITE from 192.168.13.251:5062
06/21/2018 9:46:38 PM - Call to T:Line:10000>>0554216310@[Dev:sip:[email protected]:5062] from L:112.1[Extn:2001] failed, cause: Cause: 503 Service Unavailable/INVITE from 192.168.13.251:5062
06/21/2018 9:46:38 PM - [CM503003]: Call(C:112): Call to <sip:[email protected]:5062> has failed; Cause: 503 Service Unavailable/INVITE from 192.168.13.251:5062
06/21/2018 9:46:23 PM - Call to T:Line:10000>>0554216310@[Dev:sip:[email protected]:5062] from L:111.1[Extn:2001] failed, cause: Cause: 503 Service Unavailable/INVITE from 192.168.13.251:5062
06/21/2018 9:46:23 PM - [CM503003]: Call(C:111): Call to <sip:[email protected]:5062> has failed; Cause: 503 Service Unavailable/INVITE from 192.168.13.251:5062
06/21/2018 9:46:13 PM - Call to T:Line:10000>>043285071@[Dev:sip:[email protected]:5062] from L:110.1[Extn:2001] failed, cause: Cause: 503 Service Unavailable/INVITE from 192.168.13.251:5062
06/21/2018 9:46:13 PM - [CM503003]: Call(C:110): Call to <sip:[email protected]:5062> has failed; Cause: 503 Service Unavailable/INVITE from 192.168.13.251:5062
06/21/2018 9:42:51 PM - Call to T:Line:10000>>0554216310@[Dev:sip:[email protected]:5062] from L:109.1[Extn:2001] failed, cause: Cause: 503 Service Unavailable/INVITE from 192.168.13.251:5062
06/21/2018 9:42:51 PM - [CM503003]: Call(C:109): Call to <sip:[email protected]:5062> has failed; Cause: 503 Service Unavailable/INVITE from 192.168.13.251:5062
 
First off, all of the (3) dialplans you have entered are wrong. The field PSTN Default Caller DP determines which one incoming calls will use. Use 8 (or something other than 1), then DP 1, and make DP 8, (S0<:10000>). (that's a zero after the S). Change all other DPs back to the default of (xx.)
You may have been getting the outbound failures as DP 1 is selected as a default on outbound calls and you had modified it.

Under PSTN to VoIP gateway/ PSTN to ring thru line 1, change to NO

Under Subscriber Information, change the Display Name to a name, not a number. I recall that (using a number) having an affect on calls. Once you get the 3102 working, change it back and see if it still works.

What is the IP of the 3CX server? I see 192.168.13.133 and 192.168.13.134 show in the logs and the device, which is it?

Check the Info tab of the 3103 to see that the PSTN line is seen as idle (available).

At this point, you are not using Line 1, so the settings are irrelevant.
 
Thanks, have made all the changes. Just need to wrangle the receptionist over there now.
 
If you continue to have any issues, let me know.
 
Status
Not open for further replies.

Getting Started - Admin

Latest Posts

Members Online Now

Forum statistics

Threads
141,626
Messages
748,904
Members
144,739
Latest member
Ghisl1
Get 3CX - Absolutely Free!

Link up your team and customers Phone System Live Chat Video Conferencing

Hosted or Self-managed. Up to 10 users free forever. No credit card. Try risk free.

3CX
A 3CX Account with that email already exists. You will be redirected to the Customer Portal to sign in or reset your password if you've forgotten it.