[Version 4.2 Inter-Domain Calling Thru SIP PRI GWY]

I'm running a server with multiple domains and I use a PRI Gateway to route calls to/from the PSTN. With version 3.4 I could call from one domain to the other by sending the call to the PSTN and getting it back through the PRI Gateway. When I upgrade to version 4.2, I can get a call from domain A to domain B in the same manner. However, when I call from B back to A, PBXnSIP challenges the INVITE from the PRI Gateway with a 401 "Authentication Required". I've checked all domain settings and they match on both. The Trunk that faces the PRI Gateway is a Global Trunk used by both domains.

 

What has changed between 3.4 and 4.2 that would cause this call scenario to stop working?

[404 Not Found]

I'm running release 3.3.1 in both Linux and Windows Server 2008 and I'm getting "404 Not Found" failures on extensions that have worked previoulsy. These servers are running multiple domains. The problem clears when the extension is deleted and then recreated. It appears to be an issue with the account database. Does anyone have a solution for this?

[multi domain PNP]

I've just come across this same issue of registering a 7961 in a multi domain environment. Does anyone have the answer?

[Alert-Info Parameter Defaults]

PBXnSIP's default value for Alert-Info is Belcore-dr3. Where is that changed for individual Extension?

[Moving and Copying Messages]

I recently upgraded a CS410 to release 3.3.1.3177 and the mailbox voice prompts for Moving and Copying Messages to other mailbox were not correct. Once I applied the latest US English Prompts file, the prompts were correct except for the final notification on Copying a message. When the Copying feature is used, the system response following the "##" is "message number" instead stating that the message has been copied. Also, the documentation on the wiki states that Copying is allowed to Extensions, Agent Groups and Hunt Groups. The system does not allow Copying to Agent Groups. The other two work fine.

[Cannot leave VM]

Tested the Red Hat version and the problem is resolved.

 

Will you have a set of release notes for this build when you officially release it?

[Cannot leave VM]

This link does not work.

[Cannot leave VM]

I have a RedHat environment. I'll be happy to try a test build for that environment.

[Cannot leave VM]

Sounds like you've been able to replicate the problem. I'll await a fix.

[Cannot leave VM]

The home path in this installation is "/home/PBXnSIP". Here are the permissions on the path directories:

 

drwxrwxrwx 4 root root 4096 Nov 17 14:11 home

drwxrwxrwx 36 root root 4096 Feb 14 00:00 PBXnSIP

drwxr-xr-t 2 root root 4096 Feb 7 14:09 accesslist

drwxr-xr-t 2 root root 4096 Feb 7 17:16 acds

drwxr-xr-t 2 root root 4096 Feb 7 14:09 adrbook

drwxr-xr-t 2 root root 4096 Feb 9 10:32 attendants

drwxr-xr-t 2 root root 20480 Feb 7 14:26 audio_en

drwxr-xr-t 2 root root 4096 Feb 7 14:20 audio_moh

drwxr-xr-t 2 root root 4096 Feb 7 14:09 button_lists

drwxr-xr-t 2 root root 4096 Feb 7 14:09 buttons

drwxr-xr-t 2 root root 4096 Feb 7 17:16 callingcards

drwxr-xr-t 2 root root 4096 Feb 8 14:40 calls

drwxr-xr-t 2 root root 12288 Feb 14 10:56 cdr

drwxr-xr-t 2 root root 4096 Feb 7 14:09 colines

drwxr-xr-t 2 root root 4096 Feb 9 09:26 conferences

drwxr-xr-t 2 root root 4096 Feb 9 14:39 dial_plan

drwxr-xr-t 2 root root 4096 Feb 9 14:38 dial_plan_entry

drwxr-xr-t 2 root root 4096 Feb 8 15:02 domain_alias

drwxr-xr-t 2 root root 4096 Feb 8 15:02 domains

drwxr-xr-t 2 root root 4096 Feb 9 10:31 extensions

drwxr-xr-t 2 root root 4096 Feb 7 17:16 hoots

drwxr-xr-t 2 root root 4096 Feb 7 17:16 hunts

drwxr-xr-t 2 root root 4096 Feb 7 14:09 ivrnodes

drwxr-xr-t 2 root root 4096 Feb 13 13:13 messages

drwxr-xr-t 2 root root 4096 Feb 7 14:09 mohs

lrwxrwxrwx 1 root root 24 Feb 9 17:19 pbxctrl -> pbxctrl-rhes4-3.2.0.3143

-rwxr-xr-x 1 root root 8172448 Nov 17 14:14 pbxctrl-rhes4-3.0.1.3023

-rwxr-xr-x 1 root root 7174304 Jan 28 13:29 pbxctrl-rhes4-3.1.2.3120

-rwxr-xr-x 1 root root 7340132 Jan 29 15:11 pbxctrl-rhes4-3.2.0.3143

drwxr-xr-t 2 root root 4096 Feb 7 14:09 pnp_parms

drwxr-xr-t 2 root root 4096 Feb 13 13:13 recordings

drwxr-xr-t 2 root root 4096 Feb 7 15:19 registrations

drwxr-xr-t 2 root root 4096 Feb 7 14:09 schedules

drwxr-xr-t 2 root root 4096 Feb 14 00:02 spool

drwxr-xr-t 2 root root 4096 Feb 7 17:16 srvflags

drwxr-xr-t 2 root root 4096 Feb 9 13:49 trunks

drwxr-xr-t 2 root root 4096 Feb 9 11:34 user_alias

drwxr-xr-t 2 root root 4096 Feb 9 10:32 users

drwxr-xr-t 2 root root 4096 Feb 9 09:28 wipers

[Cannot leave VM]

Looking for an update on this issue.

[Cannot leave VM]

Yes, there is a BYE message. I've attached the log file for your reference.

pbxnsip.txt

[Cannot leave VM]

Yes, all my parameters are set correctly. As Norman mentioned, a #9 to accept the message works. Just hanging up causes the scenario described earlier.

[Cannot leave VM]

I should have mentioned that I'm running on Red Hat as well with version 3.2.0.3143. I downgraded to 3.1.2.3120 and had the same exact problem. Took it down to 3.0.1.3023 and the problem went away. I should mention that I'm running 3.2.0.3143 on several CS410s and don't see this issue. Based on my experience and some of the other feedback on this topic, it appears this issue is affecting Red Hat and Windows releases 3.1.2 and higher.

[Cannot leave VM]

I too am having the same issue. I've checked permissions on the "recordings" folder and everything is fine. I actually see the .msg files that the log reports as being deleted. I've checked the mailbox settings and I'm not confirgured to send messages via email. When you call into the mailbox, the system reports no new messages.