Vitelity is sending to 5060 -- when I asked about 5080 they said: "We could change it on our end but do not recommend this. In addition if we do you will be limited to 30 channels and this amount will not be able to be increased in the future."
30 channels should be more than adequate for the next year or so at this site anyway. I'm curious about the suggestion to use a sipxbridge instance (rather than an unmanaged gateway as was suggested yesterday) and choosing bandwidth.com instead of Vitelity as the template? thanks... On Jul 20, 2012, at 11:38 , Tony Graziano wrote: > Then you would have set this up using a template in sipx as a "trunk" and > choosing "bandwidth.com" as the template and changing the addresses to match > vitelity. I do not think it will work unless vitelity is sending the inbound > invite onport 5080, which I cannot see they are due to the limited > information you have provided. > > If the invites are coming from vitelity on port 5060, it WOULD act as an > unauthorized call. > > Change those two things. Use the bandwidth.com template and have vitelity > send to port 5080. > > On Fri, Jul 20, 2012 at 1:22 PM, Kurt Albershardt <[email protected]> wrote: > I'm seeing 407 (Proxy Authentication Required) returned to incoming invites > from Vitelity. We have a no-registration (IP authentication) relationship > with them so it's possible I've missed something in the setup that would > allow unauthenticated invites from their IP. > > > This is the response sent to sipxbridge: > > Time: 2012-07-20T16:48:16.097000Z > Frame: 4 sipxbridge.xml:354 > Source: 192.168.X.24:5060 > Dest: sipx.domain.com-sipXbridge > > SIP/2.0 407 Proxy Authentication Required > Record-Route: <sip:192.168.X.24:5060;lr;sipXecs-CallDest=LD;x-sipX-done> > From: "+15759565979" <sip:[email protected]>;tag=2014970589 > To: <sip:[email protected]>;tag=1R5cwk > Call-ID: [email protected] > CSeq: 102 INVITE > Via: SIP/2.0/TCP > 192.168.X.24:5090;branch=z9hG4bK11c84e5a79571525f8a761d6bcaf2a4c393639;sipxecs-id=3164ecee > Proxy-Authenticate: Digest > realm="sipx.domain.com",nonce="d98c3b153f9c64d522cd72f9a7c28fde50098bd0",qop="auth" > Server: sipXecs/4.4.0 sipXecs/sipXproxy (Linux) > Date: Fri, 20 Jul 2012 16:48:16 GMT > Content-Length: 0 > > ...which sends this to Vitelity: > > > Time: 2012-07-20T16:48:16.103000Z > Frame: 6 sipxbridge.xml:365 > Source: sipx.domain.com-sipXbridge > Dest: 66.241.X.X:5060 > > SIP/2.0 407 Proxy Authentication required > Via: SIP/2.0/UDP > 66.241.X.X:5060;branch=z9hG4bK17b48c37;rport=5060;received=66.241.X.X > From: "+15759565979" <sip:[email protected]>;tag=as4b214e18 > To: <sip:[email protected]:5060> > Call-ID: [email protected] > CSeq: 102 INVITE > Server: sipXecs/4.4.0 sipXecs/sipxbridge (Linux) > Supported: replaces > Record-Route: <sip:192.168.X.24:5060;lr;sipXecs-CallDest=LD;x-sipX-done> > Proxy-Authenticate: Digest > realm="sipx.domain.com",nonce="d98c3b153f9c64d522cd72f9a7c28fde50098bd0",qop="auth" > Date: Fri, 20 Jul 2012 16:48:16 GMT > Contact: <sip:70.57.247.39:5080> > Content-Length: 0 > > _______________________________________________ > sipx-users mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-users/ > > > > -- > ~~~~~~~~~~~~~~~~~~ > Tony Graziano, Manager > Telephone: 434.984.8430 > sip: [email protected] > Fax: 434.465.6833 > ~~~~~~~~~~~~~~~~~~ > Linked-In Profile: > http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4 > Ask about our Internet Fax services! > ~~~~~~~~~~~~~~~~~~ > > Using or developing for sipXecs from SIPFoundry? Ask me about sipX-CoLab 2013! > > > > LAN/Telephony/Security and Control Systems Helpdesk: > Telephone: 434.984.8426 > sip: [email protected] > > Helpdesk Customers: http://myhelp.myitdepartment.net > Blog: http://blog.myitdepartment.net > _______________________________________________ > sipx-users mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-users/
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
