BLA not working with polycom firmware 4.0.7 and sipxecs canary

[Rick Cogley]

Hello - I'm using Canary sipXecs (2016.02.1.7f726 2016-02-24UTC10:02:54 2e5d52493173) update 0. 

I had my phones set to firmware 4.0.7, bootrom 4.4.0B, and set up BLA successfully like this - 

* select user that corresponds to the line on the phones we want to share - 2000

* select phones for that extension, click Shared and Apply 

* then select all the phone mac addresses, and send profiles

In ~10 seconds, the line button on the physical phone changes, so its icon goes from solid to half and half - white and grey. (varies by model)

Once we see that, the BLA is enabled and when a caller dials the DID attached to the line button 2000, we can pick it up, press hold on the phone, and others with that same line on the phone could simply press the button to pick up. 

Well, today I upgraded to firmware 4.0.10, found out that BLA stopped working, so long story short, I downgraded back to 4.0.7. 

Unfortunately, to no avail. I cannot seem to get BLA working again, in this seemingly simple configuration. When we pick up, put that call on hold, we have to use the Transfer button on the phone to send it specifically to a group or extension. That works fine. But other peoples' phones no longer show that the call is on the shared 2000 line (there's no indication at all), and this is the case for all the phones I have - including Polycom 331, 450, 670 and VVX 1500s.

Can anyone give me advice on what to check? 

Sincerely appreciate your help,

Rick

[Ryan Colobong]

Hello Rick,

I'm checking this one out. Will give you an update within the day

regards,

--
You received this message because you are subscribed to the Google Groups "SIPfoundry users and developers group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sipfoundry-users-and-dev...@googlegroups.com.
To post to this group, send email to sipfoundry-users-a...@googlegroups.com.
Visit this group at https://groups.google.com/group/sipfoundry-users-and-developers-group.
To view this discussion on the web visit https://groups.google.com/d/msgid/sipfoundry-users-and-developers-group/c1a5adee-aa02-4d15-8186-e015d8bf1478%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Ryan Colobong]

Hello Rick,

Can you give us the snapshot logs for us to investigate this.

regards,

[Ryan Colobong]

Hello Rick,

Can you increase first the log for the ingress and presence log when you provide me the snapshot for the sipxecs.

You can do this by:

            System > SBC > Log Level > Debug

System > SIP Ingress > Log Level > Debug

System > Presence Server > Log Level > Debug

System > Presence Server > Log Level > SIPX Plugin Log Level > Debug

Then apply/save those settings to the servers. Wait for a couple of minutes before you replicate the issue.

Then for the snapshot:

Diagnostics > Snapshot > Apply.

This will generate a snapshot and provide you a download link. Send us a copy of this snapshot

regards,

[Rick Cogley]

hi Ryan, thanks very much. Here's a link to it: 

https://drive.google.com/open?id=0B3E_g6R5WF8AV1lyQVl5Vm41WjQ
I changed the logs to DEBUG, then just took the defaults on the snapshot. 
Sincerely,
Rick

[Rick Cogley]

By the way, the test I did was to dial two numbers that are shared, from my mobile at 090-9959-5452:

* 03-6273-3500 connected to extension 2000

* 03-6273-3513 connected to extension 2003

The result was the same as before. After putting the call on hold, the light on the line on the phone goes out. 

[Ryan Colobong]

Hello Rick,

Can you run this command on your sipxecs server

sudo kamcmd pkg.stats

and paste the result here.

regards,

[Rick Cogley]

Ryan, sorry for the delay - here you are: 

sudo kamcmd pkg.stats

{

entry: 0

pid: 3570

rank: 0

used: 289704

free: 7789920

real_used: 598688

total_size: 8388608

total_frags: 29

}

{

entry: 1

pid: 3582

rank: 1

used: 364520

free: 7604416

real_used: 784192

total_size: 8388608

total_frags: 94

}

{

entry: 2

pid: 3583

rank: 2

used: 362432

free: 7611688

real_used: 776920

total_size: 8388608

total_frags: 85

}

