shopcomputer

What does this mean, I am seeing it in the log.TCP TOS could not be set

I got the same message.

And on the phone I had to set the http client setting with the user name and password of the extension, then it worked. On the server generated folder, it created a folder named localhost, iinstead of the MAC_ADDRESS.

Has this provisioning method been completely disabled from outside the lan? http://pbx.pbxnsip.com:9012/provisioning/s...0041324006D.htm What is the correct method to provision from outside the LAN, and obtain all the phone settings. I tried putting the MAC in the extension, and using http://pbx.pbxnsip.com:9012, the phone logs showed some redirects, time settings being applied however thats about it, it did not register. 3.3.0.3165 (Win32)

I never actually tried it, however these solutions should work. http://www.ippbx.us/Home/tabid/408/List/1/.../1/Default.aspx

FYI it appears to be aknown issue. http://forum.snom.com/index.php?showtopic=...entry2456

Did you try the Snom.com forum?

Here is a new one on the market, I had good experiences with their products. http://www.mobotix.com/eng_US/Products/Hom...IP-Door-Station

I think he is talking about, http://wiki.pbxnsip.com/index.php/Release_..._3.1#Cell_Phone Also, when the cell phone was used to place an outbound call, the PBX sometimes presented the Caller-ID of the cell phone, not the extension. The purpose was to hide it. That was fixed, and now users can use their cell phones to place outbound calls and present the caller-ID of the PBX. For most cases this problem still exists, I did manage to get it working with 1 ITSP, creating an inbound trunk and an outbound trunk, and some how forcing it to display the trunk ANI.

Would be nice to be able to choose in admin how many processes to run, and maybe be able to map domains or functions to a process.

If I understand this, he is trying to block the cell phones number from displaying as the outbound caller ID, this was supposedly fixed in version 3.2, thus far most ITSP's I tried still display the cell phone.

On the IVR there is a from based routing field. Here is an example !8005551212|2125551212|8005552222!401 That will forward the 3 phone numbers to extension 401. You can find more details here http://wiki.pbxnsip.com/index.php/IVR_Node

not fixed for me either.

Did anyone ever get a phone behind a Microsoft ISA server connect to a PBXnSIP server on the public internet. I tried following http://stewedprunes.com/blogs/stewed_prune.../08/29/502.aspx written for Vonage and changing the RTP port range, and also forwarding ports 5060-5080 tcp and udp it did not work. If I set transport=tcp, then I get http://wiki.pbxnsip.com/index.php/One-way_Audio.

Depending on your firmware version, you should have a search field, so you can find the setting in a minute.

I am not following, there is only 1 service flag field in the autoattendant, and one night service field. If you seperate by spaces, the first service flag corresponds to the first night service number, second to the 2nd, etc.?

I am quoting on an opportunity for a nonprofit volunteer organization, they basically have 1 person on duty taking calls on their cell phone 24/7. Every hour there is someone else on duty. I am thinking how to configure this for them, the first thought that came to mind was creating a hunt group and adding all the volunteers as members of the hunt group, and setting the call cell phone option, with an explicit schedule allowing calls only during his on duty hour. However then I reminded myself about our no cell phone from hunt groups issue. I am back at the drawing board. What can I accomplish with a service flag? should I create scheduled service flags for each user and have an IVR forward to the users with manual registration?

On the trunk settings, there are options for changing its behavior.

Do you have a wireshark? Can you check your firewall log?

http://wiki.pbxnsip.com/index.php/PAC has a download link.

I am affraid at the moment you would need to use an IVR node in order to route based on the caller ID.

I have nothing after that, if you post your audiocodes and PBXnSIP logs, I am sure we can figure out your problem.

The IP of the pbxnsip is the 192.168.0.10, I don't know what that password is, it certainly is is not to the PBXnsip, as it is a gateway trunk not registered. According to http://wiki.pbxnsip.com/index.php/Audiocodes those 2 values should be left at their default values.

