[WXC/VFX] Setting up Asterisk for VFX - Device not registered to place calls?

Forums › One New Zealand (including Vodafone, WxC, Farmside) › [WXC/VFX] Setting up Asterisk for VFX - Device not registered to place calls?

DannoNZ

5 posts

Wannabe Geek

#18833 25-Jan-2008 14:04

Hi Guys,

I'm a little stumped here setting up my Asterisk to connect to VFX - I thought I'd done everything perfectly and it appeared to be all going nicely until I tried making a test call.

I get a recorded message (in a New Zealand accent) so I'm pretty sure it came from Xnet, saying:
The device you are using is not registered to place calls on the network, please contact your administrator for assistance."

Now I do have the register line in my sip.conf, and I've triple checked everything is as per the example (http://www.geekzone.co.nz/forums.asp?forumid=65&topicid=17174) but since I'm not too familiar with Asterisk I'm not really sure how to get appropriate logs or troubleshooting out of it... I tried watching the verbose messages on the output, but that's seemingly just saying that the VFX sip is answering the call, and my extension is being connected through to it - but no errors as to why I would be getting an unregistered message from Xnet...

I tried asking Xnet and they referred me back here, so it sounds like they think I've done something wrong rather than any issue at their end.

Any hints as to where to look for further troubleshooting/logs? :-)

Thanks in advance,

Dan

maverick

3594 posts

Uber Geek

Trusted

WorldxChange

#106732 25-Jan-2008 14:30

Can you PM me you VFX number please and I will take a look

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

#106736 25-Jan-2008 15:06

There is nothing from the number you PM me, can you send me your IP address I am guessing that you will probably have the wrong Number being sent, so I will need your IP. if you PM that as well it will help

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

#106739 25-Jan-2008 15:24

I went and found your IP, sorry we are not seeing anything at all from your IP address or phone number, the device is not registered and were not even seeing try to get to us, however in saying that that RVA does sound like on of ours, so a little confused hera at present.

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

https://www.facebook.com/wxccommunications

DannoNZ

5 posts

Wannabe Geek

#106765 25-Jan-2008 18:15

Just got home and put asterisk onto the ADSL and made some more test calls on my IP, but still getting the same message btw :-)

jedney

39 posts

Geek

#106767 25-Jan-2008 18:39

Slightly off topic, but I had my Asterisk working fine and then all of a sudden it started giving me a recorded announcement saying "You are not authorised to make this call, please contact your administrator" (or something similar), needless to say, when I phoned up it was a job to get past the customer support agent to speak to a techie (as soon as you mention Asterisk they near enough hang-up on you!), but I eventually did get to speak to a techie and they fixed it. They were always very polite but the emphasis is very much on proving it's not your problem before getting though to a techie - maybe a bit too hard if you get my drift XNet!? :-)

The thing that made it easier to diagnose my problem was that (at least on my system) all Asterisk voice prompts and errors are a womans voice - the one I was getting was a male voice. It made it easy to identify it was at least not a call routing/time condition issue on my server. It's something worth bearing in mind - but not sure its too much help in your case.

Good luck :-)

maverick

3594 posts

Uber Geek

Trusted

WorldxChange

#106769 25-Jan-2008 18:40

Hi Daniel,

As discussed, your Asterisk box is sending calls (invites) but it has not actually sent a register message, hence the reason for the RVA, you need to sned the register message and have the device registered before making calls.

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

https://www.facebook.com/wxccommunications

DannoNZ

5 posts

Wannabe Geek

#106772 25-Jan-2008 18:55

I've been having a little bit more of a look into this and I've figured out how to turn on debugging, and played with a few of the settings and this is what I'm seeing now:

Scheduling destruction of SIP dialog '469A1978-1DD2-11B2-AFD4-8F4E030A4018@192.168.177.1' in 32000 ms (Method: OPTIONS)

