It seems getting closer .... . This is my solution though I don't make myself understood fully. 1. Add a dial plan - matching patterns : $request = ^REGISTER - deploy pattern : $continue = true, &register.contact.remote = true, &register.contact.nat = true 2. Add a variable on Congiruation>Advanced ...

One more for your understanding. Case A) Client1(wifi) --> Client2(4G) : Client2 can't get INVITE Case B) Client2(4G) --> Client1(wifi) : Client1 can get INVITE and talk together Case C) Client1(wifi) <--> Client2(4G) : works fine at any direction When makes a call, - On Case A, Client1 uses "Source ...

1. Brekeke Product Name and Version: 3.5.3.0, Standard 2. Java version: 1.8.0_77 3. OS type and the version: Windows Server 2008 4. UA (phone), gateway or other hardware/software involved: Phone on 4G connection 5. Your problem: A client works fine with registration and a call on WiFi, but it can't ...

Brekeke SIP server version is 3.5.3.0. From my understanding, Brekeke SIP server supports Shared address space from 3.4 so I guess no need to setup something for RFC6598 on Brekeke SIP Server. Could you let me know how callee uses IP in Shared address space? Or do I need to set up the configuration ...

I also have a similar problem on 4G call connection though it works on wifi well.

- Registration is done successfully
- Invitation call is not recognized from a callee, so status stays on 'Inviting'

Is there any other setting required for 4G