Here is a sample config from a mp114 ;************** ;** Ini File ** ;************** ;Board: MP-114 FXS_FXO ;Serial Number: 768949 ;Slot Number: 1 ;Software Version: 5.20A.027.004 ;DSP Software Version: 204IM => 520.13 ;Board IP Address: 192.168.0.6 ;Board Subnet Mask: 255.255.255.0 ;Board Default Gateway: 192.168.0.1 ;Ram size: 32M Flash size: 8M ;Num DSPs: 1 Num DSP channels: 4 ;Profile: NONE ;----------------------------------------- [sYSTEM Params] SyslogServerIP = 10.1.1.89 [bSP Params] PCMLawSelect = 3 LocalOAMIPAddress = 192.168.0.6 RoutingTableHopsCountColumn = 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0 [ATM Params] [Analog Params] MinFlashHookTime = 100 FXSLoopCharacteristicsFilename = 'MP11x-02-1-FXS_16KHZ.dat' [ControlProtocols Params] [MGCP Params] [MEGACO Params] EP_Num_0 = 0 EP_Num_1 = 1 EP_Num_2 = 0 EP_Num_3 = 0 EP_Num_4 = 0 [PSTN Params] [sS7 Params] [Voice Engine Params] VoiceVolume = 1 RFC2833PayloadType = 101 CallProgressTonesFilename = 'usa_tones_12.dat' [WEB Params] LogoWidth = '339' [sIP Params] ENABLECALLERID = 1 MAXDIGITS = 11 REGISTRATIONTIME = 3600 ISTWOSTAGEDIAL = 0 GWDEBUGLEVEL = 5 ENABLEEARLYMEDIA = 1 ISUSERPHONE = 0 CNONCE = '0a123bcf' PASSWORD = '787899' ENABLEVOICEDETECTION = 1 ALTROUTINGTEL2IPMODE = 0 ISFAXUSED = 1 [VXML Params] [iPsec Params] [Audio Staging Params] ; ; *** TABLE DspTemplates *** ; This table contains hidden elements and will not be exposed. ; This table exists on board and will be saved during restarts ; ; ; *** TABLE PREFIX *** ; ; [ PREFIX ] FORMAT PREFIX_Index = PREFIX_DestinationPrefix, PREFIX_DestAddress, PREFIX_SourcePrefix, PREFIX_ProfileId, PREFIX_MeteringCode; PREFIX 0 = *, 192.168.0.10, *, 0, 255; [ \PREFIX ] ; ; *** TABLE CoderName *** ; ; [ CoderName ] FORMAT CoderName_Index = CoderName_Type, CoderName_PacketInterval, CoderName_rate, CoderName_PayloadType, CoderName_Sce; CoderName 0 = g711Ulaw64k, 20, 0, 255, 0; [ \CoderName ] ; ; *** TABLE TrunkGroup *** ; ; [ TrunkGroup ] FORMAT TrunkGroup_Index = TrunkGroup_TrunkGroupNum, TrunkGroup_FirstTrunkId, TrunkGroup_FirstBChannel, TrunkGroup_LastBChannel, TrunkGroup_FirstPhoneNumber, TrunkGroup_ProfileId, TrunkGroup_LastTrunkId, TrunkGroup_Module; TrunkGroup 0 = 1, 255, 1, 1, 8, 0, 255, 0; TrunkGroup 1 = 1, 255, 2, 2, 9, 0, 255, 0; TrunkGroup 2 = 2, 255, 3, 3, , 0, 255, 0; TrunkGroup 3 = 1, 255, 4, 4, , 0, 255, 0; [ \TrunkGroup ] ; ; *** TABLE PstnPrefix *** ; ; [ PstnPrefix ] FORMAT PstnPrefix_Index = PstnPrefix_DestPrefix, PstnPrefix_TrunkGroupId, PstnPrefix_SourcePrefix, PstnPrefix_SourceAddress, PstnPrefix_ProfileId; PstnPrefix 0 = *, 2, *, *, 0; [ \PstnPrefix ] ; ; *** TABLE TxDtmfOption *** ; ; [ TxDtmfOption ] FORMAT TxDtmfOption_Index = TxDtmfOption_Type; TxDtmfOption 0 = 4; [ \TxDtmfOption ] ; ; *** TABLE TrunkGroupSettings *** ; ; [ TrunkGroupSettings ] FORMAT TrunkGroupSettings_Index = TrunkGroupSettings_TrunkGroupId, TrunkGroupSettings_ChannelSelectMode, TrunkGroupSettings_RegistrationMode, TrunkGroupSettings_GatewayName; TrunkGroupSettings 0 = 1, 3, 255, ; TrunkGroupSettings 1 = 2, 3, 255, ; [ \TrunkGroupSettings ] ; ; *** TABLE EnableCallerId *** ; ; [ EnableCallerId ] FORMAT EnableCallerId_Index = EnableCallerId_IsEnabled; EnableCallerId 0 = 1; EnableCallerId 1 = 1; EnableCallerId 2 = 1; EnableCallerId 3 = 1; [ \EnableCallerId ] ; ; *** TABLE TargetOfChannel *** ; ; [ TargetOfChannel ] FORMAT TargetOfChannel_Index = TargetOfChannel_Destination, TargetOfChannel_Type; TargetOfChannel 2 = 53, 1; TargetOfChannel 3 = 58, 1; [ \TargetOfChannel ]

I do not see your ini, please attach it again. Are you using the MP114 FXO, FXS, or 2FXO/2FXS. If you can post your PBxnsip and MP114 logs, that will be helpful too.