Belkin VoIP modem known issue
-
- Exetel Staff
- Posts: 424
- Joined: Fri Jan 28, 2005 5:10 pm
- Contact:
The problem is with the SIP negotiation with the Belkin units, there is nothing we can change on our switch.
We are sending the right invite but the unit does not respond.
You will need to get in touch with Belkin, we are more than happy to liaise with them for a solution but the problem is not on our end.
It works fine with every other unit.
If someone can provide me with remote access to a unit i am more than happy to check the settings and investigate further.
We are sending the right invite but the unit does not respond.
You will need to get in touch with Belkin, we are more than happy to liaise with them for a solution but the problem is not on our end.
It works fine with every other unit.
If someone can provide me with remote access to a unit i am more than happy to check the settings and investigate further.
Re: Belkin VoIP modem known issue
Um... why hasn't there been another post to this thread in two months? Was there a resolution to this?
Re: Belkin VoIP modem known issue
Great. I've just churned from Internode ( previously iinet ) with this exact modem, and now I find that there still may be a problem. I also ask, has this been resolved...?
-
- Posts: 1
- Joined: Fri Aug 01, 2008 8:31 pm
- Location: Brisbane
Re: Belkin VoIP modem known issue
I am in the same boat and it appears that there are many others! Can someone from exetel please investigate and resolve this with Belkin (the customer as middle man does not seem to be working and we would appreciate your help)?
I am happy to provide settings etc for background info or allow remote access (although I wouldn't know how to do this and would need instruction).
I am happy to provide settings etc for background info or allow remote access (although I wouldn't know how to do this and would need instruction).
Re: Belkin VoIP modem known issue
I've asked the Exetel VOIP experts to have another look, although having re-acquainted myself with the thread I'm a bit doubtful that there is anything further Exetel can do.
Gidget
Gidget
Log a fault ticket here
or call Exetel VOIP numbers (02) 8030 1000 or 1300 788 141 (log faults 24x7)
Exetel Support Portal
or call Exetel VOIP numbers (02) 8030 1000 or 1300 788 141 (log faults 24x7)
Exetel Support Portal
Re: Belkin VoIP modem known issue
I wasn't contacted about remoting into my modem, I guess that doesn't mean it wasn't done using another customers modem though.
The offer still stands of course (and I can also of course now obtain a DID free of charge and will most likely do this very soon).
The offer still stands of course (and I can also of course now obtain a DID free of charge and will most likely do this very soon).
Re: Belkin VoIP modem known issue
I just tried that with another customer tonight, there's no ability in the modem configuration to perform SIP debugging.
SIP debugging would allow to see what is happening to the INVITE packets the modem receives, it logs the INVITES it 'sends', and calls from Exetel VoIP do successfully connect, but even the INVITE packets for these are not logged, but the call is successfully established.
Belkin modems don't offer the debug option - at least, the iiNet rebadged firmware does not offer a sip debugging option, despite the other features offered.
The logs don't show enough information about the VoIP calls in to identify why they don't accept incoming calls, a snapshot below:
08/04/2008 17:58:32 INVITE[028090XXXX call 0299271000]: 200 OK for CSeq 15
08/04/2008 17:58:29 INVITE[028090XXXX call 0299271000]: 183 Session Progress for CSeq 15
08/04/2008 17:58:28 INVITE[028090XXXX call 0299271000]: 100 trying -- your call is important to us for CSeq 15
08/04/2008 17:58:28 INVITE[028090XXXX call 0299271000]: 407 Proxy Authentication Required for CSeq 14
--
The above is an outgoing call, as is seen, the log demonstrates the call, and the packet received, and even the CSeq (for those familiar with Asterisk, the packet sequence).
Incoming calls don't appear to log any information in the security log at all, even with a successful call in from Exetel VoIP (yes, PSTN calls were still failing), there is nothing in the log, the Received call counter is incremented, but that isn't very helpful.
It'd be sweet if they had a debug option, and allowed sending the packets to a syslog server so that they could be reviewed, and compared between an Exetel VoIP on net call, and a PSTN -> DID call (the PSTN -> DID call is not working on iiNet branded Belkin modems).
SIP debugging would allow to see what is happening to the INVITE packets the modem receives, it logs the INVITES it 'sends', and calls from Exetel VoIP do successfully connect, but even the INVITE packets for these are not logged, but the call is successfully established.
Belkin modems don't offer the debug option - at least, the iiNet rebadged firmware does not offer a sip debugging option, despite the other features offered.
The logs don't show enough information about the VoIP calls in to identify why they don't accept incoming calls, a snapshot below:
08/04/2008 17:58:32 INVITE[028090XXXX call 0299271000]: 200 OK for CSeq 15
08/04/2008 17:58:29 INVITE[028090XXXX call 0299271000]: 183 Session Progress for CSeq 15
08/04/2008 17:58:28 INVITE[028090XXXX call 0299271000]: 100 trying -- your call is important to us for CSeq 15
08/04/2008 17:58:28 INVITE[028090XXXX call 0299271000]: 407 Proxy Authentication Required for CSeq 14
--
The above is an outgoing call, as is seen, the log demonstrates the call, and the packet received, and even the CSeq (for those familiar with Asterisk, the packet sequence).
Incoming calls don't appear to log any information in the security log at all, even with a successful call in from Exetel VoIP (yes, PSTN calls were still failing), there is nothing in the log, the Received call counter is incremented, but that isn't very helpful.
It'd be sweet if they had a debug option, and allowed sending the packets to a syslog server so that they could be reviewed, and compared between an Exetel VoIP on net call, and a PSTN -> DID call (the PSTN -> DID call is not working on iiNet branded Belkin modems).
Re: Belkin VoIP modem known issue
Well that's not the best news... but thanks for looking into it 

Re: Belkin VoIP modem known issue
I'm having exactly the same issue connecting with a Belkin F1PI-241EGau.
I've contacted Belkin 3rd line support, who have given a contact number for Exetel to call.
I've spoken to Jason M, who will pass on the details to the VOIP specialists at Exetel.
Here's hoping they can reach a resolution...I really don't want to buy another modem..if nothing else also this waste is not very carbon friendly!
I've contacted Belkin 3rd line support, who have given a contact number for Exetel to call.
I've spoken to Jason M, who will pass on the details to the VOIP specialists at Exetel.
Here's hoping they can reach a resolution...I really don't want to buy another modem..if nothing else also this waste is not very carbon friendly!

Re: Belkin VoIP modem known issue
A quick update on this, after a fair bit of heartache with Exetel, iiNet and Belkin, the situation is this:
Exetel: Do not have the resources for a VOIP Engineer to investigate (and to be fair, they've already been very specific)
Belkin 3rd Level Support: This is an iiNET branded modem and has customised VOIP settings for the iiNET network. iiNET would not be happy for us to 'fix it'
iiNET Supervisor: This unit is not hard coded and will work with other ISPs. Belkin should give the same level of support as to non iiNet customers.
Final line from Belkin: This is the only VOIP IAD they make, and whilst it is not hardcoded, they will not develop firmware updates to make it work with other providers...Sounds like semantics to me.
I've had enough..I'm going to have to ditch this proprietary modem, which really sucks, as I sold my NB9W when it didn't work with iiNET VOIP and I had to by the Belkin model..Hopefully I can pass mine on to another iiNet customer and get a preloved NB9W!
Exetel: Do not have the resources for a VOIP Engineer to investigate (and to be fair, they've already been very specific)
Belkin 3rd Level Support: This is an iiNET branded modem and has customised VOIP settings for the iiNET network. iiNET would not be happy for us to 'fix it'
iiNET Supervisor: This unit is not hard coded and will work with other ISPs. Belkin should give the same level of support as to non iiNet customers.
Final line from Belkin: This is the only VOIP IAD they make, and whilst it is not hardcoded, they will not develop firmware updates to make it work with other providers...Sounds like semantics to me.
I've had enough..I'm going to have to ditch this proprietary modem, which really sucks, as I sold my NB9W when it didn't work with iiNET VOIP and I had to by the Belkin model..Hopefully I can pass mine on to another iiNet customer and get a preloved NB9W!