-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Jim,
If you can, try using the latest 3.10 RPM:
http://repo.2600hz.com/R15B-staging/6/x86_64/Kazoo/origin/3.10/kazoo-R15B-3.10-1.el6.x86_64.rpm
And see if that addresses the issue for you.
On 04/08/2014 02:03 PM, Darren Schreiber wrote:
> Hi Jim, We looked at this extensively and it is working for us. I
> am not sure what else to give you here. It seems specific to your
> setup from what I can tell, so I can't advise further.
>
> "
2600hz...@googlegroups.com<mailto:
2600hz...@googlegroups.com>"
> <
2600hz...@googlegroups.com<mailto:
2600hz...@googlegroups.com>>
>
>
Subject: Re: openCNAM lookups not working
>
> Hmm..no further comments on this? It appears to be some bug in the
> cnam code...I'm really surprised that it has worked for anyone
> given the bug I found with the malformed URL....
>
> In case it matters, I'm running on CentOS 6.x
>
> --Jim
>
>
> On Fri, Apr 4, 2014 at 10:01 AM, Jim Kusznir
> <
jkus...@gmail.com<mailto:
jkus...@gmail.com>> wrote: Ok, with
> help from people over on #erlang, I did manage to find out what's
> going on. It turns out there is still a bug in the code. ibrowse
> wants a flat string, not an iolist, which is what currently
> happens.
>
> So, the patch/fix is to modify line 224 to look like: Url =
> unicode:characters_to_list(wh_util:to_list(get_http_url(JObj))),
> Unfortunately, its still failing, but this time its with a timeout
> error. I also modified line 237 to look like: lager:debug("cnam
> lookup for ~p failed: ~p ~p", [Number, _R, Url]),
>
> Thus getting the specific URL its feeding to the web browser. In
> any case, I now get this as my error: pr 4 12:50:29 voip
> 2600hz[19743]:
> |
701cd8ed41cb19bc...@64.2.142.26<mailto:
701cd8ed41cb19bc...@64.2.142.26>|stepswitch_cnam:237
> (<0.1226.0>) cnam lookup for <<"
+15093385920<tel:%2B15093385920>">>
> <
jkus...@gmail.com<mailto:
jkus...@gmail.com>> wrote: I took a
> look, but my programming is not great, and I don't know any erlang,
> so it wasn't obvious how to add logging.
>
> I did take some extra debugging steps: I ran the sup command
> specified, I flushed yum's cache, reinstalled the kazoo package,
> and rebooted, but still no go. I did get more debug output:
>
> Apr 2 14:11:23 voip 2600hz[1001]: |0000000000|Undefined:Undefined
> (<0.881.0>) Supervisor stepswitch_sup started
> poolboy:start_link([{worker_module,stepswitch_cnam},{name,{local,stepswitch_cnam_pool}},{size,10},{max_overflow,50},...])
> at pid <0.883.0> Apr 2 14:11:25 voip 2600hz[1001]:
> |00000000000|whapps_config:422 (<0.1008.0>) fetch db config for
> notify.cnam_request Apr 2 14:11:25 voip 2600hz[1001]:
> |00000000000|whapps_config:439 (<0.1008.0>) stored
> notify.cnam_request into whapps config cache Apr 2 14:11:25 voip
> 2600hz[1001]: |00000000000|notify_util:145 (<0.1008.0>) compiling
> notify_cnam_request_text_tmpl: 'Caller name update request for
> {{request.number}}#012#012Request#012Display-Name:
> "{{request.cnam.display_name}}"#012#012Number#012Number:
> {{request.number}}#012State:
> {{request.number_state}}#012Local-Number:
> {{request.local_number}}#012#012Account#012Account ID:
> {{account.pvt_account_id}}#012Account Name:
> {{
account.name<
http://account.name>}}#012Account Realm:
> {{account.realm}}#012#012{% if admin %}Admin#012First Name:
> {{admin.first_name}}#012Last Name: {{admin.last_name}}#012Email:
> {{admin.email}}#012Timezone: {{admin.timezone}}#012#012{% endif
> %}{% if devices %}SIP Credentials#012{% for device in devices
> %}User: {{device.user.first_name}}
> {{device.user.last_name}}#012Email:
> {{device.user.email|default:""}}#012SIP Username:
> {{device.sip.username}}#012SIP Password:
> {{device.sip.password}}#012SIP Realm: {{account.realm}}#012#012{%
> endfor %}{% endif %}{% if account.pvt_wnm_numbers %}Phone
> Numbers#012{% for number in account.pvt_wnm_numbers
> %}{{number}}#012{% endfor %}#012{% endif %}Service#012URL:
> {{service.url}}#012Name:
> {{
service.name<
http://service.name>}}#012Provider:
> {{service.provider}}#012#012Sent from {{service.host}}' Apr 2
> 14:11:26 voip 2600hz[1001]: |00000000000|notify_util:145
> (<0.1008.0>) compiling notify_cnam_request_html_tmpl:
> '<html><head><meta charset="utf-8" /></head><body><h3>Caller name
> update request for {{request.number}}</h3><h2>Request</h2><table
> cellpadding="4" cellspacing="0" border="0"><tr><td>Display-Name:
> </td><td>"{{request.cnam.display_name}}"</td></tr></table><h2>Number</h2><table
> cellpadding="4" cellspacing="0" border="0"><tr><td>Number:
> </td><td>{{request.number}}</td></tr><tr><td>State:
> </td><td>{{request.number_state}}</td></tr><tr><td>Local-Number:
> </td><td>{{request.local_number}}</td></tr></table><h2>Account</h2><table
> cellpadding="4" cellspacing="0" border="0"><tr><td>Account ID:
> </td><td>{{account.pvt_account_id}}</td></tr><tr><td>Account Name:
> </td><td>{{
account.name<
http://account.name>}}</td></tr><tr><td>Account
> Realm: </td><td>{{account.realm}}</td></tr></table>{% if admin
> %}<h2>Admin</h2><table cellpadding="4" cellspacing="0"
> border="0"><tr><td>Name: </td><td>{{admin.first_name}}
> {{admin.last_name}}</td></tr><tr><td>Email:
> </td><td>{{admin.email}}</td></tr><tr><td>Timezone:
> </td><td>{{admin.timezone}}</td></tr></table>{% endif %}{% if
> devices %}<h2>SIP Credentials</h2><table cellpadding="4"
> cellspacing="0" border="1"><tr><th>User</th><th>Email</th><th>SIP
> Username</th><th>SIP Password</th><th>SIP Realm</th></tr>{% for
> device in devices
> %}<tr><td>{{device.user.first_name}}{{device.user.last_name}}</td><td>{{device.user.email|default:""}}</td><td>{{device.sip.username}}</td><td>{{device.sip.password}}</td><td>{{account.realm}}</td></tr>{%
> endfor %}</table>{% endif %}{% if account.pvt_wnm_numbers
> %}<h2>Phone Numbers</h2><ul>{% for number in
> account.pvt_wnm_numbers %}<li>{{number}}</li>{% endfor %}</ul>{%
> endif %}<h2>Service</h2><table cellpadding="4" cellspacing="0"
> border="0"><tr><td>URL:
> </td><td>{{service.url}}</td></tr><tr><td>Name:
> </td><td>{{
service.name<
http://service.name>}}</td></tr><tr><td>Service
> Provider: </td><td>{{service.provider}}</td></tr></table><p
> style="font-size:9pt;color:#CCCCCC">Sent from
> {{service.host}}</p></ Apr 2 14:11:26 voip 2600hz[1001]:
> |00000000000|notify_util:145 (<0.1008.0>) compiling
> notify_cnam_request_subj_tmpl: 'Caller name update request for
> {{request.number}}' Apr 2 14:11:26 voip 2600hz[1001]:
> |00000000000|notify_cnam_request:36 (<0.1008.0>) init done for
> notify_cnam_request Apr 2 14:11:28 voip 2600hz[1001]:
> |00000000000|wh_amqp_channel:259 (<0.1008.0>) bound notify_listener
> to notifications exchange (routing key notifications.number.cnam)
> via channel <0.840.0> Apr 2 14:26:32 voip 2600hz[1001]:
> |
3d1f9a5f62054120...@64.2.142.26<mailto:
3d1f9a5f62054120...@64.2.142.26>|whapps_config:422
> (<0.4276.0>) fetch db config for stepswitch.cnam Apr 2 14:26:32
> voip 2600hz[1001]:
> |
3d1f9a5f62054120...@64.2.142.26<mailto:
3d1f9a5f62054120...@64.2.142.26>|whapps_config:439
> (<0.4276.0>) stored stepswitch.cnam into whapps config cache Apr 2
> 14:26:32 voip 2600hz[1001]:
> |
3d1f9a5f62054120...@64.2.142.26<mailto:
3d1f9a5f62054120...@64.2.142.26>|stepswitch_cnam:237
> (<0.4276.0>) cnam lookup for <<"
+15093321225<tel:%2B15093321225>">>
> failed: {url_parsing_failed,{error,invalid_uri}} -------------- Not
> sure how to go on from here, though...
>
> --Jim
>
>
> On Tue, Apr 1, 2014 at 11:51 PM, James Aimonetti
> <
ja...@2600hz.com<mailto:
ja...@2600hz.com>> wrote: Possible, if you
> upgraded the RPM without restarting the whistle_apps VM.
>
> You could try:
>
> sup whistle_maintenance hotload stepswitch_cnam
>
> to ensure the latest BEAM is loaded (basically the Erlang
> bytecode).
>
> Alternatively, you could add some logging to see what the URL is
> just before it makes the ibrowse request.
>
> On 04/01/2014 07:40 PM, Jim Kusznir wrote:
>> Thanks! They do match exactly.
>
>> Is there the possibility of "cached binary" (or whatever erlang
>> calls machine-executable code) hanging around somewhere? Is
>> there anything other than reboot that would be required for the
>> new code to take effect?
>
>> Here's the exact log entry that came in earlier today (random
>> call): Apr 1 14:53:54 voip 2600hz[1001]: |
>>
55ec249c1d7a53f5...@64.2.142.26<mailto:
55ec249c1d7a53f5...@64.2.142.26>|stepswitch_cnam:237
>>
>>
(<0.7828.8>) cnam lookup for <<"
+13024148737<tel:%2B13024148737>">> failed:
>>>>> <
dar...@2600hz.com<mailto:
dar...@2600hz.com>>wrote:
From: Jim Kusznir <
jkus...@gmail.com<mailto:
jkus...@gmail.com>> Reply-To:
>>>>>> "
2600hz...@googlegroups.com<mailto:
2600hz...@googlegroups.com>"
>>>>>>
>>>>>>
<
2600hz...@googlegroups.com<mailto:
2600hz...@googlegroups.com>>
Date: Monday, March 31,
>>>>>> 2014 at 10:06 AM To:
>>>>>> "
2600hz...@googlegroups.com<mailto:
2600hz...@googlegroups.com>"
>>>>>>
>>>>>>
<
2600hz...@googlegroups.com<mailto:
2600hz...@googlegroups.com>>
>>>>>>>>> "
https://api.opencnam.com/v2/phone/{{phone_number}}<
https://api.opencnam.com/v2/phone/%7B%7Bphone_number%7D%7D>",
>>>>>>>>>> "
2600hz...@googlegroups.com<mailto:
2600hz...@googlegroups.com>
>>>>>>>>>> <javascript:>"
>>>>>>>>>> <
2600hz...@googlegroups.com<mailto:
2600hz...@googlegroups.com><javascript:>
>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
Subject: Re: openCNAM lookups not working
>>>>>>>>>>
>>>>>>>>>> Any suggestions on how to troubleshoot this
>>>>>>>>>> further? I haven't found any indication that
>>>>>>>>>> Kazoo has "seen" any of my configs (even though
>>>>>>>>>> they're in the database) -- no attempts to
>>>>>>>>>> connect or anything. I don't know where to look
>>>>>>>>>> for what's going on, or to even verify that its
>>>>>>>>>> recognizing my documents in the db correctly,
>>>>>>>>>> that they've been loaded/activated, etc.
>>>>>>>>>>
>>>>>>>>>> Thanks! --Jim
>>>>>>>>>>
>>>>>>>>>> On Monday, March 24, 2014 5:14:11 PM UTC-7,
>>>>>>>>>> Darren Schreiber wrote:
>>>>>>>>>>>
>>>>>>>>>>> OK, then it must be some other issue you are
>>>>>>>>>>> having, cause this works for sure on latest
>>>>>>>>>>> RPM...
>>>>>>>>>>>
>>>>>>>>>>> From: Jim Kusznir
>>>>>>>>>>> <
jkus...@gmail.com<mailto:
jkus...@gmail.com>>
>>>>>>>>>>> Reply-To:
>>>>>>>>>>> "
2600hz...@googlegroups.com<mailto:
2600hz...@googlegroups.com>"
>>>>>>>>>>>
>>>>>>>>>>>
<
2600hz...@googlegroups.com<mailto:
2600hz...@googlegroups.com>> Date:
Monday, March
>>>>>>>>>>> 24, 2014 at 5:03 PM To:
>>>>>>>>>>> "
2600hz...@googlegroups.com<mailto:
2600hz...@googlegroups.com>"
>>>>>>>>>>>
>>>>>>>>>>>
<
2600hz...@googlegroups.com<mailto:
2600hz...@googlegroups.com>> Subject: Re:
>>>>>>>>>>> openCNAM lookups not working
>>>>>>>>>>>
>>>>>>>>>>> I found updated rpms inthe repo; I installed
>>>>>>>>>>> them, sup flush'ed, and rebooted, but still no
>>>>>>>>>>> change in CNAM lookups...
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --Jim
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On Thu, Mar 20, 2014 at 8:09 AM, Jim Kusznir
>>>>>>>>>>> <
jkus...@gmail.com<mailto:
jkus...@gmail.com>>
>>>>>>>>>>> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> In case the RPM has been uploaded, I looked
>>>>>>>>>>>> for new RPMs in the repo, found none...8am
>>>>>>>>>>>> PDT.
>>>>>>>>>>>>
>>>>>>>>>>>> I don't know if it hasn't been pushed yet,
>>>>>>>>>>>> or perhaps the rpmdb needs to be
>>>>>>>>>>>> regenerated...
>>>>>>>>>>>>
>>>>>>>>>>>> I did try a yum clean all as well, just in
>>>>>>>>>>>> case, and that did not reveal any updates.
>>>>>>>>>>>>
>>>>>>>>>>>> --Jim
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> On Wed, Mar 19, 2014 at 2:18 PM, Darren
>>>>>>>>>>>> Schreiber
>>>>>>>>>>>> <
dar...@2600hz.com<mailto:
dar...@2600hz.com>>wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
We discovered today that infact there may
>>>>>>>>>>>>> have been an issue with this.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Please try the latest RPM tomorrow (we'll
>>>>>>>>>>>>> spin it sometime today if it hasn't been
>>>>>>>>>>>>> done already). Should fix this.
>>>>>>>>>>>>>
>>>>>>>>>>>>> From: Jim Kusznir
>>>>>>>>>>>>> <
jkus...@gmail.com<mailto:
jkus...@gmail.com>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
Reply-To: "
2600hz...@googlegroups.com<mailto:
2600hz...@googlegroups.com>"
>>>>>>>>>>>>> <
2600hz...@googlegroups.com<mailto:
2600hz...@googlegroups.com>>
>>>>>>>>>>>>> Date: Wednesday, March 19, 2014 at 1:35 PM
>>>>>>>>>>>>> To:
>>>>>>>>>>>>> "
2600hz...@googlegroups.com<mailto:
2600hz...@googlegroups.com>"
>>>>>>>>>>>>>
>>>>>>>>>>>>>
<
2600hz...@googlegroups.com<mailto:
2600hz...@googlegroups.com>> Subject: Re:
>>>>>>>>>>>>> "
https://api.opencnam.com/v2/phone/{{phone_number}}<
https://api.opencnam.com/v2/phone/%7B%7Bphone_number%7D%7D>",
>>>>>>>>>>>>> <
ja...@2600hz.com<mailto:
ja...@2600hz.com>>wrote:
>>>>>>>>>>>>>>>> "
https://api.opencnam.com/v2/phone/{{phone_number}}<
https://api.opencnam.com/v2/phone/%7B%7Bphone_number%7D%7D>",
>>>>>>>>>
http://2600hz.comsip:...@2600hz.com<mailto:
sip%3A...@2600hz.com>
>>>>>>>>>
>>>>>>>>>
tel:
415.886.7905<tel:
415.886.7905> irc:mc_ @ freenode
>>>>>>>>>>>>>>
>>>>>>>>>>> -- You received this message because you are
>>>>>>>>>>> subscribed
>>>>>>>>>>>>>> to the Google Groups "2600hz-users"
>>>>>>>>>>>>>> group. To unsubscribe from this group and
>>>>>>>>>>>>>> stop receiving emails from it, send an
>>>>>>>>>>>>>> email to
>>>>>>>>>>>>>>
2600hz-users...@googlegroups.com<mailto:
2600hz-users...@googlegroups.com>.
>>>>>>>>>>>>>> For more options, visit
>>>>>>>>>>>>>>
https://groups.google.com/d/optout.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> -- You received this message because you
>>>>>>>>>>>>> are subscribed to the Google Groups
>>>>>>>>>>>>> "2600hz-users" group. To unsubscribe from
>>>>>>>>>>>>> this group and stop receiving emails from
>>>>>>>>>>>>> it, send an email to
>>>>>>>>>>>>>
2600hz-users...@googlegroups.com<mailto:
2600hz-users...@googlegroups.com>.
>>>>>>>>>>>>> For more options, visit
>>>>>>>>>>>>>
https://groups.google.com/d/optout.
>>>>>>>>>>>>>
>>>>>>>>>>>>> -- You received this message because you
>>>>>>>>>>>>> are subscribed to the Google Groups
>>>>>>>>>>>>> "2600hz-users" group. To unsubscribe from
>>>>>>>>>>>>> this group and stop receiving emails from
>>>>>>>>>>>>> it, send an email to
>>>>>>>>>>>>>
2600hz-users...@googlegroups.com<mailto:
2600hz-users...@googlegroups.com>.
>>>>>>>>>>>>> For more options, visit
>>>>>>>>>>>>>
https://groups.google.com/d/optout.
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>> -- You received this message because you are
>>>>>>>>>>> subscribed to the Google Groups "2600hz-users"
>>>>>>>>>>> group. To unsubscribe from this group and stop
>>>>>>>>>>> receiving emails from it, send an email to
>>>>>>>>>>>
2600hz-users...@googlegroups.com<mailto:
2600hz-users...@googlegroups.com>.
>>>>>>>>>>> For more options, visit
>>>>>>>>>>>
https://groups.google.com/d/optout.
>>>>>>>>>>>
>>>>>>>>>> -- You received this message because you are
>>>>>>>>>> subscribed to the Google Groups "2600hz-users"
>>>>>>>>>> group. To unsubscribe from this group and stop
>>>>>>>>>> receiving emails from it, send an email to
>>>>>>>
2600hz-users...@googlegroups.com<mailto:
2600hz-users...@googlegroups.com>
>>>>>>> <javascript:>. For more options,
>>>>>>>>>> visit
https://groups.google.com/d/optout.
>>>>>>>>>>
>>>>>>>>>
>>>>>
>>>>>>>
>>>>>>> -- You received this message because you are
>>>>>>> subscribed to the Google Groups "2600hz-users" group.
>>>>>>> To unsubscribe from this group and stop receiving
>>>>>>> emails from it, send an email to
>>>>>>>
2600hz-users...@googlegroups.com<mailto:
2600hz-users%2Bunsu...@googlegroups.com>.
>>>>>>>
>>>>>>>
For more options, visit
>>>>>>>
https://groups.google.com/d/optout.
>>>>>>>
>>>>>>
>>>>>> -- You received this message because you are subscribed
>>>>>> to the Google Groups "2600hz-users" group. To unsubscribe
>>>>>> from this group and stop receiving emails from it, send
>>>>>> an email to
>>>>>>
2600hz-users...@googlegroups.com<mailto:
2600hz-users%2Bunsu...@googlegroups.com>.
>>>>>> For more options, visit
>>>>>>
https://groups.google.com/d/optout.
>>>>>>
>>>>>> -- You received this message because you are subscribed
>>>>>> to the Google Groups "2600hz-users" group. To unsubscribe
>>>>>> from this group and stop receiving emails from it, send
>>>>>> an email to
>>>>>>
2600hz-users...@googlegroups.com<mailto:
2600hz-users%2Bunsu...@googlegroups.com>.
>>>>>> For more options, visit
>>>>>>
https://groups.google.com/d/optout.
>>>>>>
>>>>>
>
>>>
>>> -- You received this message because you are subscribed to the
>>> Google Groups "2600hz-users" group. To unsubscribe from this
>>> group and stop receiving emails from it, send an email to
>>>
2600hz-users...@googlegroups.com<mailto:
2600hz-users%2Bunsu...@googlegroups.com>.
>>> For more options, visit
https://groups.google.com/d/optout.
>>>
>
>
>
> -- You received this message because you are subscribed to the
> Google Groups "2600hz-users" group. To unsubscribe from this group
> and stop receiving emails from it, send an email to
>
2600hz-users...@googlegroups.com<mailto:
2600hz-users%2Bunsu...@googlegroups.com>.
>
>
For more options, visit
https://groups.google.com/d/optout.
>
>
>
>
> -- You received this message because you are subscribed to the
> Google Groups "2600hz-users" group. To unsubscribe from this group
> and stop receiving emails from it, send an email to
>
2600hz-users...@googlegroups.com<mailto:
2600hz-users...@googlegroups.com>.
iF4EAREIAAYFAlNEawUACgkQ54NxaUq7OmDbgQEAw3SwpzCYyfcSoTMfT8hKe6ZR
uRopnb4rrSK1Y7mIrXcA/0TwE9JFIfg1tuYS1OCnlvsJ3nzYT7EPYYwYXHP9cEOK
=bqLC
-----END PGP SIGNATURE-----