[Jan 25 18:47:14] NOTICE[39713]: chan_sip.c:8877 sip_reg_timeout: -- Registration for '9950?!#%@as.wxcnz.net' timed out, trying again (Attempt #88)

REGISTER 13 headers, 0 lines

Reliably Transmitting (no NAT) to 58.28.20.150:5060:

REGISTER sip:as.wxcnz.net SIP/2.0

Via: SIP/2.0/UDP 192.168.1.3:5060;branch=z9hG4bK40ccb09a;rport

Max-Forwards: 70

From: ;tag=as246c07c8

To:

Call-ID: 1baa2ab633ecc77748b5901c1aa76042@10.37.129.2

CSeq: 190 REGISTER

User-Agent: Asterisk PBX 1.6.0-beta1

Authorization: Digest username="**MYUSERNAMEHERE**", realm="xport.co.nz", algorithm=MD5, uri="sip:as.wxcnz.net", nonce="BroadWorksXfbubaexkTz9kh9eBW", response="6c381c0d7da9d4d8c9a77400c019f0c3", opaque="", qop=auth, cnonce="27b58a7e", nc=00000002

Expires: 120

Contact:

Event: registration

Content-Length: 0

---

<--- SIP read from UDP://58.28.20.150:5060 --->

SIP/2.0 401 Unauthorized

From: ;tag=as246c07c8

To:

Call-ID: 1baa2ab633ecc77748b5901c1aa76042@10.37.129.2

CSeq: 190 REGISTER

Via: SIP/2.0/UDP 192.168.1.3:5060;received=118.90.43.123;rport=5060;branch=z9hG4bK40ccb09a

WWW-Authenticate: DIGEST realm="xport.co.nz", nonce="BroadWorksXfbubauctTg622y1BW", algorithm=MD5, qop="auth"

Content-Length: 0

<------------->

--- (8 headers 0 lines) ---

Responding to challenge, registration to domain/host name as.wxcnz.net

REGISTER 13 headers, 0 lines

Reliably Transmitting (no NAT) to 58.28.20.150:5060:

REGISTER sip:as.wxcnz.net SIP/2.0

Via: SIP/2.0/UDP 192.168.1.3:5060;branch=z9hG4bK2a1e8f53;rport

Max-Forwards: 70

From: ;tag=as781f3cd5

To:

Call-ID: 1baa2ab633ecc77748b5901c1aa76042@10.37.129.2

CSeq: 191 REGISTER

User-Agent: Asterisk PBX 1.6.0-beta1

Authorization: Digest username="**MYUSERNAMEHERE**", realm="xport.co.nz", algorithm=MD5, uri="sip:as.wxcnz.net", nonce="BroadWorksXfbubauctTg622y1BW", response="35e4f02b94bd748681ede569a62a54d7", opaque="", qop=auth, cnonce="73fde86f", nc=00000001

Expires: 120

Contact:

Event: registration

Content-Length: 0

Any further hints from anybody...?

Edit: removed phone number, Internal IP not really very helpful to anybody...

Equinox IT

Cloud spending continues to surge globally, but most organisations haven’t made the changes necessary to maximise the value and cost-efficiency benefits of their cloud investments. Download the whitepaper From Overspend to Advantage now.

maverick

3594 posts

Uber Geek

Trusted

WorldxChange

#106777 25-Jan-2008 19:09

jedney: Slightly off topic, but I had my Asterisk working fine and then all of a sudden it started giving me a recorded announcement saying "You are not authorised to make this call, please contact your administrator" (or something similar), needless to say, when I phoned up it was a job to get past the customer support agent to speak to a techie (as soon as you mention Asterisk they near enough hang-up on you!), but I eventually did get to speak to a techie and they fixed it. They were always very polite but the emphasis is very much on proving it's not your problem before getting though to a techie - maybe a bit too hard if you get my drift XNet!? :-)

The thing that made it easier to diagnose my problem was that (at least on my system) all Asterisk voice prompts and errors are a womans voice - the one I was getting was a male voice. It made it easy to identify it was at least not a call routing/time condition issue on my server. It's something worth bearing in mind - but not sure its too much help in your case.

Good luck :-)

Actually this is starting to point to one of the reasons we were were reluctant to support Asterisk, there were a number of discussions as to why we locked configs and controlled all the devices, only supported Linksys etc. This is probably a good point, SIP is a very open and configurable standard, so is an Asterisk box first line support people will not be skilled up on it to many vraiables, When we deploy the locked down devices they generally register straight away with no issue the services just work. Now taking your example how would a first line support person know what you configured your box, and how much time would be taken to diagnose issues when you can control so many settings.

We are still evaulating if we will offer continuing support for Asterisk and one of the key issues is the impact on support channels for devices we have no control over, we explained right at the start and in the VV's done when the customer signs up that Asterisk is not supported by the helpdesk, yet it seems by your comments that we are now seeing people expecting direct support of Asterisk,

