then i think its a lack of support on the part of sflphone. have you talked to them as to whether they plan to support hostname or srv? I am not sure this is a sipx question or problem. sflphone is really geared towards * and likely hasn't matured to handle dns properly yet.
2012/4/3 Simon Brûlé <[email protected]> > Right now the softphone (SFLPhone) that is in the same subnet can be > registered by the IP alias that SipXecs have but cant register by hostname > or domain name. > > I can ping the hostname of the SipXecs server and i can resolve the SRV > record i tried with this command *dig -t SRV _sip._udp.example.com* that > i found on the Wiki and its working. > > > 2012/4/3 Tony Graziano <[email protected]> > >> can you ping by hostname? how are the phones tryong to register? by ip, >> hostname or domain name? >> >> if the user agent is sflphone, can it register by domain? do you have srv >> records populated that the host pc can resolve? >> >> realize if you are trying to register by IP, you need to add the IP as a >> domain alias to sipxconifg. You stand to lose functionality by registering >> to a hostname or IP address. >> >> good luck. >> >> >> 2012/4/3 Simon Brûlé <[email protected]> >> >>> RIght now i can ping my sipXecs server by its domain name from a >>> computer on the same subnet and from one on a different subnet but they >>> cant register with their softphone. >>> >>> With the one on the same subnet i get the error 502 Bad Gateway and from >>> the one outside the subnet i get a Transfer Error and in the debug mode the >>> error are No SRV Record and couldn't fin host. >>> >>> >>> 2012/4/3 Simon Brûlé <[email protected]> >>> >>>> Thanks for the suggestion I am working on it at the moment. >>>> >>>> >>>> 2012/4/1 Michael Picher <[email protected]> >>>> >>>>> sipXecs likes domain names... if you want to play with IP addresses, >>>>> I'd suggest not. >>>>> >>>>> see wiki for DNS suggestions, and start with a simple network first to >>>>> learn the ropes. >>>>> >>>>> mike >>>>> >>>>> On Fri, Mar 30, 2012 at 3:13 PM, Simon Brûlé < >>>>> [email protected]> wrote: >>>>> >>>>>> Hi >>>>>> >>>>>> My network (for testing purpose) looks like this at the moment. >>>>>> >>>>>> WAN ---------------> Router --------------------> LAN -------------> >>>>>> Router --------------------> SipXecs >>>>>> xxx.xxx.xxx.xxx and 192.168.175.1 192.168.175.22 and >>>>>> 192.168.0.2 192.168.0.1 >>>>>> >>>>>> Keep in mind this is only for testing purpose. >>>>>> >>>>>> I have 2 computer in the 192.168.175.xxx network with softphone and I >>>>>> am not able to register them to SipXecs.The Ip Adresse of the computer >>>>>> use >>>>>> for the test is 192.168.175.136. >>>>>> >>>>>> I did everything as they say in the wiki >>>>>> >>>>>> http://wiki.sipfoundry.org/display/sipXecs/Remote+User+NAT+Traversal >>>>>> >>>>>> I did the troubleshooting test for problem #1.The Number is different >>>>>> from 0 each time so my sipXecs receive everything but my SFLPhone and the >>>>>> ekiga of the other computer have the Error 483 "Too Many Hops". >>>>>> >>>>>> The text file I created to put the result of the Tail of the >>>>>> sipXproxy file got 170 line in about 2-3sec when I try to log one of my >>>>>> softphone. >>>>>> >>>>>> The line are all the same. Here is an exemple of the incoming lines, >>>>>> the outgoing lines and the NAT lines I have in the file: >>>>>> >>>>>> "2012-03-30T17:30:14.399076Z":104805:INCOMING:INFO:voiptest.netappsid.local:SipClientUdp-12:4237A940:SipXProxy:"Read >>>>>> SIP message:\n----Local Host:192.168.0.1---- Port: 5060----\n----Remote >>>>>> Host:192.168.175.22---- Port: 5060----\nSIP/2.0 483 Too many >>>>>> hops\r\nFrom: < >>>>>> sip:[email protected]>;tag=19f76c2c-9a0c-4f24-9f2c-afd86d03ef35\r\nTo: >>>>>> <sip:[email protected]>;tag=N39HZK\r\nCall-Id: >>>>>> bc3d355a-5161-4c83-b5f0-a59c471be90d\r\nCseq: 25984 REGISTER\r\nVia: >>>>>> SIP/2.0/UDP >>>>>> 192.168.0.1:5060;branch=z9hG4bK-XX-07f9Y5qFu6pl6TjooSuxLgqdow;received=192.168.0.2;rport=5060\r\nVia: >>>>>> SIP/2.0/UDP >>>>>> 192.168.0.1:5060;branch=z9hG4bK-XX-07f6AirluMWLBMyodL4I7TqoSg;received=192.168.0.2;rport=5060\r\nVia: >>>>>> SIP/2.0/UDP >>>>>> 192.168.175.136:5060;rport=5060;branch=z9hG4bKPj3b0817f3-43c8-4ce0-a346-d8008040fe2c\r\nWarning: >>>>>> 399 192.168.0.1 \"Too many hops\"\r\nContent-Type: >>>>>> message/sipfrag\r\nServer: sipXecs/4.4.0 sipXecs/sipXproxy >>>>>> (Linux)\r\nContent-Length: 3167\r\nDate: Fri, 30 Mar 2012 17:30:12 >>>>>> GMT\r\n\r\nREGISTER sip:192.168.175.22 SIP/2.0\r\nRecord-Route: >>>>>> <sip:192.168.0.1:5060;lr;sipXecs-rs=%2Aauth%7E.%2Afrom%7EMTlmNzZjMmMtOWEwYy00ZjI0LTlmMmMtYWZkODZkMDNlZjM1.900_ntap%2ACrT%7EMTkyLjE2OC4wLjI6NDY5OTM7dHJhbnNwb3J0PXVkcA%60%60%214a544449ed5ce5e50a94e999a899bdc5>\r\nVia: >>>>>> SIP/2.0/TCP >>>>>> 192.168.0.1:5060;branch=z9hG4bK-XX-0832i5x33`VKc22zP3mkGNjmfQ;received=192.168.0.2;rport=46993\r\nVia: >>>>>> SIP/2.0/TCP >>>>>> 192.168.0.1:5060;branch=z9hG4bK-XX-082fq1WJ8M5x6b4tDeiljIBDTA;received=192.168.0.2;rport=46993\r\nVia: >>>>>> SIP/2.0/TCP >>>>>> 192.168.0.1:5060;branch=z9hG4bK-XX-082csuOFUit3bmLpyKgObSVCXA;received=192.168.0.2;rport=46993\r\nVia: >>>>>> SIP/2.0/TCP >>>>>> 192.168.0.1:5060;branch=z9hG4bK-XX-0829VHLuUQt1lIHkHqgVbjqDKQ;received=192.168.0.2;rport=46993\r\nVia: >>>>>> SIP/2.0/TCP >>>>>> 192.168.0.1:5060;branch=z9hG4bK-XX-0826Cupn7TcFk7PeF35kpdFV`w;received=192.168.0.2;rport=46993\r\nVia: >>>>>> SIP/2.0/TCP >>>>>> 192.168.0.1:5060;branch=z9hG4bK-XX-08230CQtsnYLPfSwLvYOh80itg;received=192.168.0.2;rport=46993\r\nVia: >>>>>> SIP/2.0/TCP >>>>>> 192.168.0.1:5060;branch=z9hG4bK-XX-0820av2EdSD`IWoQzZaWUD6VNw;received=192.168.0.2;rport=46993\r\nVia: >>>>>> SIP/2.0/TCP >>>>>> 192.168.0.1:5060;branch=z9hG4bK-XX-081dLyz7l7Q2j7wpiJyQvREDig;received=192.168.0.2;rport=46993\r\nVia: >>>>>> SIP/2.0/TCP >>>>>> 192.168.0.1:5060;branch=z9hG4bK-XX-081aE4YsWuzNtylJsrrXDRPpJw;received=192.168.0.2;rport=46993\r\nVia: >>>>>> SIP/2.0/TCP >>>>>> 192.168.0.1:5060;branch=z9hG4bK-XX-08178PP4lMUYpgYq8P52Jn`2vg;received=192.168.0.2;rport=46993\r\nVia: >>>>>> SIP/2.0/TCP >>>>>> 192.168.0.1:5060;branch=z9hG4bK-XX-0814SHnrAwRgnajljOeOsxph6A;received=192.168.0.2;rport=46993\r\nVia: >>>>>> SIP/2.0/TCP >>>>>> 192.168.0.1:5060;branch=z9hG4bK-XX-0811JA_CvNGjag8HGBcpHMt7ag;received=192.168.0.2;rport=46993\r\nVia: >>>>>> SIP/2.0/TCP >>>>>> 192.168.0.1:5060;branch=z9hG4bK-XX-080e3ERtfd7bk2Kvwpo0gBczhQ;received=192.168.0.2;rport=46993\r\nVia: >>>>>> SIP/2.0/TCP >>>>>> 192.168.0.1:5060;branch=z9hG4bK-XX-080b4OdhNrpwOTslfNyvvMSq1Q;received=192.168.0.2;rport=46993\r\nVia: >>>>>> SIP/2.0/TCP >>>>>> 192.168.0.1:5060;branch=z9hG4bK-XX-08087iV`FPifr5gtrxb6pmgBVw;received=192.168.0.2;rport=46993\r\nVia: >>>>>> SIP/2.0/TCP >>>>>> 192.168.0.1:5060;branch=z9hG4bK-XX-0805ezBBZ9Rr5Uxix_`iaS6i0A;received=192.168.0.2;rport=46993\r\nVia: >>>>>> SIP/2.0/TCP >>>>>> 192.168.0.1:5060;branch=z9hG4bK-XX-08021pc96y1seSQwJcQrD8WMwQ;received=192.168.0.2;rport=46993\r\nVia: >>>>>> SIP/2.0/UDP >>>>>> 192.168.0.1:5060;branch=z9hG4bK-XX-07ffx`4TeZoMqeci8hGz9zRAQw;received=192.168.0.2;rport=5060\r\nVia: >>>>>> SIP/2.0/UDP >>>>>> 192.168.0.1:5060;branch=z9hG4bK-XX-07fcJ8HxRMec4Qr2kgAJ`ZQj5w;received=192.168.0.2;rport=5060\r\nVia: >>>>>> SIP/2.0/UDP >>>>>> 192.168.0.1:5060;branch=z9hG4bK-XX-07f9Y5qFu6pl6TjooSuxLgqdow;received=192.168.0.2;rport=5060\r\nVia: >>>>>> SIP/2.0/UDP >>>>>> 192.168.0.1:5060;branch=z9hG4bK-XX-07f6AirluMWLBMyodL4I7TqoSg;received=192.168.0.2;rport=5060\r\nVia: >>>>>> SIP/2.0/UDP >>>>>> 192.168.175.136:5060;rport=5060;branch=z9hG4bKPj3b0817f3-43c8-4ce0-a346-d8008040fe2c\r\nMax-Forwards: >>>>>> 0\r\nFrom: >>>>>> <sip:[email protected]>;tag=19f76c2c-9a0c-4f24-9f2c-afd86d03ef35\r\nTo: >>>>>> <sip:[email protected]>\r\nCall-Id: >>>>>> bc3d355a-5161-4c83-b5f0-a59c471be90d\r\nCseq: 25984 >>>>>> REGISTER\r\nUser-Agent: >>>>>> SFLphone\r\nContact: <sip:[email protected]:5060>\r\nExpires: >>>>>> 600\r\nAllow: PRACK, SUBSCRIBE, NOTIFY, REFER, INVITE, ACK, BYE, CANCEL, >>>>>> UPDATE, INFO, REGISTER, OPTIONS, MESSAGE\r\nContent-Length: 0\r\nDate: >>>>>> Fri, >>>>>> 30 Mar 2012 17:30:10 >>>>>> GMT\r\n\r\n====================END====================" >>>>>> >>>>>> >>>>>> "2012-03-30T17:30:14.399076Z":104805:INCOMING:INFO:voiptest.netappsid.local:SipClientUdp-12:4237A940:SipXProxy:"Read >>>>>> SIP message:\n----Local Host:192.168.0.1---- Port: 5060----\n----Remote >>>>>> Host:192.168.175.22---- Port: 5060----\nSIP/2.0 483 Too many >>>>>> hops\r\nFrom: < >>>>>> sip:[email protected]>;tag=19f76c2c-9a0c-4f24-9f2c-afd86d03ef35\r\nTo: >>>>>> <sip:[email protected]>;tag=N39HZK\r\nCall-Id: >>>>>> bc3d355a-5161-4c83-b5f0-a59c471be90d\r\nCseq: 25984 REGISTER\r\nVia: >>>>>> SIP/2.0/UDP >>>>>> 192.168.0.1:5060;branch=z9hG4bK-XX-07f9Y5qFu6pl6TjooSuxLgqdow;received=192.168.0.2;rport=5060\r\nVia: >>>>>> SIP/2.0/UDP >>>>>> 192.168.0.1:5060;branch=z9hG4bK-XX-07f6AirluMWLBMyodL4I7TqoSg;received=192.168.0.2;rport=5060\r\nVia: >>>>>> SIP/2.0/UDP >>>>>> 192.168.175.136:5060;rport=5060;branch=z9hG4bKPj3b0817f3-43c8-4ce0-a346-d8008040fe2c\r\nWarning: >>>>>> 399 192.168.0.1 \"Too many hops\"\r\nContent-Type: >>>>>> message/sipfrag\r\nServer: sipXecs/4.4.0 sipXecs/sipXproxy >>>>>> (Linux)\r\nContent-Length: 3167\r\nDate: Fri, 30 Mar 2012 17:30:12 >>>>>> GMT\r\n\r\nREGISTER sip:192.168.175.22 SIP/2.0\r\nRecord-Route: >>>>>> <sip:192.168.0.1:5060;lr;sipXecs-rs=%2Aauth%7E.%2Afrom%7EMTlmNzZjMmMtOWEwYy00ZjI0LTlmMmMtYWZkODZkMDNlZjM1.900_ntap%2ACrT%7EMTkyLjE2OC4wLjI6NDY5OTM7dHJhbnNwb3J0PXVkcA%60%60%214a544449ed5ce5e50a94e999a899bdc5>\r\nVia: >>>>>> SIP/2.0/TCP >>>>>> 192.168.0.1:5060;branch=z9hG4bK-XX-0832i5x33`VKc22zP3mkGNjmfQ;received=192.168.0.2;rport=46993\r\nVia: >>>>>> SIP/2.0/TCP >>>>>> 192.168.0.1:5060;branch=z9hG4bK-XX-082fq1WJ8M5x6b4tDeiljIBDTA;received=192.168.0.2;rport=46993\r\nVia: >>>>>> SIP/2.0/TCP >>>>>> 192.168.0.1:5060;branch=z9hG4bK-XX-082csuOFUit3bmLpyKgObSVCXA;received=192.168.0.2;rport=46993\r\nVia: >>>>>> SIP/2.0/TCP >>>>>> 192.168.0.1:5060;branch=z9hG4bK-XX-0829VHLuUQt1lIHkHqgVbjqDKQ;received=192.168.0.2;rport=46993\r\nVia: >>>>>> SIP/2.0/TCP >>>>>> 192.168.0.1:5060;branch=z9hG4bK-XX-0826Cupn7TcFk7PeF35kpdFV`w;received=192.168.0.2;rport=46993\r\nVia: >>>>>> SIP/2.0/TCP >>>>>> 192.168.0.1:5060;branch=z9hG4bK-XX-08230CQtsnYLPfSwLvYOh80itg;received=192.168.0.2;rport=46993\r\nVia: >>>>>> SIP/2.0/TCP >>>>>> 192.168.0.1:5060;branch=z9hG4bK-XX-0820av2EdSD`IWoQzZaWUD6VNw;received=192.168.0.2;rport=46993\r\nVia: >>>>>> SIP/2.0/TCP >>>>>> 192.168.0.1:5060;branch=z9hG4bK-XX-081dLyz7l7Q2j7wpiJyQvREDig;received=192.168.0.2;rport=46993\r\nVia: >>>>>> SIP/2.0/TCP >>>>>> 192.168.0.1:5060;branch=z9hG4bK-XX-081aE4YsWuzNtylJsrrXDRPpJw;received=192.168.0.2;rport=46993\r\nVia: >>>>>> SIP/2.0/TCP >>>>>> 192.168.0.1:5060;branch=z9hG4bK-XX-08178PP4lMUYpgYq8P52Jn`2vg;received=192.168.0.2;rport=46993\r\nVia: >>>>>> SIP/2.0/TCP >>>>>> 192.168.0.1:5060;branch=z9hG4bK-XX-0814SHnrAwRgnajljOeOsxph6A;received=192.168.0.2;rport=46993\r\nVia: >>>>>> SIP/2.0/TCP >>>>>> 192.168.0.1:5060;branch=z9hG4bK-XX-0811JA_CvNGjag8HGBcpHMt7ag;received=192.168.0.2;rport=46993\r\nVia: >>>>>> SIP/2.0/TCP >>>>>> 192.168.0.1:5060;branch=z9hG4bK-XX-080e3ERtfd7bk2Kvwpo0gBczhQ;received=192.168.0.2;rport=46993\r\nVia: >>>>>> SIP/2.0/TCP >>>>>> 192.168.0.1:5060;branch=z9hG4bK-XX-080b4OdhNrpwOTslfNyvvMSq1Q;received=192.168.0.2;rport=46993\r\nVia: >>>>>> SIP/2.0/TCP >>>>>> 192.168.0.1:5060;branch=z9hG4bK-XX-08087iV`FPifr5gtrxb6pmgBVw;received=192.168.0.2;rport=46993\r\nVia: >>>>>> SIP/2.0/TCP >>>>>> 192.168.0.1:5060;branch=z9hG4bK-XX-0805ezBBZ9Rr5Uxix_`iaS6i0A;received=192.168.0.2;rport=46993\r\nVia: >>>>>> SIP/2.0/TCP >>>>>> 192.168.0.1:5060;branch=z9hG4bK-XX-08021pc96y1seSQwJcQrD8WMwQ;received=192.168.0.2;rport=46993\r\nVia: >>>>>> SIP/2.0/UDP >>>>>> 192.168.0.1:5060;branch=z9hG4bK-XX-07ffx`4TeZoMqeci8hGz9zRAQw;received=192.168.0.2;rport=5060\r\nVia: >>>>>> SIP/2.0/UDP >>>>>> 192.168.0.1:5060;branch=z9hG4bK-XX-07fcJ8HxRMec4Qr2kgAJ`ZQj5w;received=192.168.0.2;rport=5060\r\nVia: >>>>>> SIP/2.0/UDP >>>>>> 192.168.0.1:5060;branch=z9hG4bK-XX-07f9Y5qFu6pl6TjooSuxLgqdow;received=192.168.0.2;rport=5060\r\nVia: >>>>>> SIP/2.0/UDP >>>>>> 192.168.0.1:5060;branch=z9hG4bK-XX-07f6AirluMWLBMyodL4I7TqoSg;received=192.168.0.2;rport=5060\r\nVia: >>>>>> SIP/2.0/UDP >>>>>> 192.168.175.136:5060;rport=5060;branch=z9hG4bKPj3b0817f3-43c8-4ce0-a346-d8008040fe2c\r\nMax-Forwards: >>>>>> 0\r\nFrom: >>>>>> <sip:[email protected]>;tag=19f76c2c-9a0c-4f24-9f2c-afd86d03ef35\r\nTo: >>>>>> <sip:[email protected]>\r\nCall-Id: >>>>>> bc3d355a-5161-4c83-b5f0-a59c471be90d\r\nCseq: 25984 >>>>>> REGISTER\r\nUser-Agent: >>>>>> SFLphone\r\nContact: <sip:[email protected]:5060>\r\nExpires: >>>>>> 600\r\nAllow: PRACK, SUBSCRIBE, NOTIFY, REFER, INVITE, ACK, BYE, CANCEL, >>>>>> UPDATE, INFO, REGISTER, OPTIONS, MESSAGE\r\nContent-Length: 0\r\nDate: >>>>>> Fri, >>>>>> 30 Mar 2012 17:30:10 >>>>>> GMT\r\n\r\n====================END====================" >>>>>> >>>>>> "2012-03-30T17:30:10.176058Z":101184:NAT:DEBUG:voiptest.netappsid.local:SipRouter-15:4287F940:SipXProxy:"NTAP >>>>>> considering REGISTER sip:192.168.175.22 SIP/2.0\r\nVia: SIP/2.0/UDP >>>>>> 192.168.175.136:5060;rport=5060;branch=z9hG4bKPj3b0817f3-43c8-4ce0-a346-d8008040fe2c\r\nMax-Forwards: >>>>>> 70\r\nFrom: >>>>>> <sip:[email protected]>;tag=19f76c2c-9a0c-4f24-9f2c-afd86d03ef35\r\nTo: >>>>>> <sip:[email protected]>\r\nCall-Id: >>>>>> bc3d355a-5161-4c83-b5f0-a59c471be90d\r\nCseq: 25984 >>>>>> REGISTER\r\nUser-Agent: >>>>>> SFLphone\r\nContact: >>>>>> <sip:[email protected]:5060;x-sipX-nonat>\r\nExpires: >>>>>> 600\r\nAllow: PRACK, SUBSCRIBE, NOTIFY, REFER, INVITE, ACK, BYE, CANCEL, >>>>>> UPDATE, INFO, REGISTER, OPTIONS, MESSAGE\r\nContent-Length: 0\r\nDate: >>>>>> Fri, >>>>>> 30 Mar 2012 17:30:10 GMT" >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> sipx-users mailing list >>>>>> [email protected] >>>>>> List Archive: http://list.sipfoundry.org/archive/sipx-users/ >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> Michael Picher, Director of Technical Services >>>>> eZuce, Inc. >>>>> >>>>> 300 Brickstone Square**** >>>>> >>>>> Suite 201**** >>>>> >>>>> Andover, MA. 01810 >>>>> O.978-296-1005 X2015 >>>>> M.207-956-0262 >>>>> @mpicher <http://twitter.com/mpicher> >>>>> www.ezuce.com >>>>> >>>>> >>>>> ------------------------------------------------------------------------------------------------------------ >>>>> There are 10 kinds of people in the world, those who understand binary >>>>> and those who don't. >>>>> >>>>> >>>>> _______________________________________________ >>>>> 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/ >>> >> >> >> >> -- >> ~~~~~~~~~~~~~~~~~~ >> 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! >> ~~~~~~~~~~~~~~~~~~ >> >> LAN/Telephony/Security and Control Systems Helpdesk: >> Telephone: 434.984.8426 >> sip: [email protected].**net<[email protected]> >> >> Helpdesk Customers: >> http://myhelp.myitdepartment.**net<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/ > -- ~~~~~~~~~~~~~~~~~~ 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! ~~~~~~~~~~~~~~~~~~ -- 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/
