Isn't there a change required on the Voip.ms end as well?  I can't imagine
you change one end to static, and not the other end, and I believe I've seen
that option on their site as well.  I didn't see that in your step by step
here, maybe you left that out of your instructions here, or is it possible
you are missing that step?

 

From: [email protected]
[mailto:[email protected]] On Behalf Of Michael
Scheidell
Sent: Thursday, March 03, 2011 1:05 AM
To: Joegen Baclor
Cc: Discussion list for users of sipXecs software
Subject: Re: [sipx-users] doesn't work tony , Re: Q About port 5060 trunking
support on 4.4

 

its all pretty easy to reproduce.  just set up sipx 4.4.0, a voip.ms
account. set voip.ms to ip based authentication. uncheck 'register on init'
on sipx on its account, restart what it wants started.  bang.  broken.
doesn't work.  you and tony say it will work, but has anyone actually tried
this?  

for me, its not that easy, I have to wait till 7 pm when no one is using the
phones, and switch over to 4.4.0.

voip.ms uses port 5060 for ip based authentication.

sorry if being short, but this is the same thing, with the same results,
that have not changed.  I can point to emails going back to april 2010.
nothing has changed.  If I can't get port 5060 ip based authentication to
work I'll be forced to buy something.  Iv never bee shy is saying I would
pay to have this work, and, no, its not with paying for a $6000 SBC, when I
can get a full commercial product for not that much more.
people tell me if i want port 5060 and not port 5080, its as simple as a
port nat/reditect on a firewall.  I tried that also.  doen't work.

BUT IF I PUT UP A SIMPLE FREESWITCH, OFF THE SHELF, ip based authentication
from voip.ms works.  inbound, outbound, hair pinned calls, transfers, caller
id, audio, touch tones on AA, everything.   its not me, its not my (pfsense
firewall), its that no one has actually tested this.

if you have gotten this to work, (ip based authentication on voip.ms),
please share with the world the itsp account settings.

user/auth is different.  with user/auth, sipx will call out, and tell the
itsp what port to use.  with ip based, the ports are fixed.

On 3/3/11 12:12 AM, Joegen Baclor wrote: 

If you think this is not working, it benefit all of us if you can share the
whats happening in signalling by getting a sipxviewr snapshot or by
producing a packet capture we could analyze before painstakingly resorting
to reading logs between proxy and sipxbridge.

 

-- 
Michael Scheidell, CTO
o: 561-999-5000
d: 561-948-2259
ISN: 1259*1300
> | SECNAP Network Security Corporation 

.        Certified SNORT Integrator

.        2008-9 Hot Company Award Winner, World Executive Alliance

.        Five-Star Partner Program 2009, VARBusiness

.        Best in Email Security,2010: Network Products Guide

.        King of Spam Filters, SC Magazine 2008

 

  _____  

This email has been scanned and certified safe by SpammerTrapR. 
For Information please see http://www.secnap.com/products/spammertrap/

  _____  

 

_______________________________________________
sipx-users mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users/

Reply via email to