Now straight away the message you recieved was "you are not registered on the network", did you see the sip registration messages ? so what we are expecting is a bit of work done by Asterisk users as we have no control over your settings ad how you configure your box, we recommend that you place questions and issues here, so the more expert Technical people can assit so not to load up support on the help desk with what is almost always a config issue on the customers box itself, we are also expecting the Asterisk users to support themselves as that is what the platform users and user group push, Asterisk users support asterisk users.

But rest assured I am noting your comments and expectations / drift, I am also noting how much support is required by us for Asterisk and number of Astersik users on the network compared to the amount of support / number of users for locked down devices.

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

#106779 25-Jan-2008 19:11

Daniel,

Please remove all your phone number details and IP address details, this is not stuff you want to post on a public forum,

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

#106782 25-Jan-2008 19:17

Your trying now sending registers but details appear to be incorrect,

PM your details and I will take a look , the details recieved and your conf with those details

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

https://www.facebook.com/wxccommunications

jedney

39 posts

Geek

#106785 25-Jan-2008 19:47

Maverick,

Please don't misunderstand me, I'm not really moaning, as I said the front line person was very polite it was just difficult to get past them. It's just a bit frustrating to know the problem (in my case) is almost certainly at the XNet end and to not be able to get someone to help (as it was in my case).

I did say to the person who answered the call "I know you don't support Asterisk, I'm not asking you to diagnose my server or to assist me in any way with the setup at my end, but I believe this error is coming from your end. Could you please just check my account settings and VFX control panel settings." It took me (at a guess) 4-5 minutes to pursuade the front line guy to put me through, when he did the techie took 5 seconds to diagnose a "bazar" setting on my account which blocked all but 0800 calls from my line. It was an XNet fault which I wouldn't have been able to fix myself.

I can see in the context of this post you might have taken my comments as trying to get DannoNZ (or other people with problems) to force their way through on the phone when his problem is in fact a setup issue (which as you say isn't covered). This is not what my post was supposed to say. I was trying to make two completely different points:

1) You can use the gender of the voice to diagnose how far the call is getting without having to resort to debug command.
and
2) (As a seperate issue) I was suggesting that if a front line support person has told the customer that Asterisk isn't supported and the person is adament its not a problem at their end they should be willing to at least check the persons account to make sure there are no funny setting/locks in place. If there isn't then by all means hang-up on them! ;-)

I gather from the tone of your post I have touched on an area which is causing some grief, I hope post like mine are not making XNet rethink their policy on Asterisk, it really is a fantastic service for us "geeks" and something which we have all wanted (and NZ has neeeded) for number of years. Were exceptionally lucky to have this forum to share ideas and talk with people like yourself.

Thanks,
Jon.

P.S. Before I get flamed by 100+ angry Geeks for being the one responsible to getting the plug pulled on Asterisk - can we say "truce"? ;-)

P.P.S. Before those 100+ Geeks either flame me or start singing XNet's praises can we leave this thread for Danno so he can get his problem fixed and we'll hold any further input under a thread called "Lynch JEdney" or "Hoorah for XNet" (as applicable!).

DannoNZ

5 posts

Wannabe Geek

#106797 25-Jan-2008 20:39

For the future reference of anybody that stumbles across this, I'd made the silly mistake of having the register line in the wrong format.

Make sure it is:
register=VFXNumber:PASSWORD:USERID@as.wxcnz.net/VFXNumber

I had password and userid inverted ;-)

maverick

3594 posts

Uber Geek

Trusted

WorldxChange

#106799 25-Jan-2008 20:44

Nice reply and with a touch of humour as well , I like that

.

From your first post you said that it was registration issue which is one of the basics, not that you could only Dial 0800, basically your account was suspended, but your right I probably misread your post.

I tend to back up our support people as well as they have to support a lot of equipment and do a fantastic job in most cases. they will not always have the answers especailly with Asterisk as it is very difficult and time consuming when you don't know how a device is setup, however you are correct again there are some basic checks that can be done before we can hand it back to the custy.

Good comments though as I now understand where you were coming from, As for a touchy subject not really I think

more of a re inforcement I suppose that we are still evaulating what we are doing with Asterisk, so far it is working well once it sit up, but there are varying levels of users out there and the support required to get them going and it's impact is still being accessed, we have a lot of users now btw. so there would be a 100+ user coming after you if I shut it down as I would name you as the sole reason

.....kidding btw

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

https://www.facebook.com/wxccommunications

jedney

39 posts

Geek

#106809 25-Jan-2008 21:01

Glad there's no harm done. Thanks for taking the time to reply.

Have a good long weekend.