ATA SPA122 - In-coming call problem

[ngon.bui]

Hi there,

I was previously with Distributel Inc. and 3Web.

I just switch-over using cable internet and VOIP with Acanac (about <1 month)

The VOIP was "porting" over to Acanac first, using Cisco ATA SPA122 (new purchase), everything was working as expected (cable internet still with Distributel for few days later)

When Cable Internet switched over to Acanac.  My VOIP started acting-up!!!

1. Calling out (out-bound): no prolem at all
   • to non-Acanac phone number=OK
   • to Acanac phone number=OK
2. In-coming call (in-bound): Problem!!!
   • from non-Acanac phone number (Rogers, Bell, cell) = PROBLEM: (a) I didn't hear any ring - (b) callers heard busy tones, and then dropped - (c) the caller NOT redirect to vmail
   • from Acanac phone number = OK (phone ring, vmail, talking)

Took my ATA to my neighbor who also using services with Acanac as same as me. Also borrowed the ATA from neighbor and test in my place. 

Test result still same on my ATA @ his or my place/network.  I didn't change the configure on each ATA - kept them as-is

My internet is function as normal.  My ATA connecting with or without router still having same issue (not blocking ports)

I personally don't think my ATA device broken, please advice.  My device also has been factory reset but didn't help on the issue

the firware already update.  Comparing the ATA configure with neighbor, everything matching except personal info/password.  My though would it be (??) Acanac voice system doesn't allow any "outside" calls to establish with my phone/number .. routing issue within VOIP system??

I am @ the 4th-week of no-phone service.  Acanac support is not very helpful at alll.   I am looking for an advice from expert, any suggestion is very appreciated.

Regards,

[Dan Lukes]

You should turn on debug on device. You should catch SIP packets as well.

Debug and syslog Messages from SPA1x2 and SPA232D ATA (Analog Telephone Adapters)

Installing and Using Wireshark for Capturing Network Traffic

It's very hard to analyze such kind of problem, especially with no support from your telco operator, so you should collect as much informations as you can.

Misconfiguration of Acanac voice system sound plausible.

[ngon.bui]

I got a respond from the support, any suggestion?

Posted on 21 Jan 2014 09:36 AM Hello, We've done another check on your line and for the most part everything  looks correct. I am getting an error when checking your IP address: "[Jan 18 11:47:04] NOTICE[13945] rtp.c: Unknown RTP codec 100 received from 'xxx.xxx.xxx.xxx'" This error usually occurs when there is a configuration issue with the  device, possibly the codec initiated is the wrong one for your SIP.  Please ensure the settings of your ATA is correct and re-attempt. Best regards, Acanac Inc.

Ngon Bui

Posted on 21 Jan 2014 12:36 PM the SIP was factory default,  what are the codec vs field that I should configure?  Any additional  instruction is very appreciated. Thanks,

[Dan Lukes]

By the way:

1. your device should NOT be accesible from public (no port of them) not counting the access from SIP proxy of your telco. Anyone can reboot your device now. Change configuration of your firewall
2. upgrade your device to latest firmware, you have 1.3.3 here now
3. line 1 registration is failing. I know no Acanac requirements, but in most cases the registration to SIP proxy is not optional

[Dan Lukes]

There are pile of codecs on the world. Those supported by a device are announced during dialog. Of course, some of them may be unknown to oposite side. They should be ignored. Call is still possible, as long as there is an codec known to both sides.

Information that a particular codec from is not unknown to recipient is not so helpfull alone. I assume there is a common codec that can be used. Acanac seems to be using G.711 uLaw so verify you didn't disabled it in your configuration.

Please catch the SIP dialog packets as I suggested before. It's not possible to give you a valuable advice without it. There are so many possible reason for symptoms you described.

[ngon.bui]

Understood,

I have wireshark and will have that setup to test out.  I will provide more info after get package capture.  I would assume (PC & ATA SPA122) connecting directly to hub/switch (non-managed) => Router => Cable modem would suitable to capture traffic as your instruction

here is more update from Acanac support, not sure why they asked me to use uLaw but sent me the snapshot of G726a :-(  !!!

Hmm, I thought Acanac VOIP support able to identify the issue but still hopeless!!!

------------------------------------------------------------

Christian Bernard

Posted on 21 Jan 2014 02:31 PM

Hello,

The  codec we use is uLaw (g.711). I've included a picture to assist you  with finding that field on your device. Ensure the codec is set to uLaw.

best regards,

Acanac Inc.

linksys-configuration-4.gif (10.01KB) -

---------------------------------------------

Ngon Bui

Posted on 21 Jan 2014 03:08 PM

thanks for the info,

My  existing setting is (Audio Configuration / Preferred Codec: G711u, I  believe that is uLaw (G711u). Your attachment is showing the Preferred  Codec: G729a)

Please confirm the uLaw codec is G711u (NOT G729a). I will keep my existing settings until receive your confirmation.

thanks,

[Dan Lukes]

According Acanac pages, both G.711u (a.k.a. uLaw or PCMU) and G.729a are supported by Acanac. You should prefer G.711u for now. You may decide to switch to G.729a later if you wish, but not now. There are some G.729a specific issues which may make current problems worse. So disable G.729a completelly (don't offer it even as less prefered codec).