OK, figured out that in the vars.xml file, I can set the domain from internal-ip-v4 to 192.168.11.5 in the pre-processor command. Why internal-ip-v4 points to the external ip of the WAN interface (got from PPPOE) is another question. But, I digress. That give me a user of 1009@192.168.11.5. The sounds of rejoicing ring in my ears. However, I still don't get the message waiting indicator to go off. Or get the stutter tone. But, the message is there. *Everything works perfectly. Just not the wmi. Mercy? * Mike On Tue, Jul 20, 2010 at 10:03 AM, Michael Gende <mgende@gendesign.com>wrote:
Hello All,
I'm interested in understand more about how a user (1009@somedomain for instance) acquires that "somedomain".
Here's an example:
Registrations:
================================================================================================= Call-ID: b5429e1b9f1b91fd@192.168.99.101 User: 1009@*99.93.12.80*
Contact: "user" Agent: Grandstream GXP2000 1.2.2.26 Status: Registered(UDP)(unknown) EXP(2010-07-20 11:54:30) Host: pfsense.local IP: 192.168.99.101 Port: 5060
Auth-User: 1009 Auth-Realm: *192.168.11.5*
=================================================================================================
Note the differences in the User: domain (99.93.12.80 is actually the external IP address) and the Auth-Realm: 192.158.11.5 (which is the LAN ip of the FreeSwitch box).
Typically, I'd like to see the user show as 1009@internalLANip or 1009@192.168.11.5 in this case. For some reason, I can't make that happen. Something stupid I'm doing, surely. But I can't see it at the moment.
This functions fine for calling. But, I can't get the MWI to light up on the phone or get the tones to indicate a message. I assume this is because FS is looking for user@LANip not user@externalWANip. But the vm is there if I actually go look in the VM box.
Comments? I'm scratching my head. Must be in the internal.xml somewhere.
Regards,
Mike