[Cisco 7960 Ring Tone / Huntgroup Melody]

I have noticed that if you specify a specific ring tone on a Cisco 7960 (other than the default chirp) it will not be played when calling the extension from the inside, or outside of the office. However if the phone is part of a hunt group where the ring melody is set to none, then the ring tone you selected on the phone will play. I am guessing that the PBXnSIP is sending a specific ring melody to the phone and overriding the user's selection. Is there a way to stop the PBXnSIP from sending a specific melody to the phone without needing to have it ring through a hunt group that is specifically set not to send one?

[Snom 360 Park Reminder]

I have found that on a Snom 360 if there are different buttons programmed to be different Park+Orbit destinations, the park reminder feature does not work. however if you manually put the call on hold, and dial *85+orbit number then the reminder feature works. Does anyone know how to fix this?

[Caller ID From Address]

I am trying to pass outbound caller ID on a NexVortex trunk. I have found that the caller ID that they accept is the portion infront of the @ symbol of the sip from address. The problem is PBXnSIP populates this with the info entered in the Account: field of the trunk, and not the Trunk DID: field. The problem is the Account: field will not accept dunamic content like the Trunk DID field will in order to send the tel: aliases. NexVortex will not accept the caller ID to be sent in the form of Remote Party/Privacy Indication:

[2.1.7]

You are correct, it only offered camp on when calling from a cell phone associated with an internal account. Now that I realize that, I can accept it, however I cannot accept that it offers when there is no answer.

[ondemand recording]

What did you find? I am asking myself the same question right now.

[2.1.7]

I am running 2.1.8 and the PBXnSIP is now offering call camp when the extension does not answer, and rolls to voicemail. It is also offering call camp to external callers. Is there a way to make it only offer when the call comes from the inside, and the extension is in use?

[Dynamically changing a scheduled flag]

Based on the many key systems I have had experience with I like the systems that use an override mode. The extension would place a call to the Day Night service flag. They would then be prompted to enter 1 to override into day mode (temporarily until the next scheduled mode change). 2 to override into night mode (temporarily until the next scheduled mode change). 3 to permanently override into day mode, 4 to permanently override into night mode, and 0 to cancel any active overrides. The permissions could be set to only allow certain extensions to place a call to the service flag, or you could pin protect it. You could also utilize a "monitor extension button" to indicate if any of the overrides are active.

 

I have also had many issues selling this system simply because of many small details like this that have existed on traditional phone systems forever. People take them for granted, and don't care so much about the wonderful new capabilities a system like this can bring if they have to loose useful features that they have had for 20+ years

[CDR EMAIL Date Problem]

I just read the RFC, and PBXnSIP clearly not compliant with the RFC on several levels. The RFC states:

 

"The zone specifies the offset from Coordinated Universal Time (UTC,

formerly referred to as "Greenwich Mean Time") that the date and

time-of-day represent. The "+" or "-" indicates whether the

time-of-day is ahead of (i.e., east of) or behind (i.e., west of)

Universal Time. The first two digits indicate the number of hours

difference from Universal Time, and the last two digits indicate the

number of minutes difference from Universal Time. (Hence, +hhmm

means +(hh * 60 + mm) minutes, and -hhmm means -(hh * 60 + mm)

minutes). The form "+0000" SHOULD be used to indicate a time zone at

Universal Time. Though "-0000" also indicates Universal Time, it is

used to indicate that the time was generated on a system that may be

in a local time zone other than Universal Time and therefore

indicates that the date-time contains no information about the local

time zone."

 

The first TWO digits indicate the hour offset, and the second TWO indicate the minute offset. The first violation is there is more than the total of 4 digits that are allowed by the RFC. The second problem is no time zone in the world is more that + or - 13 hours from UTC. I am in the central time zone which means that we are either -0500 or -0600 depending on Daylight savings time.

[CDR EMAIL Date Problem]

I am running 2.1.7 and noticed that on some email clients, the date of the email appears to be almost 13 days in the future. Other email clients like outlook do not have this problem. I have figured out that the issue lies on the PBXnSIP machine. The date and time is set correctly, however the offset is set to -30000 This shifts the time 12.5 days! If the email client pays attention to this value, the email can show up way out of chroniligical order from the rest of the emails in the mailbox. I have checked the PBXnSIP server, and it's timezone settings within windows are set properly.

[Snom 360 Autoprovisioning VLAN]

I have my network setup with all voice on VLAN 3 The problem is that the autoprovisioning feature keeps removing the VLAN settings from the phone, and it looses connectivity. I was told that I can go into the generated folder, and manually edit the file for the phone, however PBXnSIP overwrites my setting changes to the file. I am forced to manually configure the phone. Is there a fix?

[Buttons, huntgroups and 360's]

The problem is then you loose the pickup feature. You also loose the ability to transfer to that extension by pressing the transfer button followed by the speed dial button. With a Snom 220 set to destination, you can do all 3 on 1 button.

[2.1.7.2461 Message Waiting Indicator Issue]

When a caller leaves a voicemail, and they then press # 9 as they are promped to do from the voice mail system, the message Waiting Indicator never turns on. However if the caller leaves a message, and then hangs up, the indicator will turn on. I have verified that this is an issue with 2.1.6 as well as 2.1.7.2461 All running on Win2k3. This is happening on Snom, as well as Cisco phones. Doesn't matter is the caller leaves the message from the inside or outside. Any suggestions?

[Buttons, huntgroups and 360's]

I am having the same issue. Customers coming from traditional PBX systems expect to be able to monitor, and speed dial the extension all on the same button. I feel that not having this feature is a major shortcoming, and leads to many unhappy customers. I did find that if you are using a snom 220 you can set the button type to "destination", and then enter the extension number in the format of <sip:204@yourdomain.com;user=phone;intercom=true> and the button will monitor, speed dial, and pickup ringing calls all in one. No one ever complains about accidentally picking up a call. I wish there was a way to get a snom 360 to do this. The snom 360 does not have the ability to set the button type to "destination"

[Multiple DID Routing to 1 extension]

The "Change names in To/From-headers" in the domain settings" did the trick! Thanks a million

[Multiple DID Routing to 1 extension]

I am trying to use PBXNSIP as a go between, between my ITSP, and a traditional Samsung iDCS 100 PBX. The pbx supports sip, however it is not fully compliant, so I need to send everything through PBXNSIP and treat the traditional phone switch as an extension. This works perfectly in all respects other than inbound DID routing. The ITSP sends me the 11 digit DID info, and I can use it as tel: aliases on the extension however when the PBXNSIP sends the call along to the Samsung PBX it strips all of the DID info out of the to and the contact fields of the sip invite request, and therefore the Samsung always gets the 3 digit extension number and does not know how to route the call based on DID.