{

entry: 3

pid: 3585

rank: 3

used: 364952

free: 7605040

real_used: 783568

total_size: 8388608

total_frags: 83

}

{

entry: 4

pid: 3588

rank: 4

used: 362432

free: 7608616

real_used: 779992

total_size: 8388608

total_frags: 95

}

{

entry: 5

pid: 3590

rank: -1

used: 2013656

free: 13456

real_used: 8375152

total_size: 8388608

total_frags: 70

}

{

entry: 6

pid: 3592

rank: -1

used: 305168

free: 7773688

real_used: 614920

total_size: 8388608

total_frags: 15

}

{

entry: 7

pid: 3594

rank: -128

used: 312464

free: 7766584

real_used: 622024

total_size: 8388608

total_frags: 21

}

{

entry: 8

pid: 3596

rank: -2

used: 298792

free: 7779872

real_used: 608736

total_size: 8388608

total_frags: 19

}

{

entry: 9

pid: 3598

rank: -1

used: 305168

free: 7773688

real_used: 614920

total_size: 8388608

total_frags: 15

}

{

entry: 10

pid: 3600

rank: 5

used: 381808

free: 7694360

real_used: 694248

total_size: 8388608

total_frags: 40

}

{

entry: 11

pid: 3602

rank: 6

used: 381808

free: 7694360

real_used: 694248

total_size: 8388608

total_frags: 40

}

{

entry: 12

pid: 3604

rank: 7

used: 381808

free: 7694360

real_used: 694248

total_size: 8388608

total_frags: 40

}

{

entry: 13

pid: 3605

rank: 8

used: 381808

free: 7694360

real_used: 694248

total_size: 8388608

total_frags: 40

}

{

entry: 14

pid: 3607

rank: -4

used: 369352

free: 7709984

real_used: 678624

total_size: 8388608

total_frags: 29

}

[Rick Cogley]

Hi Ryan - great, done. 

And thanks very much. 

Is my server underpowered with 8GB RAM, should I increase that? 

Kind regards,

Rick 

On Sat, Apr 16, 2016 at 6:55 PM, Ryan Colobong <ryan.c...@gmail.com> wrote:

Hello Rick,

Sorry, i didnt notice that I didnt add the SIPFoundry list on our email discussion. We should set it back. We are currently looking on to this, we will provide a patch later on probably next week. The logs you have provided is enough for me to identify the issue. If I needed some info for you, ill notify you.

regards,

On Sat, Apr 16, 2016 at 8:12 AM, Rick Cogley <rick....@gmail.com> wrote:

Hi Ryan - not cc-ing the list because you removed the cc, so, if we should be cc-ing the list just say the word. I'll add it back. 

It's Sat 9am Japan time, and I'm going into the office today to work on the IVR. As an aside, I'm using the OS X "say" command on Mac to create the phrases, and finding it much improved over the version a couple years ago. The .aiff files still sound robotic, but, it's not terrible. I'm taking those and tweaking them in Adobe Audition (the Japanese "Kyoko" codec has a soft voice so you need to increase the gain on it), exporting to MP3, then using in the auto-attendant. 

Anyway, thanks again for your kind help. I will be there, so please advise if there is anything I should test. 

One thing about the settings you mentioned is, one was 8 so I increased it, and one was 16 so I left it the same. Unfortunately I do not remember which was which, sorry. Should I have doubled the 16 one?

The server has one 4-core Intel Xeon CPU E3-1220 V2 @ 3.10GHz, and 8Gb of physical RAM. Is that too underpowered? 

Sincerely,

Rick

On Fri, Apr 15, 2016 at 10:35 PM, Rick Cogley <rick....@gmail.com> wrote:

Hi Ryan - just saw this. I set both to 16 and sent profiles to the server. I'm still in the office, so I tried calling in, putting on hold and looking at another phone, but alas, no change. The line still does not light up. 

Unfortunately I need to leave now, as it's getting late. I don't want to miss the last train. 

Kind regards and thanks,

Rick 

On Fri, Apr 15, 2016 at 9:28 PM, Ryan Colobong <ryan.c...@gmail.com> wrote:

