Slightly different situation today(the only change i did was to send profiles and turn on capture database)
First call was from 201(primary server) to 200(secondary server), didn't work. Thats probably [email protected] to [email protected] in the logs. This worked yesterday. Second call from 201 to [email protected] (manualy gave ip address in call to field). That one works Third was 200 to 201, probably [email protected] to [email protected] in the logs Fourth was 200 to [email protected] (manualy gave ip address). That one works as well. https://www.dropbox.com/s/olw1nyxj57gadsc/configuration.tar.gz https://www.dropbox.com/s/6j1bzcgtbf1qdxh/homer.tar.gz https://www.dropbox.com/s/7r3a9d8eg1qxvhw/sipx-snapshot-sipx1.callidus.local .tar.gz https://www.dropbox.com/s/bq5yras7hyb0zyn/sipx-snapshot-sipx2.callidus.local .tar.gz From: Joegen Baclor [mailto:[email protected]] Sent: Wednesday, October 03, 2012 5:54 AM To: Discussion list for users of sipXecs software Cc: darthzejdr Subject: Re: [sipx-users] 4.6 Cluster Hi, Thanks for the snapshots. Based on the logs that was available in the registrar of the secondary node, it was able to redirect properly to the phone SIP/2.0 302 Moved Temporarily\r From: \"200\" <mailto:sip:[email protected]> <sip:[email protected]>;tag=ab5d6542\r To: <mailto:sip:[email protected]> <sip:[email protected]>;tag=AbhEaS\r Call-Id: MjdiMGE4YWE4MGY4ODU3NDgzM2E1YzU1ZTBjYmU0NTk.\r Cseq: 2 INVITE\r Via: SIP/2.0/TCP 192.168.0.47;branch=z9hG4bK-XX-001aeUrpcbmu7vBf`_c61fH_Yw\r Via: SIP/2.0/UDP 192.168.0.55:15810;branch=z9hG4bK-d8754z-983553228a49011f-1---d8754z-;rport= 15810\r Record-Route: <sip:192.168.0.47:5060;lr>\r Contact: <mailto:sip:[email protected]:62697;transport=TCP;rinstance=4ce1d9be058b9429; x-sipX-nonat;sipXecs-CallDest=INT?expires=20&ROUTE=%3Csip%3Acallidus.local%3 Blr%3E> <sip:[email protected]:62697;transport=TCP;rinstance=4ce1d9be058b9429;x-sipX- nonat;sipXecs-CallDest=INT?expires=20&ROUTE=%3Csip%3Acallidus.local%3Blr%3E> \r Contact: <mailto:sip:[email protected]:62945;transport=TCP;rinstance=276e8dd6bd8063e0; x-sipX-nonat;sipXecs-CallDest=INT?expires=20&ROUTE=%3Csip%3Acallidus.local%3 Blr%3E> <sip:[email protected]:62945;transport=TCP;rinstance=276e8dd6bd8063e0;x-sipX- nonat;sipXecs-CallDest=INT?expires=20&ROUTE=%3Csip%3Acallidus.local%3Blr%3E> \r Contact: <mailto:sip:[email protected];sipXecs-CallDest=VMR?ROUTE=%3Csip%3Acall idus.local%3Blr%3E> <sip:[email protected];sipXecs-CallDest=VMR?ROUTE=%3Csip%3Acallidus.lo cal%3Blr%3E>;q=0.1\r User-Agent: sipXecs/4.6.0 sipXecs/registry (Linux)\r Date: Tue, 02 Oct 2012 11:51:24 GMT\r Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, REGISTER, SUBSCRIBE\r Accept-Language: en\r Supported: gruu, path\r Content-Length: 0\r However, looking at the proxy log and grepping for the INVITEs I wasn't able to see the sip messages for the earlier transaction. Log is incomplete. If possible, since there seems to be not much traffic in this box yet, that you get actual TCP dumps of the call. You may do this using homer. Joegen On 10/02/2012 07:56 PM, darthzejdr wrote: https://www.dropbox.com/s/iwiatrnvkf7fh9a/sipx-snapshot-sipx1.callidus.local .tar.gz https://www.dropbox.com/s/xwjq7q2px45b4sn/sipx-snapshot-sipx2.callidus.local .tar.gz calls are: 201 -> 200 works 200 -> 201 doesn't work 200 -> [email protected] works From: Joegen Baclor [mailto:[email protected]] Sent: Tuesday, October 02, 2012 1:22 PM To: Discussion list for users of sipXecs software Cc: darthzejdr Subject: Re: [sipx-users] 4.6 Cluster Please send snapshots with both proxy and registrar in debug level. On 10/02/2012 07:08 PM, darthzejdr wrote: I've done a few more tests(extensions registered with normal domain(callidus.local) but using proxy field with ip adress) but again the same problem. II can make calls from primary server to sacondary, but the only way to make a call from secondary server is to use [email protected] as the number i am calling. For some reason secondary server can't reach extensions on primary. From: darthzejdr [mailto:[email protected]] Sent: Tuesday, October 02, 2012 10:49 AM To: 'Discussion list for users of sipXecs software' Subject: RE: [sipx-users] 4.6 Cluster I reinstalled my sipx according to your setup. 201 is registered on primary server(with ip address in domain, 92.168.0.46) 200 is registered on secondary server(with ip address in domain, 192.168.0.47) 201 to 200 works normaly 200 to 201 gives error "user is temporarily unavailable(404)" 200 to [email protected](primary <mailto:[email protected]%28primary> server ip address) works https://www.dropbox.com/s/cn9vqmt25zurm2z/sipx-snapshot-sipx1.callidus.local .tar.gz https://www.dropbox.com/s/loqjb4v0x74kktm/sipx-snapshot-sipx2.callidus.local .tar.gz -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of George Niculae Sent: Friday, September 28, 2012 5:47 PM To: Discussion list for users of sipXecs software Subject: Re: [sipx-users] 4.6 Cluster On Fri, Sep 28, 2012 at 4:35 PM, darthzejdr <[email protected]> wrote: > Didnt help. Everything the same. If i try to call extension on second > server i get The user is temporarily unavailable (404 ) > That's what I did, let me know if testing scenario different: - setup cluster with 2 nodes, both running DNS, Proxy and Registrar - configured secondary IP and fqdn as domain aliases, then sent profiles to servers - registered account 200 Bria on first node (giving 1st node IP as domain) - registered account 201, another phone on 2nd node (giving 2nd node IP as domain) - calls 200 to 200 established just fine George _______________________________________________ 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/ _______________________________________________ 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/
