iTalk SIP trunks on Asterisk stop working

Forums › VoIP › iTalk SIP trunks on Asterisk stop working - other SIP trunks OK

1 | 2 | 3 | 4 | 5

3344 posts

Uber Geek

Trusted

Vocus

#862010 19-Jul-2013 09:50

paul21019: Going by the replies it looks as though I am not alone, I assume "snap here" means you have the same problem ( or does it?) and the Telstra Clear / Vodafone comment refers to Italks wholesaler.

OK so where to from here? I am a small business and my DR copes with this, however if there is no answer I need to goto a provider that works. I have been with Italk for 10 years and I have a fixed IP as well, I spend about $150 a month, so if Italk wont talk to me and my device that did work for the last three years ( I was a copper customer before that, now I am Naked DSL) is unsupported... great .

I am assuming that we need a genius to work out new peer details ( which is not me) or I move - what are my options ? Is Orcon going to work for me? Since UbergeekNZ has been the most helpful, I may as wwell put my money in that direction and support his employer...

Thoughts Please?

Paul

If you get a business grade connection from Orcon, we can provide a SIP trunk service over it, which will support Asterisk.

However there are other providers who will give you a SIP service on its own (WxC, 2Talk spring to mind) that can support it too.

carrots98

17 posts

Geek

#862062 19-Jul-2013 11:33

Just been on the phone to slingshot (15 minutes to answer, 30 minutes of troubleshooting). They tried on a softphone and ATA and can get it to work (which I advised them would be the case due to my own testing).

They refuse to escalate as their tier 2 helped them do the testing which "works"

The calltaker advised that he had a couple of other calls this morning with the same issue (Cisco Call Managers, Asterisk etc) but that is a "coincidence" and doesn't constitute an issue on their side.

Their advice was to reboot the asterisk server (which has been done and I had told them such) and to move to supported equipment.

Having supported SIP services myself in the UK it's frustrating getting a helpdesk who don't understand the technology and aren't interested in getting the right people to investigate an issue... even if it could be user error.

Also interesting to see that they refused to change my SIP trunk passwords as it would cause issues on their side. A major security flaw in their design. I'm going to ring back later and advise that my password has been "compromised" and demand they provide a solution otherwise they will be responsible for all calls on my account under toll fraud.

After 5 years it's time for me to consider another provider...

maverick

3594 posts

Uber Geek

Trusted

WorldxChange

#862141 19-Jul-2013 14:13

At home sick and saw this post, downloaded the trace and its pretty simple actually,

The reason why one works and the other does not is that the xlite client is sending auth info in the invite message after being challenged proxy auth required (SIP 407) ,

In the one that fails the italk server is sending a forbidden (SIP 403) straight away to an invite with no auth details instead of a proxy auth required , you will also see that they are sending to 2 different IP addresses the one that works is 203.184.16.2 the one the rejects with the 403 is 203.184.16.89 so one would suggest one server has a problem as you should be expecting to get a SIP 407 to the invite not a 403,

This would not appear to be a user problem but a italk problem. should have been pretty simple to check I would have thought.

Yes I am a employee of WxC (My Profile) ... but I do have my own opinions as well

https://www.facebook.com/wxccommunications

paul21019

19 posts

Geek

#862159 19-Jul-2013 14:50

Maverick,

I follow your logic, this is getting too deep for me, but its great you guys have taken an interest, as there are many of us in the same boat - it there anything we can do to get our asterisk to work?

When you say simple to fix - can we as users do anything

I believe Italk monitors the geekzone and perhaps whomever you are can you provide a solution?

PDE

maverick

3594 posts

Uber Geek

Trusted

WorldxChange

#862188 19-Jul-2013 15:22

No this is not your issue I believe, this appears to be a italk issue as it appears one of their servers is not behaving as it should IMHO , send the trace to them and tell them its got nothing to do with supported devices but possibly one of their servers at the .89 address is not working as it should

Yes I am a employee of WxC (My Profile) ... but I do have my own opinions as well

https://www.facebook.com/wxccommunications

maverick

3594 posts

Uber Geek

Trusted

WorldxChange

#862190 19-Jul-2013 15:23

paul21019: Maverick,

I follow your logic, this is getting too deep for me, but its great you guys have taken an interest, as there are many of us in the same boat - it there anything we can do to get our asterisk to work?

When you say simple to fix - can we as users do anything