Hello Rick,

I need to update the kamailio script to allow kamcmd to send command to either on kamailio ingress and presence. I'll adjust this and provide some update as well. For now can you try updating the ingress & presence server by going to:

Server > Presence Server

Server > Ingress

and update the value of Default Private Memory from 8 to 16.

Once done, apply the changes to the server.

regards,

Ryan

[Ryan Colobong]

Hello Rick,

We have updated the rpms in the canary-release. This includes bug fixes related to web ui and sip functionalities. Please update your sipxecs rpm and let us know if this issue has been resolved on this update:

sudo yum update

After the update, restart the sipxecs and then wait for 1-2 minutes before testing the BLA issue.

In case you still encounter the issue on the BLA, increase the log level for System  > SIP Ingress and System  > Presence server to a Debug value. Replicate the issue and then send us a snapshot. Also run this command on the server terminal.

sudo kamcmd -s /var/sipxdata/tmp/kamailio-proxy.ctl pkg.stats

and provide us the output of this command.

regards,

[Rick Cogley]

Hi Ryan, thank you very much! I'll give it a try and let you know the result. 

Kind regards,

Rick 

[Rick Cogley]

Hi Ryan - ok, I did "sudo yum update" (no errors) then a "reboot", and after some time, the web interface comes up, but, there seems to be a problem with the kamailio-proxy. 

Here is a snapshot after the reboot and after trying to dial into a couple DIDs: 

https://drive.google.com/open?id=0B3E_g6R5WF8AQ1lsYVY0UW81b3c

I'm seeing this sort of thing in the /var/log/sipxpbx/kamailio-proxy.log: 

Apr 22 23:53:14 sipxecs1 /usr/sbin/kamailio[26321]: DEBUG: dialog [dlg_hash.c:320]: destroy_dlg(): destroying dialog 0x7fb3795b3c18 (ref 1)

Apr 22 23:53:14 sipxecs1 /usr/sbin/kamailio[26321]: DEBUG: dialog [dlg_hash.c:336]: destroy_dlg(): removed timer for dlg 0x7fb3795b3c18 [76:8283] with clid '52796163522...@10.81.2.3' and tags '1c527962671' ''

Apr 22 23:53:14 sipxecs1 /usr/sbin/kamailio[26321]: : <core> [mem/q_malloc.c:130]: qm_debug_frag(): BUG: qm_*: fragm. 0x7fb3791c83d0 (address 0x7fb3791c8400) end overwritten(c0c0c0c0, ffffffff)!

... and when I call any of our DIDs I get a "user busy". I have not tested BLA yet as I am not on the site.

It's late in Japan so I'll get some sleep now. 

Kind regards

Rick

[Rick Cogley]

Hi - just checking in. Is it safe to roll back with "yum history undo X" where X is the yum update number? 

Or, can I try uninstall/reinstall via rpm of the kamailio rpms? 

Regards,

--Rick

[Rick Cogley]

Hi - yesterday I tried re-installing the sipx-related RPMs that got updated during the yum update, but it made no difference. Kamailio still won't start, and as a result, dialing in from the outside does not get picked up by any DID number I dial. 

Because of that I cannot run "sudo kamcmd -s /var/sipxdata/tmp/kamailio-proxy.ctl pkg.stats".

I noticed:

[root@sipxecs1 ~]# /etc/init.d/sipxecs status

sipxconfig ( pid 13576 ) is running and listening on port

sipxcdr ( pid 11964 ) is running and listening on port

freeswitch ( pid 13717 ) is running and listening on port

sipxivr ( pid 14063 ) is running and listening on port

kamailio is stopped

kamailio dead but pid file exists

sec (pid 14902) is running...

sipstatus ( pid 14517 ) is running and listening on port

sipXproxy ( pid 14409 ) is running and listening on port

sipregistrar ( pid 14795 ) is running and listening on port

cf-serverd ( pid 15815 ) is running and listening on port

sipxprovision ( pid 14306 ) is running and listening on port

sipxrecording (pid  14692) is running...

So I tried: 

rm -rf /var/run/kamailio.pid

