[liberty2]

Hello all...

We are having a little trouble with our SPA-2102 ...

Currently, it will allow the reception of calls, but users cannot place calls through it. When they attempt to place a call through the device, they receive a fast busy. On the server, the log indicates:

Code: Select all

14:19:04.207  Currently active calls [none]
14:18:58.131  [CM502001]: Source info: From: "Anonymous"<sip:anonymous@localhost>;tag=cc6b0cd3cba3d984o0<sip:13@192.168.1.4>
14:18:58.131  [CM503013]: Call(93): Incoming call rejected, caller is unknown; msg=SipReq:  INVITE 13@192.168.1.4 tid=-3fa8dbd3 cseq=INVITE contact=20@192.168.1.120:5060 / 102 from(wire)
14:18:58.130  [CM500002]: Info on incoming INVITE:
  INVITE sip:13@192.168.1.4 SIP/2.0
  Via: SIP/2.0/UDP 192.168.1.120:5060;branch=z9hG4bK-3fa8dbd3
  Max-Forwards: 70
  Contact: "Anonymous"<sip:20@192.168.1.120:5060>
  To: <sip:13@192.168.1.4>
  From: "Anonymous"<sip:anonymous@localhost>;tag=cc6b0cd3cba3d984o0
  Call-ID: b13e5e3f-4c64d708@localhost
  CSeq: 102 INVITE
  Expires: 240
  Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER
  Proxy-Authorization: Digest username="20",realm="3CXPhoneSystem",nonce="414d535c051fc32203:0e37aee0412444cc209f8185329fe1c7",uri="sip:13@192.168.1.4",algorithm=MD5,response="87d7d60b03c186fb67d8449e0c9f2f6e"
  Supported: x-sipura
  User-Agent: Linksys/SPA2102-3.3.6
  Content-Length: 0
  Remote-Party-ID: 20 <sip:20@192.168.1.4>;screen=yes;privacy=full;party=calling
 
14:18:58.004  [CM500002]: Unidentified incoming call. Review INVITE and adjust source identification:
  INVITE sip:13@192.168.1.4 SIP/2.0
  Via: SIP/2.0/UDP 192.168.1.120:5060;branch=z9hG4bK-1740fb4f
  Max-Forwards: 70
  Contact: "Anonymous"<sip:20@192.168.1.120:5060>
  To: <sip:13@192.168.1.4>
  From: "Anonymous"<sip:anonymous@localhost>;tag=cc6b0cd3cba3d984o0
  Call-ID: b13e5e3f-4c64d708@localhost
  CSeq: 101 INVITE
  Expires: 240
  Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER
  Supported: x-sipura
  User-Agent: Linksys/SPA2102-3.3.6
  Content-Length: 0
  Remote-Party-ID: 20 <sip:20@192.168.1.4>;screen=yes;privacy=full;party=calling

As I said, the device does register and can receive calls.

[leejor]

Without looking over the settings in the 2102, I'm not sure if this is a an internal dialplan issue (although the calls are making it to 3CX) or a misconfiguration in the 2102.
Was this ATA used on another system? Did you do a factory reset before using? There are only a few settings that are required to get basic service working.... user (the Ext number), password and the sip server (3CX IP). (besides a dialplan that allows your calls to go out).
Did you manually provision this?

[liberty2]

This device was used on another 3CX system for a brief time and worked perfectly. However, it has never worked with this 3CX system. What concerns me is the line:

Code: Select all

14:18:58.131  [CM503013]: Call(93): Incoming call rejected, caller is unknown; msg=SipReq:  INVITE 13@192.168.1.4 tid=-3fa8dbd3 cseq=INVITE contact=20@192.168.1.120:5060 / 102 from(wire)

I have verified that the user ID / extension and password are both correct. In fact, the device does register and receive calls.

Here are screen shots from the configuration:

Capture.PNG (45.31 KiB) Viewed 274 times

Capture2.PNG (47.08 KiB) Viewed 274 times

Capture3.PNG (51.95 KiB) Viewed 274 times

[SY]

This device was used on another 3CX system for a brief time and worked perfectly.

Personally, I don't believe because of

Code: Select all

 Contact: "Anonymous"<sip:20@192.168.1.120:5060>
  To: <sip:13@192.168.1.4>
  From: "Anonymous"<sip:anonymous@localhost>;tag=cc6b0cd3cba3d984o0

...

[leejor]

If you haven't done so, do a factory reset. There may be something left in from the previous installation that is causing the problem. Then, manually datafill only the basic settings.

The 3CX site used to have a manual configuration section on the Linksys ATA devices, this is about as close as it gets now.

http://www.3cx.com/sip-phones/cisco-SPA50XG.html

Some of the fields are the same.

[leejor]

I seem to recall something about not making the display name the same as the user ID.

It looks like you've left the default dialplan in place, if you haven't (the last part is cut off) you may want to revise it to accommodate your two digit extensions.

[eagle2]

At least the dialplan is fake. Do a factory reset and apply 3CX automatic provisioning or follow manual configuration guidelines. We have installed over a thousand pcs. and never had any problems with SPA2102. It is probably the best VoIP ATA in the market for the past 5 years.

Regards