I believe Italk monitors the geekzone and perhaps whomever you are can you provide a solution?

PDE

Possibly set the trunk to use the .16.2 address and see how you go

Btw when I said simple , I meant simple to diagnose with the trace if you know what your looking for :)

Yes I am a employee of WxC (My Profile) ... but I do have my own opinions as well

https://www.facebook.com/wxccommunications

rabsoft

20 posts

Geek

#862231 19-Jul-2013 16:12

Just did a test on my asterisk box

Changed
host=akl.italk.co.nz
to
host=203.184.16.2
also changed the Register String to the IP

Now I am able to dial out and in without a problem

Samsung

Shop now on Samsung phones, tablets, TVs and more (affiliate link).

sbaird

81 posts

Master Geek

#862246 19-Jul-2013 16:28

I have set
fromdomain=hlz.italk.co.nz
Previously it was not set,
Its working now
Can someone else try setting fromdomain to the same as they have host set, IE host=hlz.italk.co.nz, host=wlg.italk.co.nz

jnawk

176 posts

Master Geek

#862274 19-Jul-2013 16:40

From what I've seen here, there's no doubt Slingshot have made changes. And then cowardly as ever, they hide behind the "Asterisk isn't supported" gag.

What sbaird did not mention is he & I share an asterisk instance. My trunk had fromdomain set (and I've not changed the config for years), and his did not (and his config has been likewise stable).

Isn't it wonderful how organisations hide behind the "we don't support X" position, even when they are the cause of the problem? (We made no change, so logic dictates they must have, since all other factors are constant). In this instance, I solved the problem (without their support) by harmonising the configs (ie, port bits of my config that weren't present in the other config).

I often, when presented with the "we don't support X" position try to tell the CSR that I don't want support for my hardware/software, but that I want support for their product. Of course, I'm not in the habit of randomly poking about in my production config. That doesn't stop them from trying to fob off responsibility. Have you tried turning it off and on again?

Surely an admission "we changed something", or even "we changed X" would have been nice. Especially as there have been at least 3 instances of configs that formerly worked all spontaneously failing at the same time. Or am I being unreasonable?

rabsoft

20 posts

Geek

#862275 19-Jul-2013 16:42

I just added the fromdomain

host=akl.italk.co.nz
fromdomain=akl.italk.co.nz

649xxxxxxx:Password@akl.italk.co.nz/649xxxxxxx

It seems to work fine with the fromdomain setting, if I remove it I get the forbidden error message back

maverick

3594 posts

Uber Geek

Trusted

WorldxChange

#862282 19-Jul-2013 16:53

rabsoft: Just did a test on my asterisk box

Changed
host=akl.italk.co.nz
to
host=203.184.16.2
also changed the Register String to the IP

Now I am able to dial out and in without a problem

So your all good then, so it also appears to be as I suggested a proxy on the italk service is not working correctly.

Yes I am a employee of WxC (My Profile) ... but I do have my own opinions as well

https://www.facebook.com/wxccommunications

carrots98

17 posts

Geek

#862299 19-Jul-2013 18:01

Working now too using the fromdomain option on each trunk. Thanks for everybody's help.

Interesting to see that even though we are sending to 203.184.16.89 iTalk pbx is responding with 203.184.16.2 in the Call-ID part of the SIP header.

BarryP

5 posts

Wannabe Geek

#862866 21-Jul-2013 01:03

Many Thanks !!
This had Been Driving me Nuts For Days .
Calls In & Out are all working now , But Still have Forbidden Being Returned On OPTIONS

Any one figured a way to solve That ?

maverick

3594 posts

Uber Geek

Trusted

WorldxChange

#862878 21-Jul-2013 06:49

Glad we could help italk out :)

All it means is that the "Options" method is not supported as a keep alive on the the proxy, actually has no real impact.

Yes I am a employee of WxC (My Profile) ... but I do have my own opinions as well

https://www.facebook.com/wxccommunications

maverick

3594 posts

Uber Geek

Trusted

WorldxChange

#862879 21-Jul-2013 06:49

Glad we could help italk out :)

All it means is that the "Options" method is not supported as a keep alive on the the proxy, actually has no real impact.

Yes I am a employee of WxC (My Profile) ... but I do have my own opinions as well

https://www.facebook.com/wxccommunications

1 | 2 | 3 | 4 | 5