rm -rf /var/run/sipxpbx/kamailio-presence.pid

... but it makes no difference. Restarting just gets to the same kamailio-less situation. 

Anyone have any ideas? 

Kind regards,

Rick

[Ryan Colobong]

Hello Rick,

I got your snapshot, I'm currently checking the issue on kamailio.

regards,

[Ryan Colobong]

Hello Rick,

Sorry, I wasn't able to replicate the issue, can you please increase the logs both on the sbc, ingress and presence. I need more information.

Please Increase the log level to DEBUG for Ingress, Presence,  SBC, etc:

System > SIP Ingress > Log Level

System > Presence > Log Level

System > SBC > Log Level
System > SIP Proxy > Log Level
System > SIP Registrar > Log Level

Once done, restart the services via System Servers > Servers > Send Profile.

Wait for a couple of minutes then replicate the issue and get the snapshot.

I notice as well on your snapshot that some of the files in the kamailio script were not updated. Can you check if there is a file *.rpmnew inside the folder /etc/sipxbpx/kamailio? Also replace the templates in /etc/sipxpbx/kamailio using the attach files.

regards,

[Rick Cogley]

Hi Ryan - thanks very much. 

I managed to really mess things up with yum and all kinds of stuff started going wrong, so, I reinstalled centos and am now installing canary again from scratch. 

I am hoping the backups I took can be used to restore. 

I wonder, when I install using:

sudo bash -c "$(curl -L http://rpms.sipfoundry.org/canary-release/sipxecs-install)"

... does it install the latest Kamailio that you prepared? The log said it's 3.1.1 (Iirc). 

I ask because I'm a little wary of yum update at this point. 

Best regards,

Rick 

Rick 

To unsubscribe from this group and stop receiving emails from it, send an email to sipfoundry-users-and-developers-group+unsubscribe@googlegroups.com.
To post to this group, send email to sipfoundry-users-and-developers-group@googlegroups.com.

[Rick Gmail]

Finally got it basically working again. 

The BLA is working too. 

Restoration challenges:

* passwords don't get restored right. Somehow the Superadmin was blank. The reset command gave an error so I'm not sure if it errored and fixed the problem or, it restored as blank. Other passwords were not working as what I reset them to, so I just reset them manually one by one. Is there a way to bulk reset?

* most user aliases got set to blank so no inbound calls were working. Glad I even noticed. Reset and it's ok. 

* polycom 450 and vvx 1500 needed a manual reset. The 670s, 331s, and 7000 Conf phone were ok. 

* restored voicemail but it did not restore for all users. Some worked, some didn't. Will manually reset the latter. 

How can I confirm my installed version?

Regards

Rick

You received this message because you are subscribed to a topic in the Google Groups "SIPfoundry users and developers group" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/sipfoundry-users-and-developers-group/UncTpIV3w9Y/unsubscribe.
To unsubscribe from this group and all its topics, send an email to sipfoundry-users-and-dev...@googlegroups.com.
To post to this group, send email to sipfoundry-users-a...@googlegroups.com.

Visit this group at https://groups.google.com/group/sipfoundry-users-and-developers-group.

To view this discussion on the web visit https://groups.google.com/d/msgid/sipfoundry-users-and-developers-group/76e2e1a9-1011-464e-9e9a-44d4c42ffca6%40googlegroups.com.

[Ryan Colobong]

Hello Rick,

Glad that's work for you. As for the issue that you have raised, I'll check this up and replicate it on our side. We will provide you an update soon. Also we will still continue to investigate the issue on upgrading the sipxecs.

To verify your installation if it installed with the latest canary version. Please check the installed package sipxecs via:

yum info sipxecs.

It should match the version below:

Installed Packages
Name        : sipxecs
Arch        : x86_64
Version     : 2016.02
Release     : 21.6e2fd

If we want to make sure, you can send us a snapshot file on your new installed sipxecs and check if everything was setup or installed.

regards,

Rick 

To unsubscribe from this group and stop receiving emails from it, send an email to sipfoundry-users-and-dev...@googlegroups.com.

