maslym Posted October 24, 2007 Report Share Posted October 24, 2007 If I register my cell phone number under my extension, when I make a call from my cell phone into my own pbx on the pbxnsip server, I will hit the auto attendant annoucement instead of the DISA menu. But when I make a call from my cell phone into other pbx on the same pbxnsip server, I will hit the DISA menu instead of the auto attendant annoucement of that pbx. This really confuses me. This happens on both 2.1.0.2115 (Linux) and 2.0.3.1715 (Unix). Any idea? Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted October 24, 2007 Report Share Posted October 24, 2007 Maybe there is a matching problem with the leading 1 (in NANPA area). Check the dialplan scheme of the domains. Quote Link to comment Share on other sites More sharing options...
maslym Posted October 24, 2007 Author Report Share Posted October 24, 2007 Okay the problem is fixed if I change "Default PnP Dialplan Scheme" to something other than "User must press enter". But it seems that I have to change such setting for all domains on the same pbxnsip server because the call from the cell phone will still hit DISA menu on any domain with "Default PnP Dialplan Scheme" set to "User must press enter". For example, if I register the cell phone under any extension in domain1 and set "Default PnP Dialplan Scheme" to "North America (3-digit extensions [2-7]xx)". The call from my cell phone into domain1 will hit the auto attendant annoucement. But the call from my cell phone to any other domain will still hit DISA menu if "Default PnP Dialplan Scheme" of that domain is set to "User must press enter". So it seems that the pbxnsip will search all domains for the registered cell phone number, not just the domain that the call from the cell phone is coming into. Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted October 25, 2007 Report Share Posted October 25, 2007 Well, the original problem is how to present numbers in a "canonical" format on you server. There are different conflicting styles: 1xxxxxxxxxx, xxxxxxxxxx, and +1xxxxxxxxxx. In the end, the PBX must make a string comparison to get a match. Ideally, all connected devices talk the same way. The dial plan "workaround" puts NANPA numbers into a internal canonical format, so that the comparison works. If you are living outside of the NANPA there is no other choice than getting all connected trunks straight. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.