Carl Johnson Posted September 4, 2008 Report Share Posted September 4, 2008 If I set an ANI in v3, the PBX transforms the given ANI and add the Country code .. this is fully unexpected? What is wrong? Set ANI to: 4061234567 Trunk sends: 14061234567 From: "Carl Johnson" <sip:14061234567@192.168.40.218;user=phone>;tag=2047478008 Quote Link to comment Share on other sites More sharing options...
Carl Johnson Posted September 6, 2008 Author Report Share Posted September 6, 2008 If I set an ANI in v3, the PBX transforms the given ANI and add the Country code .. this is fully unexpected? What is wrong? Set ANI to: 4061234567 Trunk sends: 14061234567 From: "Carl Johnson" <sip:14061234567@192.168.40.218;user=phone>;tag=2047478008 Any ideas? Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted September 6, 2008 Report Share Posted September 6, 2008 If I set an ANI in v3, the PBX transforms the given ANI and add the Country code .. this is fully unexpected? What is wrong? Set ANI to: 4061234567 Trunk sends: 14061234567 From: "Carl Johnson" <sip:14061234567@192.168.40.218;user=phone>;tag=2047478008 That happens when you select that your domain is in the NANPA region. Quote Link to comment Share on other sites More sharing options...
Carl Johnson Posted September 22, 2008 Author Report Share Posted September 22, 2008 Ok, I guess that doesn't seem the expected result. So just remove that CC and it should work as expected then? Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted September 22, 2008 Report Share Posted September 22, 2008 Ok, I guess that doesn't seem the expected result. So just remove that CC and it should work as expected then? No, just select "user must press enter" as region... That does not change anything. Quote Link to comment Share on other sites More sharing options...
Carl Johnson Posted September 26, 2008 Author Report Share Posted September 26, 2008 That would affect the ability to properly PNP, wouldn't it? Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted September 26, 2008 Report Share Posted September 26, 2008 That would affect the ability to properly PNP, wouldn't it? Well, only the dialplan part... As VoIP becomes more mainstream and people have cell phones, hitting the "call" button on a SIP phone also becomes more popular these days. Quote Link to comment Share on other sites More sharing options...
Carl Johnson Posted September 29, 2008 Author Report Share Posted September 29, 2008 That is definetly and interesting spin .. so is this something that we are just stuck with as it seems incorrect if I specifiy a ANI it should just use that and not try to outsmart the input .. right? Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted September 29, 2008 Report Share Posted September 29, 2008 That is definetly and interesting spin .. so is this something that we are just stuck with as it seems incorrect if I specifiy a ANI it should just use that and not try to outsmart the input .. right? Well, what we need at a certian point is a transformation rule for the trunk. Because different service providers have different ways of presenting a phone number we might need a setting for that. For example, one provider would like to see <sip:+19787562777@...>, the next one <sip:19787562777@...>, and the next one <sip:9787562777@...>, and the next one <sip:0019787562777@...>. Internally we decided to use only the + form, as this is the only global common denominator. Quote Link to comment Share on other sites More sharing options...
Carl Johnson Posted October 8, 2008 Author Report Share Posted October 8, 2008 Can this be put in the next incremental release, maybe 3.0.2 then as this completly breaks our ability to use forwarding, etc starting a few versions ago and we would really appreciate the change. Thanks! Well, what we need at a certian point is a transformation rule for the trunk. Because different service providers have different ways of presenting a phone number we might need a setting for that. For example, one provider would like to see <sip:+19787562777@...>, the next one <sip:19787562777@...>, and the next one <sip:9787562777@...>, and the next one <sip:0019787562777@...>. Internally we decided to use only the + form, as this is the only global common denominator. Quote Link to comment Share on other sites More sharing options...
Carl Johnson Posted October 31, 2008 Author Report Share Posted October 31, 2008 On this, I have been testing build 3033 and have a few questions so on these scenarios: 1) I dial out on my extension that has an ANI set, it properly passes that ANI 40612345678 in the FROM header as set on the extension and using the NAPNA 10 trunk setting From: "Carl Johnson" <sip:40612345678@192.168.40.218;user=phone>;tag=574149672 2) I dial into the PBX with a header of: From: <sip:4067890000@rcp.local:5060>;tag=3184c2f731d55ce then that extension is set with a proper ANI and is setup to redirect calls outside via the same trunk as used above the system isists on sending the users inbound caller-id, which is not what is hoped for can we resolve this somehow our our circuits lock us into to providing out caller-id that is valid and known as a good DID on that circuit? From: <sip:4067890000@rcp.local:5060;user=phone>;tag=1529366861 instead of the .. I think expected from header of From: "Carl Johnson" <sip:40612345678@192.168.40.218;user=phone>;tag=574149672 Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted October 31, 2008 Report Share Posted October 31, 2008 On this, I have been testing build 3033 and have a few questions so on these scenarios: 1) I dial out on my extension that has an ANI set, it properly passes that ANI 40612345678 in the FROM header as set on the extension and using the NAPNA 10 trunk setting From: "Carl Johnson" <sip:40612345678@192.168.40.218;user=phone>;tag=574149672 2) I dial into the PBX with a header of: From: <sip:4067890000@rcp.local:5060>;tag=3184c2f731d55ce then that extension is set with a proper ANI and is setup to redirect calls outside via the same trunk as used above the system isists on sending the users inbound caller-id, which is not what is hoped for can we resolve this somehow our our circuits lock us into to providing out caller-id that is valid and known as a good DID on that circuit? From: <sip:4067890000@rcp.local:5060;user=phone>;tag=1529366861 instead of the .. I think expected from header of From: "Carl Johnson" <sip:40612345678@192.168.40.218;user=phone>;tag=574149672 We have introduced a new setting for the trunk that tells the PBX hoe to represent a international telephone number (+ sign in the beginning, 011, 00, and so on). It is still not 100 % stable. Not sure if you want to try that one out. Quote Link to comment Share on other sites More sharing options...
Carl Johnson Posted October 31, 2008 Author Report Share Posted October 31, 2008 That is the setting I am using .. what I would like to know is if a call comes in how can I FORCE the outgoing ANI to be the extenstions ANI vs the incoming caller-id? Quote Link to comment Share on other sites More sharing options...
Carl Johnson Posted November 7, 2008 Author Report Share Posted November 7, 2008 Anyone? Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted November 8, 2008 Report Share Posted November 8, 2008 Anyone? If you like give http://pbxnsip.com/protect/pbxctrl-3.1.0.3042.exe a shot. Quote Link to comment Share on other sites More sharing options...
Wim van Ommen Posted November 10, 2008 Report Share Posted November 10, 2008 If you like give http://pbxnsip.com/protect/pbxctrl-3.1.0.3042.exe a shot. Could you please check the webinterface of this version with other browsers then Internetexplorer, the new stuff for codecs does not work in Safari and Firefox. Quote Link to comment Share on other sites More sharing options...
Carl Johnson Posted November 10, 2008 Author Report Share Posted November 10, 2008 Can you post a debian 4.0 x86 version? If you like give http://pbxnsip.com/protect/pbxctrl-3.1.0.3042.exe a shot. Quote Link to comment Share on other sites More sharing options...
pbx support Posted November 10, 2008 Report Share Posted November 10, 2008 Can you post a debian 4.0 x86 version? Please check out the posting http://forum.pbxnsip.com/index.php?showtopic=1650&hl= 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.