To post to this group, send email to sipfoundry-users-a...@googlegroups.com.
Visit this group at https://groups.google.com/group/sipfoundry-users-and-developers-group.
To view this discussion on the web visit https://groups.google.com/d/msgid/sipfoundry-users-and-developers-group/c1a5adee-aa02-4d15-8186-e015d8bf1478%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

You received this message because you are subscribed to a topic in the Google Groups "SIPfoundry users and developers group" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/sipfoundry-users-and-developers-group/UncTpIV3w9Y/unsubscribe.
To unsubscribe from this group and all its topics, send an email to sipfoundry-users-and-dev...@googlegroups.com.
To post to this group, send email to sipfoundry-users-a...@googlegroups.com.
Visit this group at https://groups.google.com/group/sipfoundry-users-and-developers-group.
To view this discussion on the web visit https://groups.google.com/d/msgid/sipfoundry-users-and-developers-group/76e2e1a9-1011-464e-9e9a-44d4c42ffca6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

You received this message because you are subscribed to the Google Groups "SIPfoundry users and developers group" group.

To unsubscribe from this group and stop receiving emails from it, send an email to sipfoundry-users-and-dev...@googlegroups.com.

To post to this group, send email to sipfoundry-users-a...@googlegroups.com.
Visit this group at https://groups.google.com/group/sipfoundry-users-and-developers-group.

To view this discussion on the web visit https://groups.google.com/d/msgid/sipfoundry-users-and-developers-group/FBE370CE-166F-49B1-9DED-F9E890429F43%40gmail.com.

[Rick Cogley]

Hi Ryan, thanks very much. 

Ok, confirmed via yum info sipxecs. 

Installed Packages

Name        : sipxecs

Arch        : x86_64

Version     : 2016.02

Release     : 21.6e2fd

Actually, yes, I've noticed a few more things. 

1. Got a couple of these via email: 

Message from sipXecs

Alarm: DNS_LOOKUP_FAILED

Reported on: sipxecs1.esolia.co.jp

Reported at: 2016-04-24T21:17:47+09:00

Message: sipxproxy:\": DNS lookup failed for 'sipxecs1.esolia.co.jp'. No valid 'SRV' records found\"

Suggested Resolution: Check DNS settings

... and it seems networking is somehow not quite right. 

 - the above says the SRV records are missing, but, I can see the SRV records... 

 - I can't ping or ssh to the server internally, where this was possible before, with the same server IP. I _can_ access both the web UI and ssh, via the external IP which is nat-ted through the firewall to the server. 

 - I _can_ ping _from_ the server to itself, or to various other devices on the network. 

 - The server had no loopback config file so I added one. 

 - The eth0 config file had PREFIX=7, which does not seem right. We are using 10.81.2.x for this server and phones, and 10.81.1.x for PCs etc. 

 - Despite the above error via email, the System, DNS, "DNS Advisor" checker gives the all clear. 

2. Transferring manually via the physical phones seems to be working, for instance, dropping VM to 82000. But when I try that same thing via the directory IVR it fails. I get the "wait a moment while I transfer your call" message, then I hear nothing, then the line drops. 

3. Diagnostics, Registrations shows all registrations are Expired. Yet, the phones seem to be working mostly fine. 

Here is the latest snapshot: 

https://drive.google.com/file/d/0B3E_g6R5WF8AUTRzN3VJcWRXb0k/view?usp=sharing

Just before I took it, I dialed 03-6273-3509 from my mobile, and tried transferring to the 1002000 conference by pressing 5, which should bring up the conference for x2000. I also tried entering my own extension 2011, but, this too just cuts off after a moment of silence. 

I did restore from backup, so, it's possible some file got corrupted. 

FYI and thanks very much for your help. Gotta get some sleep as I've been at this 15 hours. 

Sincerely

Rick 

[Rick Cogley]

Hi Ryan - I discovered some anomalies with the inability to ping the server and ssh to it, but, when I went in via an outside IP, reverse-natted via the firewall, it would let me in fine. Then, I found that the "ip addr" command was reporting an extra IP address linked to eth0, which is really odd. Further, something is inserting PREFIX=7 in that file (and network manager is not running). When I remove that PREFIX command in the eth0 file, and restart everything, I can get in from an internal machine, like I would expect. 

As for functionality, everything is working except, for IVR. I can deposit voicemails directly, but I cannot transfer to other extensions like voicemail drop or conferencing, when these are set up in the IVR. They were working before my reinstall, and I have confirmed that the settings are the same. I think, anyway. 

What can I try, to get the IVR to respond right, again? 

Thanks

Rick 

Rick 

To unsubscribe from this group and stop receiving emails from it, send an email to sipfoundry-users-and-developers-group+unsubscribe@googlegroups.com.
To post to this group, send email to sipfoundry-users-and-developers-group@googlegroups.com.

Visit this group at https://groups.google.com/group/sipfoundry-users-and-developers-group.
To view this discussion on the web visit https://groups.google.com/d/msgid/sipfoundry-users-and-developers-group/c1a5adee-aa02-4d15-8186-e015d8bf1478%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

You received this message because you are subscribed to a topic in the Google Groups "SIPfoundry users and developers group" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/sipfoundry-users-and-developers-group/UncTpIV3w9Y/unsubscribe.

To unsubscribe from this group and all its topics, send an email to sipfoundry-users-and-developers-group+unsubscribe@googlegroups.com.
To post to this group, send email to sipfoundry-users-and-developers-group@googlegroups.com.

Visit this group at https://groups.google.com/group/sipfoundry-users-and-developers-group.
To view this discussion on the web visit https://groups.google.com/d/msgid/sipfoundry-users-and-developers-group/76e2e1a9-1011-464e-9e9a-44d4c42ffca6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "SIPfoundry users and developers group" group.

To unsubscribe from this group and stop receiving emails from it, send an email to sipfoundry-users-and-developers-group+unsubscribe@googlegroups.com.
To post to this group, send email to sipfoundry-users-and-developers-group@googlegroups.com.

Visit this group at https://groups.google.com/group/sipfoundry-users-and-developers-group.

To view this discussion on the web visit https://groups.google.com/d/msgid/sipfoundry-users-and-

...

[Rick Cogley]

From time to time I am getting this sort of error by email, but, the DNS Advisor says the DNS is fine. 

Message from sipXecs
Alarm: DNS_LOOKUP_FAILED
Reported on: sipxecs1.esolia.co.jp

Reported at: 2016-04-29T10:36:29+09:00

Message: sipxproxy:\": DNS lookup failed for 'sipxecs1.esolia.co.jp'. No valid 'SRV' records found\"
Suggested Resolution: Check DNS settings

Not sure what this means. 

Kind regards

Rick

...

[Ryan Colobong]

Hello Rick,

This is mostly handled by the cfengine script on the sipxecs. I'll investigate the issue on the prefix on eth0 and the DNSSRV issue. Can you provide me the snapshot for this.

I need you to increase the log level to debug for System > Admin Settings > Log Level.

regards,

Rick 

To unsubscribe from this group and stop receiving emails from it, send an email to sipfoundry-users-and-dev...@googlegroups.com.
To post to this group, send email to sipfoundry-users-a...@googlegroups.com.

Visit this group at https://groups.google.com/group/sipfoundry-users-and-developers-group.
To view this discussion on the web visit https://groups.google.com/d/msgid/sipfoundry-users-and-developers-group/c1a5adee-aa02-4d15-8186-e015d8bf1478%40googlegroups.com.
For more options, visit ht

...

--

You received this message because you are subscribed to the Google Groups "SIPfoundry users and developers group" group.

To unsubscribe from this group and stop receiving emails from it, send an email to sipfoundry-users-and-dev...@googlegroups.com.
To post to this group, send email to sipfoundry-users-a...@googlegroups.com.

Visit this group at https://groups.google.com/group/sipfoundry-users-and-developers-group.

To view this discussion on the web visit https://groups.google.com/d/msgid/sipfoundry-users-and-developers-group/3d7d71ae-430a-4303-80b1-12b90df8ca2b%40googlegroups.com.

[Ryan Colobong]

Hello Rick,

For the eth0, I check the cfengine script, it should only modify this file

/etc/sysconfig/network-scripts/ifcfg-eth0

and should only add this two properties on ifcfg-eth0.

PEERDNS=NO
NM_CONTROLLED=NO

I looked at the IVR issue as well. Can you increase the log level to debug for the System > VoiceMail > Logging Level

regards,

[Rick Cogley]

Hi Ryan - here's the latest - 

https://drive.google.com/open?id=0B3E_g6R5WF8AXzZpdUV1SGozXzg

I tested like this: 

17:09 JST 

VM deposit from desk phone 82011

OK

17:11

VM deposit via DID to ...6273-3501

OK

17:11

Dial x2009 (user connected to directory/IVR)

IVR starts

One options is 5 to transfer to 1002000, the extension for 2000's conference

Press 5, get "please hold while I transfer" then it hangs up

Try again, this time entering 1002000, but, same result.

17:13

From desk phone, try 1002000, and it asks for conf PIN as expected

Enter PIN and conference starts

17:14

Desk phone, try deposit VM for 2000 via 82000, 

"Please leave message", and beep as expected. No hangup.  

OK

17:15

Call DID 6273-3509 (linked to extension 2009)

Try dialing extension 2011. 

"Please hold while I transfer" then, hangs up. 

Then I took the snapshot. 

Thanks for your help, Ryan. 

Kind regards,

Rick 

Rick 

To unsubscribe from this group and stop receiving emails from it, send an email to sipfoundry-users-and-developers-group+unsubscribe@googlegroups.com.
To post to this group, send email to sipfoundry-users-and-developers-group@googlegroups.com.
Visit this group at

...

[Rick Cogley]

Hi Ryan - I had the DHCP set up as "unmanaged" and had a couple extra segments defined in there. 

However, to simplify, I moved those off onto another DHCP server, and turned the "unmanaged" off, allowing sipXecs to control it completely. 

I don't think that's particularly important to DNS, but, wanted to mention because it simplifies the setup. 

--Rick

...

[Ryan Colobong]

Hello Rick,

Can you send the profile again to your servers to force generate configuration and replicate the data to mongodb.

This can be achieved by going to System > Servers > (Check the servers) > Send Profiles.

The issue was the REFER is being rejected by the proxy due to invalid authorization. This may due to that the configuration was not properly replicated as pin/password didn't match based on the logs.

Message me if you still have an issue on the IVR after you have send the updated the profiles of your server

regards,

--

You received this message because you are subscribed to the Google Groups "SIPfoundry users and developers group" group.

To unsubscribe from this group and stop receiving emails from it, send an email to sipfoundry-users-and-dev...@googlegroups.com.
To post to this group, send email to sipfoundry-users-a...@googlegroups.com.
Visit this group at https://groups.google.com/group/sipfoundry-users-and-developers-group.

To view this discussion on the web visit https://groups.google.com/d/msgid/sipfoundry-users-and-developers-group/4e524c8b-cd5e-4761-af31-e188bef00a41%40googlegroups.com.

[Rick Cogley]

Hi Ryan - thanks! That appears to have fixed it. Now the IVRs correctly respond to push tones and perform the transfers as expected. What a relief.

Right during the service restart, it appears, I got a lookup error message from the server saying it could not find any valid SRV records, but, they do exist and the DNS audit function gives the all-go. 

Message from sipXecs
Alarm: DNS_LOOKUP_FAILED
Reported on: sipxecs1.esolia.co.jp

Reported at: 2016-05-02T20:58:40+09:00

Message: sipxproxy:\": DNS lookup failed for 'sipxecs1.esolia.co.jp'. No valid 'SRV' records found\"
Suggested Resolution: Check DNS settings

Not sure what this means, but, it appears to basically working, so I'll look at that more after I am back from vacation next week. (It's golden week in Japan). 

Regards

Rick 

[Ryan Colobong]

Hello Rick,

Will investigate this as well. We should close this thread now as the other issue you have mention is no longer related to BLA.

regards,